Replace WFBATCH in document change history

[Dart, Jocelyn]

Good Ty - but like I said you are best off to introduce people to generic
object services anyway.
That will work for either solution and even your current one.
Jocelyn
 
-----Original Message-----
From: Ea, Ty [mailto:TEa at citgo.com]
Sent: Friday, 22 March 2002 10:16 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Replace WFBATCH in document change history
 
 
Jocelyn and Ralph,
 
Thank you for both of your replies.  Option No. 1 sounds like it just might
work.  I will give it a try and will let you know the results.
 
Thanks again!
 
Sincerely,
Ty
 
 
 
-----Original Message-----
From: Dart, Jocelyn [mailto:jocelyn.dart at sap.com]
Sent: Thursday, March 21, 2002 4:59 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Replace WFBATCH in document change history
 
 
HI Ty,
There are basically two (2) options:
 
1) Make the task that calls BAPI_PO_RELEASE a DIALOG task - i.e. set the
background processing
flag off, and make sure the advance with dialog flag is on - that way the
release will be run under the
dialog user of the previous step without them actually intervening.
The downside of this is that they need the authority to release the p.o.
directly in their authorization
as their authority's will be used by the BAPI.
 
2) If you don't want to give them the authority to release the p.o.
directly, and even if you do take option 1)
- introduce them to Generic Object Services (you haven't said what release
you are in? 4.0 or above I hope?)
These appear, depending on the verison, in the system>services menu or as a
floating button near the
okcode command field once you have selected your PO, e.g. using transaction
ME23 or ME23n.  They
let you see a workflow summary of what workflows have run against this
particular PO - and will show who
did the release step nice and clearly.
 
If you want to show who actually authorised the release in e.g. an audit
trail report, you can use the
usual WAPIs to extract the info from the workflow log.
 
Enjoy.
 
 
 
Jocelyn Dart
Consultant (EBP, BBP, Ecommerce, Internet Transaction Server, Workflow)
SAP Australia
Email  <mailto:jocelyn.dart at sap.com> jocelyn.dart at sap.com
Tel: +61 412 390 267
Fax: +61 2 9935 4880
 
 
-----Original Message-----
From: Jensen, Ralph
Sent: Friday, 22 March 2002 5:41 AM
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.
 
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.
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20020322/666e7365/attachment.htm