- BADI Definition or Implementation
- BADI's Type
- BADI's Scenario
- Identify Standard BADI's
- Steps to implement BADI
- Identify the all implementations of BADI
- User Exits and types of User Exits
- Steps to Implement User Exits
- Best Practices of Using User Exits
- User Exits vs BADI's and when to use which?
- Real-world Example of user exits in SAP SD/MM/PP
- Enhancing Standard SAP Functionality with user exits
- Customer Exits and its types
- Identifying Customer exits
- Implementing Customer Exits
- Best practices for using customer exits
- Practical Example
- Troubleshooting common issues
- Comparing Customer exits with other Enhancement Techniques
- Real-Time Case Studies
- Enhancement Framework and its Types
- Enhancement Apportunities
- Implement Explicit Enhancements
- Working with Implicit Enhancements
- Understanding and Implementing BADIs in ABAP
- Enhancement spot and Enhancement implementation
- Tools of Enhancement Framework and Transactions
- Advance topics in the Enhancement framework
- Case Studies and real-life examples
- Introduction Enhancement Spot and Types
- Ways to Finding Enhancement Spots
- Creating an Explicit Enhancement Spot
- Implementing Enhancements using Enhancement Spot
- Managing enhancement implementations
- Advance topics in Enhancement Spots
- Best Practices for using Enhancement Spot
24ENHANCEMENT2909 – Customer Exits and its types
Customer Exits in SAP allow customers to enhance the functionality of SAP standard applications without modifying the original code. SAP provides predefined hooks or enhancement points where custom code can be inserted. Unlike modifications, customer exits are more upgrade-friendly and help preserve the integrity of SAP systems during updates.
Types of Customer Exits:
- Function Module Exits:
- These exits allow you to plug custom logic into a standard SAP function module.
- SAP defines a function module with an EXIT_ prefix, and you can insert your code into it.
- Example: EXIT_SAPLV60B_001 allows you to modify billing data during the creation of billing documents.
- Screen Exits:
- These exits allow you to add custom fields to standard SAP screens.
- SAP provides empty sub-screens in standard programs where custom fields or additional UI elements can be added.
- Example: Adding custom fields to the vendor master screen in MM using screen exit SAPMF02K.
- Menu Exits:
- Menu exits allow you to add custom menu items to the standard SAP GUI menu.
- These custom menu options can trigger additional reports, transactions, or custom logic.
- Example: Adding a custom menu option to the Material Management transaction MM01.
- Field Exits:
- Field exits allow custom validation or logic to be added to individual fields on an SAP screen.
- This is useful for enforcing custom business rules for specific fields during data entry.
- Example: Adding custom validation for material codes in MM01 when users input a value into the material field.
How to Implement Customer Exits:
- Find Exits: Use transaction code SMOD to locate customer exits.
- Create a Project: In CMOD, create a project and assign the desired customer exits.
- Write Custom Code: Implement custom ABAP code in the function modules associated with the exits.
- Activate the Project: Activate the project in CMOD to apply your changes to the SAP system.
Customer exits are a powerful tool for enhancing SAP’s functionality while maintaining system integrity during updates and ensuring custom solutions are efficient and tailored to business needs.
Author : Aniket Pawar, 9373518385
24ENHANCEMENT2909 – Customer Exists and its types
Customer Exits in SAP allow customers to enhance the functionality of SAP standard applications without modifying the original code. SAP provides predefined hooks or enhancement points where custom code can be inserted. Unlike modifications, customer exits are more upgrade-friendly and help preserve the integrity of SAP systems during updates.
Types of Customer Exits:
- Function Module Exits:
- These exits allow you to plug custom logic into a standard SAP function module.
- SAP defines a function module with an EXIT_ prefix, and you can insert your code into it.
- Example: EXIT_SAPLV60B_001 allows you to modify billing data during the creation of billing documents.
- Screen Exits:
- These exits allow you to add custom fields to standard SAP screens.
- SAP provides empty sub-screens in standard programs where custom fields or additional UI elements can be added.
- Example: Adding custom fields to the vendor master screen in MM using screen exit SAPMF02K.
- Menu Exits:
- Menu exits allow you to add custom menu items to the standard SAP GUI menu.
- These custom menu options can trigger additional reports, transactions, or custom logic.
- Example: Adding a custom menu option to the Material Management transaction MM01.
- Field Exits:
- Field exits allow custom validation or logic to be added to individual fields on an SAP screen.
- This is useful for enforcing custom business rules for specific fields during data entry.
- Example: Adding custom validation for material codes in MM01 when users input a value into the material field.
How to Implement Customer Exits:
- Find Exits: Use transaction code SMOD to locate customer exits.
- Create a Project: In CMOD, create a project and assign the desired customer exits.
- Write Custom Code: Implement custom ABAP code in the function modules associated with the exits.
- Activate the Project: Activate the project in CMOD to apply your changes to the SAP system.
Customer exits are a powerful tool for enhancing SAP’s functionality while maintaining system integrity during updates and ensuring custom solutions are efficient and tailored to business needs.
Author : Aniket Pawar, 9373518385