Welcome to Amrit's World of SAP

  BADI is a kind of Enhancements ( We will use Customer namespace for enhancements using BADI ). BADI stands for Business ADD In’s. BADI is based on object Oriented Concept. In Object Oriented Concept, BADI mainly works on Classes and Interfaces. Important T Codes for BADI :- SE18 is the transaction code for BADI definition. In SE18 we just perform the definition part, which we do in Interfaces of OOPS concept. SE19 is the transaction code for BADI Implementation. In SE19 we perform the implementation part in the same way which we do in Classes of OOPS concept. Types of BADIs :- There are basically 2 types of BADI in SAP Classic BADI New BADI ( also known as Kernel BADI )

  Menu exit allows us to add menu items to the menu bar of SAP programs. For any SAP transaction, we see there are already a lot of menu bars present. Now, Suppose I have to add some addition menu items, then I can use Menu exits for the same purpose. We can perform Customer functionalities on these menu items. Note :- These menu items have function codes that begins with “+” ( a plus sign ). let’s take a requirement to understand this concept. Requirement :- We have a transaction code CAT2 which is used for timesheet. Now, we also have a transaction code CAT4 which is used for approving the timesheet. But, My Customer wants that there should be a menu bar on CAT2 transaction code and when I will click on that additional menu item, it should take me to the approve timesheet. Important Note :- Whenever you get any requirement for customer exit, it is always mandatory to check for its feasibility. Ways to find a Menu Exit :- Check for menu items

  We have discussed what are Customer Exit and their different types as well. Also, In the Previous parts we have seen how we can find the function Module Exit for our requirement through debugging. In this part, we will see how to find function module using another technique. Suppose, we want to find function module exit for our VA01 transaction code. Steps to find Customer Exit ( Function module Exit ) :- Step 1 :- Go to VA01 transaction code. Step 2 :- Click on system → status. Step 3 :- Copy the name of the program. Step 4 :- Now go to SE38 ( ABAP Editor ) transaction code and select the Attributes radio button. Step 5 :- Click on display, it will return you the package name. Step 6 :- Copy the package name and Go to SMOD transaction code. Step 7 :- Click on utilities → find. Click on execute button. We can see we have a lot of Customer Exit available here, which also contains the Customer Exit for out requirement which is Sold t

  Function module exit allows us to add code to our SAP Programs with the help of Function Modules. We can enhance our SAP programs using Function modules. Syntax :- For every Customer Exit we have a dedicated Syntax. CALL CUSTOMER-FUNCTION ‘three digit number’. the three digit number in the above syntax varies from 000 to 999. Example :- CALL CUSTOMER-FUNCTION ‘001’. let’s take a requirement first Requirement :- Go to VA01 ( Create Sales Document ) transaction code. Suppose, I have given this order type as OR and as soon as I press enter. I want my Sold to Party should be auto populated. Note :- For any function module exit, we need to check, is there any function module exit available which will fill our requirement. Finding Function Module Exit Using debugging :- Step 1 :- Go to VA01 transaction code. Step 2 :- Write /h and press enter → It will turn the debugging mode. Step 3 :- Now, again press enter and you will enter to