Understanding and Implementing Classic BADI

 

  • SAP has provided us a class CL_EXITHANDLER for classical BADI purpose.
  • We will use GET_INSTANCE method of CL_EXITHANDLER class to find the classic BADI for our requirement.

Let’s take a requirement to understand it more clearly :-

Requirement :-

  • While creating a material through MM01 transaction code,





    • The Customer wants that if I am providing basic unit of measure as KG then I should get a error, when I click on save button.

Ways to find a Classical BADI :-

  • There are mainly three ways to find a Classical BADI , I will discuss the first one here and then I will discuss the rest of the two in the next part.
  • In this part, we will find our required Classical BADI through debugging.

Finding Classical BADI for the above requirement :-

  • Step 1 :- Go to SE24 transaction code and display class CL_EXITHANDLER → double click on GET_INSTANCE method.



    • Put a debugger as shown above.

  • Step 2 :- Now go to mm01 transaction code for our requirement.



  • Step 3 :- Click on save button → It will take you to the debugging mode.



  • Step 4 :- Whatever BADI is available in this program, you get in the variable EXIT_NAME, you just need to keep pressing F8.

    Note :-

    • Whatever BADI you will get here, you need to go to SE18 and check the BADI that it fits to your requirement or not.

  • Step 5 :- For the above requirement, the suitable BADI is given below.



    • In this BADI_MATERIAL_CHECK we have a dedicated method which we will use for our requirement.



Implementing Classic BADI for our requirement :-

  • Step 1 :- Go to SE19 transaction code and select Classic BADI radio button.



  • Step 2 :- Pass the name of the BADI that we have found above in the debugging and click on create button.



    • Provide a implementation name for our BADI.


  • Step 3 :- Click on the interface tab → The name of the implementing class will be appeared automatically.



  • Step 4 :- Double Click on the implementing class.



  • Step 5 :- Double click on the check data method to write the logic.

  • Step 6 :- In this method we have a table WMEINH, where we will find the entered basis unit of measure from MM01 screen, So, We can write our logic here.



    • Now, go back to BADI and activate the BADI first.


Testing the Implementation :-

  • Go to MM01 transaction code and fill the details.



  • Press enter and fill the rest of the details.



  • Click on save button.



  • We got the error message.

Note :-

  • After practice, always go back to the BADI and deactivate the BADI.



Comments

Post a Comment

Popular posts from this blog

Understanding Different Types of SAP Function Modules: Normal, RFC, and Update

Image
  1. Normal/Regular Function Module :- It can be called inside the system. Here Pass by value + Pass by reference both is fine. 2. RFC Function Modules :- You can call from same system or from another possible. In RFC function module you can only have pass by value. In the same system if you are going to add the DESTINATION NONE’ while calling the RFC then it’ll be called in separate session. 3. UPDATE Function Modules :- This is generally used to update the database record. Update Function Module can be called from the same system. ( Background RFC / trfc / grfc ) This is used to achieve generally the SAP LUW. Some time we use from performance perspective also. When COMMIT WORK gets executed then Update starts getting executed. Important Questions on Update Function Modules :- When Update function Module gets Triggered ? ON COMMIT WORK IF a update function module gets failed, under which transaction we can see that ? OR What is the T-Code for moni
Read more

Unlocking SAP ABAP Secrets: Interactive Classical Reports with GET CURSOR, At User Command, and a Comparison of HIDE Statements

Image
 Welcome back everyone, We were discussing about the interactive classical reports, so let’s continue it. Interactive Classical Reports- GET CURSOR :- In Interactive Classical Reports, GET CURSOR statement is used to create secondary list according to cursor position. The parameter FIELD provides the name of an output field. The parameter VALUE provide the output value. Syntax : GET CURSOR FIELD <lv_field> VALUE <lv_value>. In the above syntax - the field name and field value will be returned in to variables lv_field and lv_value respectively. Requirement :- If you remember, In our last two blog, We have been displaying the order header table in a basic list and order item table in the secondary list. We have used SY-LISEL and HIDE statements to achieve the requirement. Now, we have to use the get CURSOR to achieve the same to same requirement. Code :- ************************************************************* *Start of Program *Declaring Strcutrure
Read more

Mastering ABAP: A Step-by-Step Guide to Function Modules and Groups for Modularized Programming

Image
  Function Modules :- It is a modularization technique. The transaction code to create a function module is SE37. To create a function module, we need to create a function group. Function Group :- Function group is a container for the function modules. The transaction code to create a function group is SE80. A function group can store up to 99 function modules. Requirement :- let’s create a function module for sum of two numbers. 1. Creation of function group :- Step 1 :- Go to SE80 transaction code → Object Navigator. Step 2 :- From the drop down select function group. Step 3 :- Give a name of function group. Step 4 :- press enter. Step 5 :- Click on yes a popup screen will appear. Step 6 :- Give short description → press enter → Assign package and transaction request and press enter. Step 7 :- Right click on function group and click on activate to activate the function group. Step 8 :- You will see two includes, will be added after ac
Read more