On the pull from ECC using this extractor for 28 days out of 30 it runs in acceptable time. However 1-2 days a month (always in the first 6 days) it will go from 5 minutes to 5 hours with very comparable records pulled. Seems that record count does not matter. Example
2/3/2015 pulled 4113 records in 5hr 40m
2/4/2015 pulled 12,639 records in 1h 54m (more records less time than day before)
2/5/2015 pulled 1268 records in 3m ( so slightly more than double record on 2/3, but 5h 37m longer to extract)
I've checked everything else running in ECC on the days it takes so long compared to the other days and nothing additional is running on the long extraction days.
Here is what I see in the ECC log:
02/03/2015 00:42:55 ************************************************************************* | |||||||||||
02/03/2015 00:42:55 1 LUWs confirmed and 1 LUWs to be deleted with function module RSC2_QOUT_CONFIRM_DATA | |||||||||||
02/03/2015 06:23:47 Call customer enhancement BW_BTE_CALL_BW204010_E (BTE) with 4,113 records | |||||||||||
02/03/2015 06:23:47 Result of customer enhancement: 4,113 records | |||||||||||
02/03/2015 06:23:47 Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 4,113 records |
You see the long lag time betweeen 00:42:55 and 06:23:47. On the days this extracts fast, there are just seconds of a lag time.
We have made the changes BWOM_SETTINGS based on SAP Note 631836.
Also, you see in the log it reads "EXIT_SAPLRSAP_001 (CMOD) with 4,113 records". In CMOD on the ECC side there is no code for extractor 0CO_OM_NWA_2 so I am not sure why it would say that. Looking back at my BIREQU* jobs in SM37, looks like I can't find any extractor that does not show it calls that Customer exit. Maybe I just haven't noticed that in the past?
Thanks for any help.