on 06-27-2013 12:45 AM
Hi All,
Our aim was to send data from application system (ECC) to event management. It was achieved by calling /SAPTRX/EVENT_MGR_COMMUNICATE in user exits in the OTC transactions such as VA01/VA02, VL01N/VL02N etc.
We could run the design successfully in the quality system but it failed in production system specifically for the mass change jobs running in production. It runs into "Time_Out" error failing in the function module /SAPTRX/EVENT_MGR_COMMUNICATE.
Any tips on how to increase the performance would be appreciated.
Thanks,
Deb
Hello Deb,
can you post the exact position in the coding where the time out occurs?
Running a SAT/SE30 Trace would be also interesting to find out the root cause.
/SAPTRX/EVENT_MGR_COMMUNICATE is only a wrapper around several other modules. So a more detailed analysis would be needed.
Best regards,
Steffen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Steffen,
Thank you so much for replying.
Please see the active calls/events given below in the sequence as shown in the time_out dump. SETUP_BAPI_TABLE_EVTCNT is the exact point where it fails.
Please also note that this failure happens only when mass deliveries are created through VL10A for delivery due list.
I would also like to know if anyone have similar experience of communicating ECC data to EM during mass creation of deliveries through VL10A.
USEREXIT_SAVE_DOCUMENT --> /SAPTRX/EVENT_MGR_COMMUNICATE --> /SAPTRX/INTERNAL_EM_COMMUNICAT --> /SAPTRX/PROCESS_EVENTS --> SEND_EVENT_DATA --> SETUP_BAPI_TABLE_EVTCNT
User | Count |
---|---|
7 | |
4 | |
3 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.