Workitem reaching a wrong agent for release of PO
Ineke Hopman
ineke.hopman at nl.ibm.com
Mon Sep 5 03:39:10 EDT 2005
Hello,
It looks like a table isn't refreshed at the correct time. May be you can
check the code in the user exit and check if the internal table with the
release codes (or purchase groups) is refreshed correctly. If not it can
use the release strategy from the preceding time. This explains why
sometimes the wrong agent is determined (preceding release strategy was
different) and sometimes the correct agent is determined (if the preceding
release strategy was the same).
Hope this helps...a bit finding the error.
Kind regards,
Ineke Hopman
kavitha mahishi <kavitha.sap at gmail.com>
Sent by: sap-wug-bounces at mit.edu
05-09-2005 08:21
Please respond to
"SAP Workflow Users' Group"
To
sap-wug at mit.edu
cc
Subject
Workitem reaching a wrong agent for release of PO
Hi,
A workflow is implemented for release of Purchase Order(BUS2012).
For some PO's, due to some strange reason...PO meant for the role B1
are going to A1. The agents(userid's) for sending emails of B1,A1,C1,etc
are
mentioned in a custom table. Also the release strategy's are mapped in
the OMGS transaction.
I tried debugging the method, but could not reach any solution.
The recipients are established by accessing a custom table
ZMM_PO_AUTH. Standard Role(MM_po_rel) with function module
('ME_REL_GET_RESPONSIBLE') is used. User exit 'EXIT_SAPLEBNF_001' is
implemented to read the agents (userid's) from this table.
These agents are determined by the purchasing groups of the Purchase
Order and Release code. The different Release codes are A1, B1,
C1,D1,E1. Further the Release codes are determined by the Release
strategy while creating the PO. Different Release strategy's are A1,
B1, C1, D1(which have nothing to do with the Release Codes A1,
B1,...). These Release strategy's are picked up by the system based on
the Po amount which is all mentioned in the transaction OMGS.
Also another important observation is that is is not happening always
but only sometimes when the release strategy on the PO is changed.
Also it does not happen everytime a release strategy is changed, which
is making it impossible to replicate the case.
Please help me resolve this.
Thanks,
kavitha
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20050905/e608995c/attachment.htm
More information about the SAP-WUG
mailing list