SRM WF help
Dart, Jocelyn
jocelyn.dart at sap.com
Thu Nov 10 18:18:51 EST 2005
Umm.. yes but watch it in SRM 4.0 and 5.0 as for some reason it can
short dump depending on your support pack. Something to do with a
formal/actual parameter conflict.
And you would need to add the relevant call to your custom function
module but yes that should work.
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: Friday, 11 November 2005 3:29 AM
To: SAP Workflow Users' Group
Subject: Re: SRM WF help
Jocelyn also pointed out a really cool feature which can save data in
the test data directory of
your function modules. You set the user PID BBP_TRACE to 'X'. Then,
any functions that call
BBP_TRACE_TESTDATA_CREATE will get their test data saved. I assume this
will work for custom
function modules as well, just insert a call to the above function and
populate it with the
parameters you want.
In our SRM 4.0 sandbox, we need to implement OSS Note 864462 (and
related notes) to get this to work.
Baunach, Natasha R wrote:
> Hi Rang Nat,
>
>
>
> In my opinion, the cleanest way to implement a BADI is to not write
the
> whole code in the BADI but rather call a custom function module
withint
> the BADI that will return the table of approvers. Something similar
to
> this. This would keep your BADI implementation clean and make the
code
> reusable. For example, I also call this function module in the
> DOC_CHECK badi (on Check or Order) to make sure that all required
> approvers are there and we're not missing any. If for example, a
> finance analyst is missing for cost center 32000, I give an error and
do
> not let order shopping cart (they still have an option of placing it
on
> hold). This eliminates the need to send it to Administrators.
>
> *------------------Shopping Cart
Approval------------------------------*
>
> WHEN c_shop.
>
> CALL FUNCTION 'Y_BBP_POPULATE_SC_WFL_APPROVER'
>
> EXPORTING
>
> object_id = object_id
>
> actual_approval_index = actual_approval_index
>
> TABLES
>
> approval_table = approval_table
>
> item_approval_table = item_approval_table
>
> item_approval_obj = item_approval_obj.
>
>
>
> You can set a break point on your function module in the BADI and
debug
> while you create your shopping cart (you can always create it from GUI
> as well, transaction codes are BBPSC01, 02, 03 for different create
> scenarios) or you can create your shopping cart through the web as you
> normally would and they debug function module on its own. I prefer
the
> latter since it is much easier. This way you won't have to recreate
> shopping cart over and over again since you would be able to debug
> function module with the same shopping cart number.
>
>
>
> As far as new workflow debugging tools go, I am personally not aware
of any.
>
>
>
> I hope this helps you a bit.
>
>
>
> Regards,
>
> Natasha
>
>
>
>
------------------------------------------------------------------------
>
> *From:* sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] *On
> Behalf Of *rang nat
> *Sent:* Thursday, November 10, 2005 4:35 AM
> *To:* SAP Workflow Users' Group
> *Subject:* SRM WF help
>
>
>
> Hi,
>
>
>
> i have couple of quetions...
>
>
>
> I have been working in r/3 workflows and ebp2.0 2-step workflow .and
>
> also worked on ebp3.5 but not yet in wf .
>
> I'm starting new projekt this week on srm4.0 version.
>
> How is the wf here is deifferent from earlier versions(ebp2.0).
>
> EBP2.0 does not even has approval preview ..
>
>
>
> Are there any new tools came in for debugging workflow online when
> creating shopping cart.
>
> How to debug n-step BAdi while creating shopping cart.
>
> Is this BAdI synchronized with SC txn.so that we can keep break points
> and debug OR
>
> Assyncronous and triggered based on saved event..
>
>
>
> please send me to my personal mail id,if you have any documents on
this.
>
>
>
> 1.BAdi implemetaion
>
> 2.Debugging EBP workflow..,If different from older version of
checkingl
> ogs...
>
> 3.Debugging BAdi while creating cart,if posible
>
>
>
> Your help will be greately appreciated..
>
>
>
> */"Dart, Jocelyn" <jocelyn.dart at sap.com>/* wrote:
>
> Hi rang nat,
>
> 1. EBP 2.0 - centuries ago! (well a couple of years at least) and
> doesn't have a BADI workflow
>
> 2. Did you have a question?
>
>
>
> 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 <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.
>
>
>
>
>
>
------------------------------------------------------------------------
>
> *From:* sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] *On
> Behalf Of *rang nat
> *Sent:* Thursday, 10 November 2005 5:06 PM
> *To:* SAP Workflow Users' Group
> *Subject:* RE: SRM BAdi-n step for Shopping Carts
>
> Hi Jocelyn,
>
>
>
> I can see that approval workflow restart when we change A/c assignment
> details or product category....This is happening as new shopping
> cart(new entries /v EBP2.0) has been creating in system for above
changes.
>
>
>
> Cheers
>
>
>
>
>
>
>
> */"Dart, Jocelyn" <jocelyn.dart at sap.com>/* wrote:
>
> No really you're ok Sue - the standard whole shopping cart BADI
approval
> workflow restarts as normal based on workflow security and what
changes
> were made. You shouldn't have to raise any special events for
approvers
> restarting based on rejection or change.
>
> The only event you may want to keep is your Profit Center event -
the
> trick with that however is it won't be enough to re-evaluate rules
on
> active work items - you also need to rerun the BADI to recalculate
the
> approvers and fill the workflow container appropriately. Otherwise
your
> new approvers may not be able to action the shopping cart
correctly.
>
> You might have to create a parallel workflow as well as using
> re-evaluate rules.
>
>
> 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 tho! ! se
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 Sue Keohan
> Sent: Wednesday, 02 November 2005 1:02 PM
> To: SAP Workflow Users' Group
> Subject: Re: SRM BAdi-n step for Shopping Carts
>
> Hi Jocelyn,
>
> I was thinking to raise custom events when master data on the R/3
side
> changes, for example, Profit Center, which usually means a re-org,
and
> in that case, new approvers. The Events under the workflow header,
> version dependent tab, would seem to be able to do this
'Reevaluate
> Rules of Active Workitems', but of course, seeing is believing.
>
> I am interested in whole Shopping Cart Approvals via the BAdi, not
Item
> Approval. So, for that part at least, pheww! As for the BAdi, it
may
> prove challenging, as our business process calls for certain
approvers
> (at 'level 1') to be able to 'restart' approvals at the point
where the
> last rejection occurred, or 'begin anew'. The BAdi would need to
take
> this into consideration. Looks like I have my work cut out for me.
>
> Best regards,
> Sue
>
>
> Dart, Jocelyn wrote:
>
>>Hi Sue,
>>You don't need to raise any special events to restart when the user
>>chang! ! es it.
>>The standard code will work out what happens next and whether to
remove
>>approval tasks from certain users based on what you send out in the
>>BADI.
>>So you just need to concentrate on getting your BADI code correct -
> i.e.
>>to say "who does it go to next".
>>
>>By the way, are you just looking at whole ShopCart BADI approval or
the
>>ShopCart Item approval?
>>It's a lot more complicated for ShopCart Item approval but I've just
>>done it at a customer with a hideously
>>complex business scenario, so should be able to answer any questions.
>>
>>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 otherwis! ! e 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 Baunach, Natasha R
>>Sent: Wednesday, 02 November 2005 8:01 AM
>>To: SAP Workflow Users' Group
>>Subject: RE: SRM BAdi-n step for Shopping Carts
>>
>>Sue,
>>
>>You are correct that the value in BBP_WFL_SECURITY is the key to
>>allowing/prohibiting changes to shopping carts during approvals (even
>>though they all use the same task). Please keep in mind that if the
>>value is set to 'not defined', SAP has added the code in the BADI
>>BBP_WFL_SECUR_BADI, implementation BBP_WFL_SECUR_BADI_S to change it
to
>>4 (I think it comes in as activated) which is equivalent to no changes
>>are allowed.
>>
>> if scenario is initial .
>> call function 'BBP_PDH_WFL_SECLEVEL_DB_GET'
>> exporting
>> iv_user = actual_user
>> importing
>> ev_sec_level = new_sec_level.
>>
>> if new_sec_level is initial.
>> new_sec_level = 4.
>> endif.
>> endif.
>> endif.
>>
>>I have never used Events to recalculate agents for active tasks. In
> our
>>current production system, the security level is set to "Low -
workflow
>>is always restarted when changes are made". So, if the requestor makes
>>any changes to the workflow, it is restarted so agents are
> recalculated.
>>I will look into Events during our upgrade and will leverage off
>>Ginger's presentations.
>>
>>Regards,
>>Natasha
>>
>>
>>-----Original Message-----
>>From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
> Behalf
>>Of Susan R. Keohan
>>Sent: Tuesday, November 01, 2005 12:41 PM
>>To: SAP Workflow Users' Group
>>Subject: Re: SRM BAdi-n step for Shopping Carts
>>
>>Hi Natasha,
>>
>>Thanks so much for all the info. Our current process does not call
> for
>>ad-hoc approvers, but I am
>>still hoping to take advantage of this functionality.
>>
>>Am I correct that the value in BBP_WFL_SECURITY (currently set to 'not
>>defined') would be the key to
>>allowing/prohibiting changes to S! ! hopping Carts, all using the
> same task
>>? Just re-stating in my own
>>words what I thought you said...
>>
>>Have you used Events to cause the recalculation of agents for active
>>tasks ? This could solve a lot
>>of our problems, where the Shopping Cart changes during the approval
>>process, and the wrong
>>approvers still have the 'old' approval task...(Ginger Gatling
> delivered
>>a great presentation on
>>this topic at the recent TechEd in Boston).
>>
>>Many thanks,
>>Sue
>>
>>Baunach, Natasha R wrote:
>>
>>
>>
>> >Hi Sue,
>> >
>> >I have implemented BBP_WFL_APPROV_BADI in our SRM 4.0 sandbox with
>> >different level of approvals and certain line items going to
different
>> >approvers. Hopefully, I can answer some of your questions.
>> >
>> >1. Yes, approval index must be incremented by 1. You can still have
>> >your ad-hoc appro! ! val steps between pre-defined approval steps
> assuming
>> >that you allow for ad-hoc approvers (you can disable this
>> >
>> >
>>functionality
>>
>>
>> >via BADI 'Allow Changes to Approvers' BBP_CHNG_AGNT_ALLOW.
>> >
>> >2. It is the same task that is used for approvals in all shopping
cart
>> >approval workflows available in SRM 4.0. The task is TS10008126.
>> >Whether or not an approver can change the cart during approval
process
>> >is determined by the settings at the role level. Go to transaction
>> >PFCG, input your role, hit display. Then go to Personalization tab
>> >
>> >
>>and
>>
>>
>> >look for personalization object key 'BBP_WFL_SECURITY'. During
>> >
>> >
>>runtime,
>>
>>
>> >this default can be overwritten in the BADI 'Authorization to Change
>> >During Approval' BBP_WFL_SECUR_BADI. So basically, i! f your
approvers
>> >
>> >
>>at
>>
>>
>> >different levels have different roles, you should be able to control
>> >change ability via this setting at the role level. If it is more
>> >complicated than that, then you will need to place your more
>> >
>> >
>>complicated
>>
>>
>> >logic in the BADI.
>> >
>> >BTW, I think that you can also use a different BADI to allow only
>> >certain fields to be changed. It could be applicable only to CUF's.
>> >
>> >
>>I
>>
>>
>> >have this requirement and will be looking into it shortly -- if a
user
>> >has finance approver profile, only allow them to change GL account
>> >assignment and nothing else; no changes are allowed for other
>> >
>> >
>>approver.
>>
>>
>> >I hope this helps.
>> >
>> >Natasha
>> >
>> >
>> >-----Original Message-----
>> >From: sap-wug-bounces at MIT.EDU [mailto:sap-wug-bounces at MIT.EDU] On
>> >
>> >
>>Behalf
>>
>>
>> >Of Susan R. Keohan
>> >Sent: Tuesday, November 01, 2005 6:56 AM
>> >To: SAP Workflow Users' Group
>> >Subject: SRM BAdi-n step for Shopping Carts
>> >
>> >Hi all,
>> >
>> >I am trying to embark on the implementation of BBP_WFL_APPROV_BADI
>> >
>> >
>>(SRM
>>
>>
>> >4.0). Have looked at all
>> >the notes, docu, sample implementations, etc.
>> >1) The docu for this BAdi says 'Note that there must be absolutely
no
>> >gaps in the approval steps and
>> >that approvers must be defined for every step.' I assume this means
>> >that the ApprovalIndex must be
>> >incremented from 0 by 1 with no gaps in it. Am I correct ! ! ? Or
does
>> >this mean that there can be no
>> >intervening steps *between* approval steps ?
>> >
>> >2) Is it possible to pass an approver an approval task, which also
>> >allows them to change the cart ?
>> > But other approvers (different approval levels) can only approve or
>> >reject? Can I determine
>> >which tasks the approvers can get and set that in the BAdi ?
>> >
>> >Obviously, I am an SRM novice and a BAdi novice as well, so any help
>> >
>> >
>>is
>>
>>
>> >greatly appreciated.
>> >Happy WF-ing,
>> >Sue
>> >
>> >
>>
>>
>>
> _______________________________________________
> 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
>
>
------------------------------------------------------------------------
>
> Yahoo! FareChase - Search multiple travel sites in one click.
>
<http://us.lrd.yahoo.com/_ylc=X3oDMTFqODRtdXQ4BF9TAzMyOTc1MDIEX3MDOTY2OD
gxNjkEcG9zAzEEc2VjA21haWwtZm9vdGVyBHNsawNmYw--/SIG=110oav78o/**http%3a/f
arechase.yahoo.com/>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
------------------------------------------------------------------------
>
> Yahoo! FareChase - Search multiple travel sites in one click.
>
<http://us.lrd.yahoo.com/_ylc=X3oDMTFqODRtdXQ4BF9TAzMyOTc1MDIEX3MDOTY2OD
gxNjkEcG9zAzEEc2VjA21haWwtZm9vdGVyBHNsawNmYw--/SIG=110oav78o/**http%3a/f
arechase.yahoo.com/>
>
>
>
>
------------------------------------------------------------------------
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
--
Susan R. Keohan
SAP Workflow Developer
MIT Lincoln Laboratory
244 Wood Street
LI-200
Lexington, MA. 02420
781-981-3561
keohan at ll.mit.edu
_______________________________________________
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