SRM Badi N-step
Sue Keohan
keohan at ll.mit.edu
Tue Dec 13 20:07:44 EST 2005
Hi Jocelyn,
Thanks for the info. I wondered why APPROVAL_BRANCH was there, if not
to be used for dynamic parallel branches.
But can you assist further...
I put some simple code in the BAdi to create two branches, with
different approvers, then I modified the WF (WS14000134) container to
hold Approval_Branch, which I passed back in to the workflow from
TS14007989 (BUS4101,NEXTDYNAMICAPPROVERGET). Then I added
Approval_Branch under the miscellaneous Tab of the Approval Task
TS10008126 to specify the number of branches to create. Of course, I
did this in our sandbox environment (SRM 4.0) because I would never
modify an SAP workflow for real.
The workflow did create two branches, but the approvers were the same
for both branches. Sample simple BAdi code follows...
lt_approval_table-APPROVAL_INDEX = 1.
lt_approval_table-APPROVAL_AGENT = 'USSU18094'.
lt_approval_table-NAME = 'Susan Keohan'.
lt_approval_table-APPROVAL_DESCRIPTION = 'SC Appr at Level 1'.
lt_approval_table-approval_branch = 1.
lt_approval_table-APPROVAL_OBJECT_GUID = lv_guid.
append lt_approval_table to approval_table.
lt_approval_table-APPROVAL_INDEX = 1.
lt_approval_table-APPROVAL_AGENT = 'USSUETEST'.
lt_approval_table-NAME = 'Sues Test ID'.
lt_approval_table-APPROVAL_DESCRIPTION = 'SC Appr at Level 1'.
lt_approval_table-approval_branch = 2.
lt_approval_table-APPROVAL_OBJECT_GUID = lv_guid.
append lt_approval_table to approval_table.
1) Were my changes to the WF container, task->WF binding, and
Miscellaneous Tab unnecessary ?
2) Obviously, there's something wrong in my sample BAdi code, but how
can I capitalize on the APPROVAL_BRANCH and ensure that each branch has
different approvers ? The standard approval task wants to use the
expression 'ActualAgents' for rule resolution, but this would certainly
route to all the approvers, not to just the approvers specified at the
designated branch.
I am sure there are workarounds, but I would like this implementation to
follow the model that SAP has provided as much as possible.
Many thanks
Sue
Dart, Jocelyn wrote:
>Hi Sue,
>Yes it works in SRM 4.0 - not in lower releases.
>It has to work in SRM 4.0 because this is the sort of breakdown the item
>approval uses.
>
>
>Regards,
>Jocelyn Dart
>Senior Consultant
>SAP Australia Pty Ltd.
>Level 1/168 Walker St.
>North Sydney
>NSW, 2060
>Australia
>T +61 412 390 267
>M + 61 412 390 267
>E jocelyn.dart at sap.com
>http://www.sap.com
>
>The information contained in or attached to this electronic transmission
>is confidential and may be legally privileged. It is intended only for
>the person or entity to which it is addressed. If you are not the
>intended recipient, you are hereby notified that any distribution,
>copying, review, retransmission, dissemination or other use of this
>electronic transmission or the information contained in it is strictly
>prohibited. If you have received this electronic transmission in error,
>please immediately contact the sender to arrange for the return of the
>original documents.
>Electronic transmission cannot be guaranteed to be secure and
>accordingly, the sender does not accept liability for any such data
>corruption, interception, unauthorized amendment, viruses, delays or the
>consequences thereof.
>Any views expressed in this electronic transmission are those of the
>individual sender, except where the message states otherwise and the
>sender is authorized to state them to be the views of SAP AG or any of
>its subsidiaries. SAP AG, its subsidiaries, and their directors,
>officers and employees make no representation nor accept any liability
>for the accuracy or completeness of the views or information contained
>herein. Please be aware that the furnishing of any pricing information/
>business proposal herein is indicative only, is subject to change and
>shall not be construed as an offer or as constituting a binding
>agreement on the part of SAP AG or any of its subsidiaries to enter into
>any relationship, unless otherwise expressly stated.
>
>
>-----Original Message-----
>From: sap-wug-bounces at MIT.EDU [mailto:sap-wug-bounces at MIT.EDU] On Behalf
>Of Susan R. Keohan
>Sent: Tuesday, 13 December 2005 3:27 AM
>To: SAP Workflow Users' Group
>Subject: SRM Badi N-step
>
>Hello all,
>
>Can anyone verify that the N-step BAdi (BBP_WFL_APPROV), used in
>conjunction with the SAP-delivered
>Shopping Cart Approval Workflows (WS14000133, WS14000134) will allow you
>to accomodate parallel
>approval branches ? The BAdi allows you to set 'Approval_Branch', but I
>see nothing in the actual
>approval task to deal with dynamic parallel table processing. Of
>course, this would be easy enough
>to implement... I just wondered if the functionality was there 'out of
>the box'.
>
>Thanks
>Sue
>
>
More information about the SAP-WUG
mailing list