N-step BADI approval SRM workflow

[Mark Pyc]

Why do they want to switch to header level approval if they want the same
functionality as item level????

If they want Item Level approval functionality, then surely Item Level
approval should be the solution!?!?


On 6/22/07, Kris <kvenigalla at gmail.com> wrote:
>
> Mark,
>
> We are currently using the item level WF. It works fine for parallel
> approval. But the customer wants to switch to header level approval but
> wants the same functionality as item level.
>
> Even though i am detremining FA based on the cost assignment, the header
> level WF sent the entire SC to FA approver. Only one workitem is sent for
> both FA and MGMT approvers.
>
> I may have to switch to sequential approvals. Let me know if you have any
> other ideas.
>
> Thanks
>
>
>  On 6/22/07, Mark Pyc <mark.pyc at gmail.com> wrote:
> >
> > G'day Venkat,
> >
> > It sounds like you want to do Line-Item level approval.
> >
> > At the Financial Analyst stage each approver is only responsible for
> > their lines items, at the Managerial stages the managers are resposnible for
> > all line items (note they will only see 1 workitem for approval).
> >
> > Is there a reason for not using the Line-Item approval technique?
> >
> > Have fun,
> > Mark
> >
> >
> >  On 6/22/07, Kris < kvenigalla at gmail.com> wrote:
> >
> > >  Hi,
> > >
> > > I am implementing N-step approval badi for SC approval using header
> > > level workflow (WS14000133) in SRM 5.0. My requirement is to determine
> > > the financial analysts responsible for each line item and then the mangement
> > > approvers based on their approval limits. Financial analyst need to approve
> > > the SC concurrently before the management approvers receives the SC. I
> > > developed the code in the BADI to populate the approval table. First time
> > > when the SC is created the approval table looks as follows,
> > >
> > > Index    Branch    Approver
> > > 1         1        FA1
> > > 1         2        FA2
> > > 1         3        FA3
> > > 2         1        MGMT approver1
> > > 3         1        MGMT approver2
> > >
> > > FA1, FA2 and FA3 recieves the SC. The approval preview looks great.
> > > Since this is not item level workflow, FA will approve the SC at the header
> > > level.
> > >
> > > Here is the Issue--
> > > When FA1, FA2 or FA3 approves the SC, the approval index is
> > > incremented by 1 in the workflow, the SC is sent to MGMT approvers based on
> > > he index by skipping all the FA approvers.
> > >
> > > In this scenario, how to develop logic to send the SC to MGMT
> > > approvers only after the FA approvers approves it. I mean how to control the
> > > index and branching in BADi. I am using header level workflow.
> > >
> > > Any suggestion would be highly appreciated.
> > >
> > > Thanks
> > >
> > > Venkat
> > >
> > > _______________________________________________
> > > 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20070622/475fb2c1/attachment.htm