BBP_DOC_CHECK_BADI Enhancement

[Former Member]

Hi,

I am a SAP MM consultant, haven't been used with SRM. For an adhoc requirement in my project, i am taking care of an enhhancement that has to be performed in SRM during SC & PO creation.

In the ERP system we have a Z field, identifying a special business status for a Vendor, if this check is flagged we need to populate a Message in the SRM web portal.

After discussing with few of my colleagues & surfing in the net, i came to know about the "BBP_DOC_CHECK_BADI " which can serve my purpose.

But I am not sure when this BADI is triggered in BBPSC01 and BBPPO01 transactions. Need to whethet this BADI is triggered when press the "Order or Check button".

Though we can find this by debugging, it has become difficult are creating a SC or PO in EBP back end system looks very complicated and also not sure how to debug from the SRM webportal. FYI, we are using SRM with MDM catalouge.

System Version : EBP 4.0 , SRM 3.0.

So it would be great if some can provide me any of the following informations....

1. Point of triggering of the BADi in BBPSC01 and BBPPO01 transactions.

2. How to create a SC or PO directly in an EBP back end system.

3. How to start debugging from SRM web portal.

Regards,

Murali

Edited by: Murali Mani on Sep 1, 2009 9:33 PM

[Former Member]

Hi Murali,

Using the ITS based transactions directly in the SAP GUI can be a real challenge I'll admit...it is possible, you just have to scroll all around the screens to fill in the blanks. One thing that might help is to create a cart using the browser, put it on hold then go into BBPSC01 (you probably already know you must clear the gui screen of any menus with /n) and look for old purchase orders and templates and select that one. Play time is required because detailed instruction beyond that would require a lot a space.

But as the prior post says you can also definitely debug from the browser. Using SE19 for the BADI implementation, in the Utilities > Setting > ABAP Editor > Debuggin menu make sure you have external debugging set to on for the debugging user. Then when you set the breakpoint in the BADI make sure you choose "HTTP Breakpoint" at the prompt. Note that unfortunately this doesn't always work and occasionally will cause a short dump under some circumstances.

These document BADIs are called whenever you do a check or hold or order.

In terms of the message etc, you can definitely do that probably by making an RFC call to the ECC backend to check the value for the selected vendor, then throwing the complaint via the BADI.

Good Luck!

Cheers,

[Former Member]

Hi Murali,

Its a bit complicated to create SC from EBP backend. You can easily create a SC from the SRM portal.

You can debug from SRM portal as well. Login with the same id in portal and EBP backend system. go to se18 and put a breakpoint in the implementation that you have created for "BBP_DOC_CHECK_BADI".

Note that the breakpoint shoud be a external breakpoint and not a session breakpoint and also ensure that you have logged in into portal and backend with the same id.

The BADi gets triggered when you click on check or order. Along with this it is also triggered when you change the screen.

So this BADi is triggered multiple times.

Hope i answered you question.

Regards,

Zubair.

[Former Member]

Hi,

Thanks for the information. I have a quick question here, we are currently using SRM 3.0 with the back end EBP 4.0, so is debugging in the front end is possible in this version or is it possible only in a ECC system.

Regards,

Murali Mani

[Former Member]

Hi,

You should be able to debug through the SRM web portal by applying the HTTP break point in the BADI implementation.

P.S. BBP_DOC_CHANGE_BADI is called when you make changes in the SC data(almost everytime).

BBP_DOC_CHECK_BADI is called when you click on the "CHECK' button on the SC screen.

BR,

Deepti.

[Former Member]

Hi Deeptin,

Thanks for your info...... But unfortunately still my previous question is not answered ......

Regards,

Murali M