You are on page 1of 11

Event Trace & Troubleshooting

Andrea Schmieden

1

BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Event Trace & Troubleshooting 2 .Agenda „ Business Process Engine Overview „ Runtime Cache „ Process Execution Monitoring „ Message Monitoring „ Message Monitoring Examples „ Event Trace „ Troubleshooting © SAP AG 2004.

receiver data and event receiver linkage data. The function does not therefore always delete the entire event trace automatically. 3 . but displayed in a list. the display can also be restricted to linkages with errors. „ The following data is logged in the event trace: „ Event data z Triggering object type. BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Event Trace & Troubleshooting All events created correctly are logged in the event trace irrespective of whether potential receivers exist. the events you select are not deleted. In addition to the criteria for event data.Event Trace Transaction SWELS to switch on event trace Transaction SWEL to display event trace © SAP AG 2004. „ If a receiver is entered in the event trace. „ Deleting the event trace „ The deletion of events can also be controlled using selection criteria. „ If you mark the field Only display list. triggering object z Event ID z Triggering program z Trigger date and time „ Receiver or linkage data z Receiver function module z Receiver type z Receiver instance z Linkage status „ Displaying the event trace „ The event trace display can also be restricted using a selection screen. it does not necessarily mean that this receiver was called successfully.

BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Event Trace & Troubleshooting 4 .Agenda „Business Process Engine Overview „ Runtime Cache „ Process Execution Monitoring „ Message Monitoring „ Message Monitoring Examples „ Event Triggering „ Troubleshooting © SAP AG 2004.

comparison between xsd: date and xsd: time) ¾ Check SXI_CACHE – return code of the process has to be 0 © SAP AG 2004. BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Event Trace & Troubleshooting 5 .g.Troubleshooting (1) Messages sent to a process go to error state „ Cause 1: Customizing not complete ¾ Check SWF_XI_CUSTOMIZING – all entries must have status green „ Cause 2: Cache refresh not completed ¾ Check SXI_CACHE – Cache content has to be up-to-date (green traffic light) „ Cause 3: Runtime version of the process could not be created ¾ Check SXI_CACHE – return code of the process has to be 0 „ Cause 4: Invalid condition (e.

Troubleshooting (2) Messages sent to a process are delivered successfully but there is no corresponding process instance „ Cause: Communication between messaging pipeline and process engine is not completed (Messages are sent asynchronously to the Process Engine based on tRFC) ¾ Check SWU2 – there should be no tRFC entries waiting or in error state Process does not start „ Cause: Start correlation is not active ¾ Check SXI_Cache: Display integration process in Process Builder and select Basic Data -> Start Events -> Check if Start Events are active (The process is started via events) © SAP AG 2004. BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Event Trace & Troubleshooting 6 .

© SAP AG 2004. the event is put into the event queue (if active). ¾ Check SWEQADM: event queue background job must be running. BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Event Trace & Troubleshooting 7 . In case events can not be delivered.Troubleshooting (3) Process does not start or message is not delivered to started process „ Causes: Event queue background job not running. Use event browser to check errors. Messages are delivered to process instances via events.

Several messages are sent to the process and the messages are queued in a qRfc-queue.queues have to be activated © SAP AG 2004. BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Event Trace & Troubleshooting 8 . if a message activates a correlation that should be used by another message) ¾ Use SXMB_MONI to check the messages ¾ Check SXMB_ADM . but clicking on it does not display process instances „ Cause: The inbound queues of the process engine are not processed. This is to ensure that messages are serialized correctly (e.Troubleshooting (4) Message does not arrive in target system „ Cause: Outbound message queues are blocked due to high system load ¾ Check SMQ1: Check sender System Outbound Queues Message sent to a process shows PE indicator.g.XBQO*.

¾ Use SWELS to switch on event trace and re-run the message. no process instance found (message that activates the correlation arrives after the message that uses the correlation) ¾ Check SXMB_MONI. ¾ Check SWEQADM. ¾ Use SWEL to check the event trace. © SAP AG 2004. BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Event Trace & Troubleshooting 9 .Troubleshooting (5) Message sent to a process has adapter status red „ Cause: Correlation failed.

Useful Transactions and Report Transactions „ SXI_CACHE: Runtime cache „ SXMB_MONI_BPE: Process monitoring „ SXMB_MONI: Message monitoring „ SWI1: Processes and work items „ SWELS: Switch on event trace „ SWEL: Display event trace „ SWEQADM: Check events Report „ RSWF_CRL_MAINTAIN: Check active correlations © SAP AG 2004. BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Event Trace & Troubleshooting 10 .

Summary Now you should be able to: „ Understand the relationship between integration processes in XI and workflows in SAP Business Workflow „ Check the runtime version of an integration process in the XI runtime cache „ Perform process and message monitoring „ Perform basic troubleshooting © SAP AG 2004. BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Event Trace & Troubleshooting 11 .