WF-BATCH Password Deactivated For 12 Hours-Cant Identify All Missed Items

[former_member944332]

Afternoon SAP Gurus!

Our WF-BATCH was down for 12 hours due to a glitch and no WF-Batch workflow items were kicked off during that period... Unfortunately it was down the entire business day from 6 am to 6 pm. I was not notified until 4 pm of the issue, which means there is a large gap of missing workflows. I have manually triggered all events that were from new document creation. My issues is that there was no trace running during that time due to constraints on memory. (Fortune 500, yet still... lol)...

I am a bit puzzled on how I can track the rest of these down. Any advice would be greatly appreciated!

p.s. Seems like this scenario is extremely rare, what could i do to prepare myself in the future?

[former_member602690]

Hi Aron,

1. Look in SAP Transaction Codes to see if they show any, some or all workflows which attempted to start, but didn't start, or didn't finish

SWI2

SWI2_FREQ

SWI2_DIAG

SWI2_ADM1

SWI2_DEAD

SWI1

SWIA

etc.

(see Reference below)

2. Look at your list of all workflow events/templates activated, for example, inbound orders, inbound invoices, etc.

3. For each SAP document that should trigger workflow, look at all documents created that day, during that time range, see which SAP document numbers were created during that time, see if workflow triggered for that document# or not. (Example: lookup list of all inbound SAP Sales Orders created that day (if they should have triggered workflow)

4. If workflow was not triggered, for these SAP documents that should have triggered workflow, manually trigger the workflow(s)

References

https://www.tutorialspoint.com/sap_business_workflow/sap_business_workflow_administration.htm