AW: Workitem reaching a wrong agent for release of PO

Tue Sep 6 05:27:25 EDT 2005

Normally if the exit finds an agent it is displayed in the Tab.
If it is not displayed, in my installation it indicates a problem with the
responsible resolution.
If you fill in a break point in the exit it will stop in Tx ME23N and you
can debug.

-----Ursprüngliche Nachricht-----
Von: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] Im Auftrag von
kavitha mahishi
Gesendet: Dienstag, 6. September 2005 07:59
An: SAP Workflow Users' Group
Betreff: Re: Workitem reaching a wrong agent for release of PO

Thanks for your response.

In our installation I can see the Release Codes, description and
Release Options in the tab 'Release Strategy'. But can't see the User
assigned to those release codes. Pls inform if there is any setting to
see this on ME23N.

We are using EXIT_SAPLEBNF_005 not EXIT_SAPLEBNF_001.

When he PO is created with Release Strategy, the workflows (one for
each Release Code) start. When the PO is changed to
No-Release-Strategy (EKKO-FRGRL is initial), the already started
workflow's are expected to fail with 'Role Resolution returning no
agent' (at the 'Release PO' task) and thus stop continuation (Workflow
assumes ERROR status at this point).

But in this problematic case, some workflows with the same context,
are not going to Error status because the Role is returning some agent
and then the workitem goes to that agent. Here the agent returned by
the Role is not even the 'agent to be retruned if the Release strategy
is unchanged'.

Regards
Kavitha

On 9/5/05, Schmidinger, Heinz (Unaxis IT BZ)
<heinz.schmidinger at unaxis.com> wrote:
> I can see the release-responsible directly in Tx ME23N in Tab
> "Releasestrategy" if a release-strategy is found.
> 
> In the case where a PO is changed to no-release-needed (EKKO-FRGRL is
> initial) I fire an own event to stop existing release-WF.
> 
> If no release-strategy is found (needed), the mentioned exit is not
> executed
> (at least in my installation) and no Tab "Release.." is shown in Tx ME23N.
> 
> But you are writing you use Exit 'EXIT_SAPLEBNF_001' and release of
> Purchase
> Order(BUS2012). In my opinion this exit is executed by
> Purch.Requsition-Items (BUS2009)or Purch.Requsition (BUS2105) and
> EXIT_SAPLEBNF_005 is executed from BUS2012-Objects. Isn't it ?
> 
> 
> 
> -----Ursprüngliche Nachricht-----
> Von: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] Im Auftrag
> von
> kavitha mahishi
> Gesendet: Montag, 5. September 2005 14:54
> An: SAP Workflow Users' Group
> Betreff: Re: Workitem reaching a wrong agent for release of PO
> 
> Do you see the right responsible for relaese if you use transaction ME23N
> (View PO)?
>       How do we see the responsible person on the ME23N? (directly
> thru the PO or through my custom table)
>     Anyway in this particular case we will not be able to see that as
> the PO now is changed to an amount where there is no Release Strategy.
> 
> If the strategy change, the event release_step_created is fired with the
> new
> release_code.
>          Again here in this case it is not getting fired as there is
> no more a Release Strategy now.
> 
> Are you sure, that your WF is receiving this new event and process it
> right?
>    Our Work flow is not designed to "wait for this event" (thats
> triggering event).
> 
> Thanks,
> Kavitha
> 
> 
>     
> 
> On 9/5/05, Schmidinger, Heinz (Unaxis IT BZ)
> <heinz.schmidinger at unaxis.com> wrote:
> > Do you see the right responsible for relaese if you use transaction
ME23N
> > (View PO)?
> > 
> > If the strategy change, the event release_step_created is fired with the
> > new
> > release_code.
> > 
> > Are you sure, that your WF is receiving this new event and process it
> right
> > ?
> > 
> > -----Ursprüngliche Nachricht-----
> > Von: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] Im Auftrag
> > von
> > kavitha mahishi
> > Gesendet: Montag, 5. September 2005 12:30
> > An: SAP Workflow Users' Group
> > Cc: sap-wug-bounces at mit.edu
> > Betreff: Re: Workitem reaching a wrong agent for release of PO
> > 
> > Hi Ineke,
> > 
> > Thanks for the reply.
> > 
> > I am afraid this does not solve the problem. Preceding Release
> > Strategy was checked and the agent to whom the work item is being sent
> > in the faulty case is no where related to the release code any time.
> > 
> > user exit and tables are checked. No seeming solution seen:-(...
> > 
> > Any other tips as to how I can replicate such a case?
> > 
> > Thanks,
> > Kavitha
> > 
> > On 9/5/05, Ineke Hopman <ineke.hopman at nl.ibm.com> wrote:
> > > 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
> > > 
> > > 
> > >
> > 
> > _______________________________________________
> > SAP-WUG mailing list
> > SAP-WUG at mit.edu
> > http://mailman.mit.edu/mailman/listinfo/sap-wug
> > 
> > 
> > _______________________________________________
> > SAP-WUG mailing list
> > SAP-WUG at mit.edu
> > http://mailman.mit.edu/mailman/listinfo/sap-wug
> >
> 
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
> 
> 
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug