|Home • Trainings • Quiz • Tips • Tutorials • Functional • Cert Q's • Interview Q's • Jobs • Testimonials • Advertise • Contact Us|
BADI implementation for transaction CS01
By Sakthivelan .T and Thrinath Kumar .K, Kaavian Systems
create a BADI implementation for CS01 transaction, that does not allow user to
create alternative BOMs for already created BOM.
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.
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
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.
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.
Please send us your feedback/suggestions at webmaster@SAPTechnical.COM
©2006-2007 SAPTechnical.COM. All rights reserved.
product names are trademarks of their respective companies. SAPTechnical.COM
is in no way affiliated with SAP AG.
Graphic Design by Round the Bend Wizards