Replace WFBATCH in document change history

[Sheth, Neeraja]

We have created a workflow for negative price variance on the PO which gets
kicked off when a PO is created or changed. If the variance is negative, it
goes to an approver. If it is zero or positive, the approval is automatic,
WF_BATCH shows up as the approver in the change documents, and the price
variance is documented as text on the PO header.
 
In your case, along with any text, you could put in the name of the approver
from a role resolution code. So even if you have WF_BATCH in the change
documents, users can look up the PO header text and see who the real
approver would have been.
 
Regards
 
Neeraja
 
 
 
> -----Original Message-----
>> From: Jensen, Ralph [SMTP:ralph.jensen at sap.com]
> Sent: Thursday, March 21, 2002 12:41 PM
> To:   SAP-WUG at MITVMA.MIT.EDU
> Subject:      Re: Replace WFBATCH in document change history
>
> What about passing the actual agent for the workitem
>
>       -----Original Message-----
>       From: Ea, Ty [mailto:TEa at citgo.com]
>       Sent: Thursday, March 21, 2002 9:18 AM
>       To: SAP-WUG at MITVMA.MIT.EDU
>       Subject: Replace WFBATCH in document change history
>
>
>
>       Hi Workflowers,
>
>       I posted a similar question a week ago but it did not appear on the
> distribution list.  Thought I'd give it another try.
>
>       We currently have a workflow that will automatically approve a
> Purchase Order or Outline Agreement if it determines that the creator of
> the
>
>       purchase document has enough systems of authority.  This
> functionality is made possible by calling function module BAPI_PO_RELEASE
> found
>
>       in method RELEASE of object type BUS2012.  It was hoped that this
> ability would create a more efficient work process.  The user would only
> need to go to his or
>
>       her workflow inbox if he/she does not have enough systems of
> authority.
>
>
>       Here is the problem.  We have recently noticed that all purchasing
> documents release by BAPI_PO_RELEASE have WFBATCH as the responsible user
> on its document change history.  I assume that this is due to the workflow
> manager executing the object method RELEASE in the background.  This has
> created some confusion for our business users when they are trying to
> determine who approved the document at a later time.
>
>       Does anybody know of a way to update the change history to show the
> user id of the person for which BAPI_PO_RELEASE was executed, instead of
> the id of the workflow manager (WFBATCH)?  I don't even know if we can
> alter SAP's change history log since it serves as an audit trail, but I
> thought I'd ask.
>
>       Thanks.
>
>       Ty
>       The information transmitted is intended only for the person or
> entity to which it is addressed and may contain confidential and/or
> privileged material. Any review, retransmission, dissemination or other
> use of, or taking of any action in reliance upon, this information by
> persons or entities other than the intended recipient is prohibited. If
> you received this in error, please contact the sender and delete the
> material from any computer.
>