Workflow Is Not Starting. What Might Be Possible Reasons And Correspo

1.	Workflow Is Not Starting. What Might Be Possible Reasons And Corresponding Solution?
Answer» If started by an event: Run SWU_OBUF and check transaction SWU3 for problems . Check that the linkage between the event and the WORKFLOW exists in transaction SWE2 and is activated . Check transaction SWEL to see if event was created / gets created (may need transaction SWELS to turn SWEL on) . Test if CREATING the event manually in SWUE triggers the workflow. Check if there is a start condition that isn’t being satisfied. Check if the event is in a queue (if event queueing is turned on, see transaction SWEQADM) Check WF-BATCH in transaction SU01, see if all is well (e.g. password not expired) If started directly (e.g. with function module SAP_WAPI_START_WORKFLOW; not recommended if it can be avoided): Run SWU_OBUF and check SWU3 for problems Check if workflow has been set to GENERAL TASK If started by an event: If started directly (e.g. with function module SAP_WAPI_START_WORKFLOW; not recommended if it can be avoided):

Workflow Is Not Starting. What Might Be Possible Reasons And Corresponding Solution?

Answer»

If started by an event:

Run SWU_OBUF and check transaction SWU3 for problems .
Check that the linkage between the event and the WORKFLOW exists in transaction SWE2 and is activated .
Check transaction SWEL to see if event was created / gets created (may need transaction SWELS to turn SWEL on) .
Test if CREATING the event manually in SWUE triggers the workflow.
Check if there is a start condition that isn’t being satisfied.
Check if the event is in a queue (if event queueing is turned on, see transaction SWEQADM)
Check WF-BATCH in transaction SU01, see if all is well (e.g. password not expired)

If started directly (e.g. with function module SAP_WAPI_START_WORKFLOW; not recommended if it can be avoided):

If started by an event:

If started directly (e.g. with function module SAP_WAPI_START_WORKFLOW; not recommended if it can be avoided):