SAP creates customer exits for specific programs, screens and menus within standard SAP system. There four type of exits in SAP: Menu Exits, Screen Exits, Function Module Exits, and Field Exits.
There are mainly two reasons why we need to use user exits in SAP System:
- We should use them because they do not affect the SAP source code but still allow us to change the functionality of SAP to suit user requirements. SAP has provides us with some standards user exits that we should modify by adding our own functionality to them. The code and screens we created are encapsulated as separated objects.
- And since, they do not affect the source code and are named as per SAP naming conventions; they do affect future software upgrades. Hence we do not to save them and then reenter add-ons attached exits.
We can only use SAP customer exits if they already exist within the SAP R/3 system. In case we do not find a suitable exit for an area where we would want to make a change, then we should request SAP to develop a user exit.
A user exit is a place in a software program where a customer can arrange for their own tailor-made program to be called. In R/3, some user exits use Include statements to include customer program enhancements that are called from the program. Other user exits use tables that are accessed through customization.
User exits (Function module exits) are exits developed by SAP. The exit is implemented as a call to a function module. The code for the function module is written by the developer. You are not writing the code directly in the function module, but in the include that is implemented in the function module.
The naming standard of function modules for function module exits is:
EXIT_
The call to a function module exit is implemented as:
CALL CUSTOMER.-FUNCTION <3 digit suffix>
Sales related exits
Customer exits (CMOD transaction)
| Enhancement code | Description |
| SDAPO001 | Activating Sourcing Sub item Quantity Propagation |
| SDTRM001 | Reschedule schedule lines without a new ATP check |
| V45A0001 | Determine alternative materials for product selection |
| V45A0002 | Predefine sold-to party in sales document |
| V45A0003 | Collector for customer function modulepool MV45A |
| V45A0004 | Copy packing proposal |
| V45E0001 | Update the purchase order from the sales order |
| V45E0002 | Data transfer in procurement elements (PRreq., assembly) |
| V45L0001 | SD component supplier processing (customer enhancements) |
| V45P0001 | SD customer function for cross-company code sales |
| V45S0001 | Update sales document from configuration |
| V45S0003 | MRP-relevance for incomplete configuration |
| V45S0004 | Effective type in sales order |
| V45W0001 | SD Service Management: Forward Contract Data to Item |
| V46H0001 | SD Customer functions for resource-related billing |
| V60F0001 | SD Billing plan (customer enhancement) diff. to billing plan |
Include routines reserved for customers (need a modification key)
| Include | Description |
| MV45ATZZ | For entering metadata for sales document processing |
| MV45AOZZ | For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. |
| MV45AIZZ | For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). |
| MV45AFZZ and MV45EFZ1 | For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. |
No comments:
Post a Comment