Skip to main content

Finding and Implementing SAP Customer Exits

SAP Customer Exit is a feature of SAP software that allows customers to add their own functionality to SAP programs without modifying the original source code. It provides a way to customize SAP software to meet specific business requirements without compromising the stability and integrity of the system.

Customer Exits are pre-defined locations within SAP programs where customers can add their own code. When the SAP program runs, it checks whether a customer exit exists at a specific point in the program, and if it does, the system calls the customer's own code to execute specific functionality. Customer Exit functionality can be developed using ABAP programming language, which is the programming language used in SAP.

By using SAP Customer Exit, customers can enhance standard SAP functionality, automate specific business processes, and integrate with third-party software. Examples of SAP Customer Exit functionality include adding custom fields to SAP transactions, modifying standard SAP reports, and integrating with external systems.

SAP provides a range of Customer Exits that are available for customers to use, as well as documentation and support for developing custom Customer Exit functionality. Using Customer Exit functionality allows customers to tailor SAP software to meet specific business needs and improve overall system efficiency.

Finding SAP Customer Exits

Step 1: Go to SAP transaction code CMOD.


Step 2: Go to F4 option for the "Enhancement" field.


Step 3: Click on the button "SAP Application"


Step 4: A new window will open where we can find module specific or different SAP functionality specific customer exits here.


Step 5: Suppose we want check user exit for SAP production planning for process industries customer exits. So we have to expand PP-PI node. Now if we want to use the customer exit for process order material quantity calculation, we have to expand the node "PP-PI-POR" and then "COCR". We will find the user exit for the material quantity calculation here.


Step 6: Now click on display button if you want to check the details of the user exit.


Step 7: On the first screen, we will find the attribute details of the user exit.


Step 8: There is a function module assigned for this user exit. Double click on the function module to check the details.


Step 9: On the source code tab, there is a include where we can write our custom logic. We can also check the import, export and changing parameters from this screen.



Implementing SAP Customer/User Exits

Step 1: Go to SAP transaction code CMOD. Input a custom project name and then click on the create button.


Step 2: Provide short description for the project and then go to "Enhancement Assignment"


Step 3: A pop will come asking for saving the data. Choose "Yes"


Step 4: The project needs to be saved in a package. Provide a suitable package and press save button.


Step 5: List the required user exits in the following screen and press enter. Then go to "Components". Choose "Yes" if any pop up comes.



Step 6: Now we have to go to change mode of the following screen.


Step 7: An activate button will be visible. Click on this activate button to enable the user exit. There is a deactivate button to deactivate the exit any time.


Step 8: After activating the component, double click on the component.


Step 9: Go to the source code tab in the following screen.


Step 10: A warning message will come. Ignore the message by pressing enter. Choose "Yes" if the pop comes up.



Step 11: Input a suitable package name and press save button.


Step 12: Now write the required code to implement the user exit.












Comments

Popular posts from this blog

Adding New Input Fields to SAP Confirmations Screen (CO11N/COR6N) Without Coding

It is possible to add additional input fields in the SAP production order confirmation screen without coding. We can do this just adding fields to a structure which is included in AFRU table (Confirmation table). Process Steps Step 1:   Go to below customizing path. SIMG > Production > Shop Floor Control > Operations > Confirmation > Single Screen Entry > Define Single Screen Entry for Confirming Production Order Step 2:  Double click on the standard profile. Add "Customer Specific Fields of CI_AFRU" in the detail area. Step 3:  Go to default tab. Select an option from the "Customer Specific Fields" area. Then click on save button. Step 4:  Go to transaction code "SE11". Select database table and put "AFRU" and click on change button. Step 5:  Go to the include marked in the screenshot and double click on the data element of the include. Step 6:  Double click on "CI_AFRU". Step 7:  Click on "Yes" in the pop u...

SAP Production Order Confirmation Table List

SAP Production Order Confirmation is a process that enables companies to confirm the completion of production orders in the SAP system. The confirmation process allows companies to track and manage the progress of production orders, as well as record the actual quantities of materials used and the time taken to complete the production order. Production order confirmation tables are listed here. AFFW                     Goods Movements with Errors from Confirmation AFFWPRO           Log of deleted AFFW entries AFRC                     Incorrect cost calculations from confirmation AFRD                     Default values for collective confirmation AFRH                     Header information for confirmation pool AFRH_DEL ...

SAP Quality Management Transaction Codes

 SAP Quality Management transaction codes are listed here. Quality Management General Transaction Code List T-Codes Function Q000 Quality management QA00 Quality inspection QA01 Create Inspection Lot QA01A  Create Inspection Lot QA02 Change Inspection Lot QA02A  Change Inspection Lot QA03 Display inspection lot QA05 Job planning: Periodic inspection QA06 Job overview: Periodic inspection QA07 Trigger for recurring inspection QA07L  Deadline Monitoring Log QA08 Collective Processing of Insp. Setup QA09 No. range maintenance for insp.lots QA10 Trigger automatic usage decision QA10L  Log for Automatic Usage Decision QA11 Record usage decision QA12 Change usage decision with history QA13 Display usage decision QA14 Change UD witho...