PO approval workflow

Wed Jul 27 08:06:07 EDT 2005

Aha, if I understand it correct now the note I referred to earlier is
relevant. In fact it is spot on. Implement the correction and prepare to
celebrate :-)
-- 
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: 27. juli 2005 13:40
To: SAP Workflow Users' Group
Subject: Re: PO approval workflow

Mark,

Hi, the workflow was already in place - I've been called in to resolve
this issue.

The SWETYPV entry uses Receiver FM 'SWW_WI_CREATE_VIA_EVENT' - so it's
standard.

The triggering event for the workflow is 'RELEASESTEPCREATED' (not
'significantlychanged' as in my original email).
A wait for event listens for the 'significantlychanged' event - if this
happens the workflow is terminated, and a new one triggered through the
new 'RELEASESTEPCREATED' event that is also raised by SAP when a
significant change is made to the PO.

In SWUD, I've created the event 'RELEASESTEPCREATED' manually and the
event creator *is* passed correctly to the new workflow instance (the
old workflow instance had completed before I created the event
manually).

So to summarise, if I create the event manually, the event creator is
passed into the workflow container and if SAP creates the event, the
workflow container value for _WF_INITIATOR is set to the user who
originally created the PO and not the one who created the new release
step.

Kind regards,
Nicholas Brand

             Mark Pyc

             <mark.pyc at gmail.c

             om>
To 
             Sent by:                  "SAP Workflow Users' Group"

             sap-wug-bounces at m         <sap-wug at mit.edu>

             it.edu
cc 

Subject 
             27/07/2005 09:00          Re: PO approval workflow

             Please respond to

               "SAP Workflow

               Users' Group"

G'day Nicholas,

Is this a WF you've just developed or was it already in place on site?
Although I'm not sure why it would be but could this be intentional in
the development? Are the SWETYPV entries using the standard FMs?

Have fun,
Mark

On 7/27/05, Kjetil Kilhavn <KJETILK at statoil.com> wrote:
> 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
>

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

_______________________________________________
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.