PO approval workflow

[LANGE, BODO]

Hi Nicholas,
Could that be a buffer problem?!? Try to run a Buffer_refresh before doing the PO Change.
 
Just an idea....
Regards,
Bodo

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Nicholas Brand
Sent: martedì 26 luglio 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