BADI implementation for transaction CS01

By Sakthivelan .T and Thrinath Kumar .K, Kaavian Systems

Aim: To create a BADI implementation for CS01 transaction, that does not allow user to create alternative BOMs for already created BOM.

Hint: If an alternative BOM is created the field STALT from MAST table will be increased by 1. We can control future creation of BOM using this field. Or if the particular material for which we are creating BOM has an entry in MAST then we should not allow to create again. So the Badi can be approached in two ways. But I use the former method in this example you try the latter method.   

Step1:

Keep a break point in “CALL METHOD cl_exithandler=>get_class_name_by_interface” line inside the get_instance method of the class cl_exithandler in Class builder (SE24).

Step2:

Now execute CS01 transaction, you will see the debugger that you set in SE24 transaction. Double click on the changing parameter “EXIT_NAME”. Press F8 sequentially and make a note of the exit names.

Step3:

After you see CS01 just continue with the BOM creation and in mean time note all the Exit names that you come through in the debugger.

Continue with BOM creation as follows.

Click here to continue..