PO approval workflow

[Nicholas Brand]

Kjetil,

Thanks for your email.
Yes, it is a new instance of the workflow that is started - the workflow
logs confirm this.
For the first instance the event log shows the _EVT_CREATOR value as being
User-A and the workflow logs show _WF_INITIATOR as User-A.
For the second instance the event log shows the _EVT_CREATOR value as being
User-C but the workflow logs show _WF_INITIATOR as User-A.

I'm just having a dig around using SWUD.

Thanks again.


Kind regards,
Nicholas Brand



                                                                           
             "Kjetil Kilhavn"                                              
             <KJETILK at statoil.                                             
             com>                                                       To 
             Sent by:                  "SAP Workflow Users' Group"         
             sap-wug-bounces at m         <sap-wug at mit.edu>                   
             it.edu                                                     cc 
                                                                           
                                                                   Subject 
             27/07/2005 07:23          RE: PO approval workflow            
                                                                           
                                                                           
             Please respond to                                             
               "SAP Workflow                                               
               Users' Group"                                               
                                                                           
                                                                           




Just to make sure it is as strange as it sounds: this happens when user
C changes the PO significantly *after* the workflow has completed, so it
is a _new_ workflow that is started when the change is made?

That does indeed sound strange, but if it was true that the function
module has an error the same error should be observable for any type of
document for which an event can be triggered multiple times. Not that I
have tested this, but it seems strange that no-one has discovered it
before so that it could be corrected. Have you tried to create the event
manually with the workflow trace on (SWUD). Then you can see what goes
on when the bindings are transferred.

There are only seven OSS Notes for "WF_INITIATOR" - no such luck. ....
But there are 20 for "_WF_INITIATOR" - that search engine makes me
wonder.

Note 497893 is relevant for 46C (but only up to SAPKB46C30 according to
the note) and mentions a similar problem I guess, but it is for events
created in a workflow, and that is probably not what happens here. You
may want to have a look at it anyway.
--
Kjetil Kilhavn, Statoil KTJ IT BKS


-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Nicholas Brand
Sent: 26. juli 2005 19:14
To: sap-wug at mit.edu
Subject: PO approval workflow





A quick question...

We have a PO approval workflow using business object BUS2012.
It has one triggering event: 'SIGNIFICANTLYCHANGED'.
The relevant binding between the event container and workflow container
is:
'_EVT_CREATOR' ==> '_WF_INITIATOR'
Fairly standard.

If User-A creates a PO it is workflowed to User-B for approval.
In the event log and workflow log the event creator and workflow
initiator are both shown as User-A.
User-B approves and releases the PO and the workflow completes.
This is all as it should be.

Now, if User-C significantly changes the PO so that a new release
strategy is required, the workflow is re-triggered.
In the event log the event creator (for the new workflow) is correctly
shown as User-C.
In the workflow log you'd expect the workflow container element
'_WF_INITIATOR' to be equal to the '_EVT_CREATOR' value (User-C) - but
it ain't!
Instead the workflow container element '_WF_INITIATOR' is still shown as
User-A.

In other words, the user who first creates the PO is entered in the
workflow container element '_WF_INITIATOR' even for subsequent workflows
against the same PO.

At a guess it seems like an error in the function module that populates
the _WF_INITIATOR workflow container element.

Any clues out there? Is there an OSS note for this?

BTW we're on v4.6c


Kind regards,
Nicholas Brand

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug


-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you.

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug