"Confirmation" Workflow in EBP

[Dart, Jocelyn]

Hi Yulianto, 
 
Actually SRM workflows do use a triggering event - they just don't use the standard Event Manager routines which is why they never show up on the standard event log.  
 
Instead SRM workflows use a series of equivalent custom event manager routines that let them simulate the triggering of the event, and then start the workflow either as a simulation or in actuality or both - this is so that the approval previews can be displayed even before the workflow starts. 
 
There is no point looking at SAP_WAPI_START_WORKFLOW - as SRM uses its own custom routines and not that particular standard API.  
 
Instead look at function modules with name beginning BBP_PDH_WFL... you will find routines there that evaluate the event. 
 
But in any case you should NOT need to track this through... there is no problem with having a custom workflow starting on event BUS2203.SAVED - the way SRM works it's custom event manager routines should still trigger that workflow. However there are some restrictions - for instance you must not use a check function module on the event, only a start condition, and only ONE workflow must be started by the SAVED event.  SRM workflows follow VERY VERY VERY specific patterns - e.g. settings in the basic data header, agents as ad hoc agents, program exits.  So your best bet is to compare the custom workflow to the standard Confirmation workflow in detail. 
 
Regards,
Jocelyn 

________________________________

From: sap-wug-bounces at mit.edu on behalf of Yulianto Abu Muhammad
Sent: Mon 31/03/2008 9:59 PM
To: SAP Workflow Users' Group
Subject: "Confirmation" Workflow in EBP


Dear All,
 
I just joined a support team where they currently have a problem with their workflow in their EBP system. They have an old EBP (SRM) system, it is 4.0 if I am not wrong.
 
They have a customized workflow for "Confirmation", where there is a triggering event which is "SAVED" event of the business object "BUS2203".
 
The wierd thing is, when we tried to examine the workflow log, we saw that this workflow is not started by the triggering event. We tried to switch on the event trace (SWELS) and tried to create a new confirmation. Workflow is started, but there is no log in the event trace. So I suspected that there might be a direct call of the workflow by calling the workflow API.
 
My question is, can anybody share with me, how to trace if a workflow is not started by a triggering event, but we want to know which program that has started this workflow. And in addition, this is not standard workflow, so there must be a customized setting that started this workflow. Unfortunately, the design documentation is really poor, so I can not find how they started the workflow there in the documentation.
 
Any help will be appreciated.
 
Regards,

Yulianto 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 5299 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20080401/6796bdfe/attachment.bin