Actual user ID instead of WF-BATCH

[Hilsbos, Margaret A]

Hi Melih,

We had a similar issue with the purchase requisition workflow. We solved it as follows:

1.       Capture the actual agent of the approval step. (in binding of user decision, map &_WI_ACTUAL_AGENT& from decision to an element in your workflow container)

2.       Pass the actual agent to a custom method that does the release.  (workflow step using a custom task based on your custom method; bind the element from step 1)

3.       Code in the method sets sy-uname before calling the bapi that executes the release:


  sy-uname = i_agent+2.     " i_agent is &_WI_ACTUAL_AGENT&  from the decision step

  CALL FUNCTION 'BAPI_REQUISITION_RELEASE_GEN'
    EXPORTING
      number            = i_banfn
      rel_code          = i_relcode
      no_commit_work    = ' '
    IMPORTING
      rel_status_new    = e_new_rel_stat
      rel_indicator_new = e_new_rel_indicator
    TABLES
      return            = et_return.


I hope this is helpful!

Margaret Hilsbos
Day & Zimmermann<http://www.dayzim.com/>



From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Melih Ozbagi
Sent: Wednesday, December 28, 2011 9:45 AM
To: sap-wug at mit.edu
Subject: Re: Actual user ID instead of WF-BATCH

Dear colleagues,

We use extended notification for SAP Business Workflow where work items, with a link, are send to users Outlook inbox.

There is an active vendor master approval workflow. When a user creates or changes vendor master LFA1-CONFS (confirmation status) becomes 1 until it is approved or rejected by an authorized person. Once work item is executed confirmation status is updated through TA FK08 but when I have a look to change history of fields WF-BATCH is the user that updated confirmation status although work item is executed by an actual user such as XXTTZZ.

Is there any change to see actual user ID who executed work item change history of field.

Thanks

Melih

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20111228/e3c7f242/attachment-0001.htm