SRM n step item level WF
Dart, Jocelyn
jocelyn.dart at sap.com
Sun Apr 10 21:40:37 EDT 2005
Glad you have it sorted Laszlo.
Jocelyn
-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of lmillich at yahoo.com
Sent: Monday,11 April 2005 3:37 AM
To: SAP Workflow Users' Group
Subject: RE: SRM n step item level WF
Jocelyn ,
Sorry for the late reply.
I appreciate your help to me and to the group.
In the meantime the problem is solved. An event
linkage activation was missing,the start condition
alone was not enough, but I also changed the BADI
code. Both problem has gone.
Thanks,
Laszlo
--- "Dart, Jocelyn" <jocelyn.dart at sap.com> wrote:
> Hi Laszlo,
> In your BADI, you specify which items are linked to
> which approvers.
> Sounds like you still haven't nutted out the BADI
> code correctly.
>
> Re the second problem - check for any OSS notes. If
> you can't find any
> report it in.
> Jocelyn
>
> -----Original Message-----
> From: sap-wug-bounces at mit.edu
> [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of lmillich at YAHOO.COM
> Sent: Wednesday,23 March 2005 8:27 AM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: SRM n step item level WF
>
> Hi Folks,
>
> In SRM 4.0 the 'n step item level' WF does not
> function as it is expected.
> I use WS14500015, I have implemented the BADI
> BBP_WFL_APPROV_BADI based on a sample SAP code.
> In the second step/level on item level different
> approvers should be determined based on cost center.
>
> I programmed this in the BADI.
> When there are different cost centers in the items,
> in the preview I can see that the items should be
> approved by different persons.This is good.
> But during approval in the inbox all the items are
> shown and can be accepted by all the approvers, the
> not relevant items are not greyed out.
> I tried to fill the 'hide_items_not_responsible'
> parameter,
> but this did not help either.
>
> The other problem:
> The workflow does not stop based on the BADI
> programming (I use currenlty 3 steps for testing
> purposes).
> I set the 'No_further_approval_needed' BADI
> parameter,
> but this is not passed to the corresponding WF
> container, and
> as I see even if it set, the workflow does not use
> it. So the WF does not stop after the 3.step,
> but tries to find new agents/approvers untill it
> reaches the WI limit.
>
> I appreciate any idea, which could help.
>
> Thanks,
>
> Laszlo M.
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Small Business - Try our new resources site!
> http://smallbusiness.yahoo.com/resources/
> _______________________________________________
> 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
>
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug
More information about the SAP-WUG
mailing list