EBP 4.0 N-Step Approval Problem / BUS2121 Extension

Martinek, Jerry Jerry.Martinek at icbc.com
Tue Sep 6 11:46:47 EDT 2005


Hi Jocelyn,

 

I sort of overlooked the fact that when you run BBP_PD_SC_GETDETAIL in
SE37, the default (non column) display truncates the fields in structure
e_item. 

 

Thank you for your help.

 

Jerry Martinek

 

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Dart, Jocelyn
Sent: Tuesday, September 06, 2005 2:52 AM
To: SAP Workflow Users' Group
Subject: RE: EBP 4.0 N-Step Approval Problem / BUS2121 Extension

 

Ok Jerry - Well your *HUGE* mistake was directly reading tables in SRM.
That's a no-no - why? Because of course if the shopping cart isn't saved
yet or you are in the middle of changing it all the "real" data is in
buffers and not yet actually in the database tables.  

 

Use BBP_PD_SC_GETDETAIL - that will correctly read the buffers or the
database tables depending on the situation/where the shopping cart is
currently.  

And yes the requirement tracking number *is* there it's BE_TRACKING_NO
in the item table. 

 

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 Martinek, Jerry
Sent: Saturday, 03 September 2005 10:07 AM
To: sap-wug at mit.edu
Subject: EBP 4.0 N-Step Approval Problem / BUS2121 Extension

Hi All,

 

It's Friday afternoon on a long weekend and I've run into a
user/developer error that I don't really know how to get around. 

 

I've extended BUS2121 by adding a new attribute (ReqTrackingNumber)
which is populated from table bbp_pdbei-be_tracking_no (linked to via
the guid from table crmd_orderadm_i). The actual field is called
'Requirement Tracking Number' and in part of the 'Basic Data' screen. 

 

When tested using SWO1 it works as expected. When the SC is
'Ordered/Saved' it also works fine. However, on approval preview prior
for new or held shopping carts, the new attribute isn't being populated
because the BADI isn't deriving the correct approvers. It appears the
new code isn't being executed. 

 

I'm guessing that the table entry isn't populated prior to the cart
being saved and that is why the role resolution logic isn't being
executed. Can someone help me by telling me where I can find this
information (requirement tracking number) prior to the cart being saved?
It's not available in BBP_PD_SC_GETDETAIL.

 

Thanks,

Jerry Martinek  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20050906/82cfe620/attachment.htm


More information about the SAP-WUG mailing list