Hello Experts,
How can the issues related to User exits in MV45AFZB and MV45AFZZ be resolved?
Issues related to User exits in MV45AFZB and MV45AFZZ be Resolved?
Updated May 18, 2018
Comments
Recommended Posts:
- What is SAP SD?
- SAP SD Training Tutorials for Beginners
- SAP SD T-codes
- SAP SD User Exit for Billing Document
- SAP SD User Exits for Sales Order
- SAP Customer Down Payment Configuration
- SAP IS-Retail Module
- SAP Incoterms
- SAP SD Variant Configuration Steps
- SAP SD Credit Management Interview Questions
- Subcontracting Process In SAP SD
- Rebate Processing In SAP SD
- Difference Between Rebate And Discount
- Movement Type In SAP
- Debit And Credit Note in SAP
- Sales Documents List
- Intercompany vs Intracompany
- SAP SD Invoice Table
- SAP SD Certification & Course Fees
- SAP SD Interview Questions
×
When it is required to make changes at a function module interface or at the other sections of the source code which is used for the processing of sales document in a user exit, the call of the function module and the existing /ASP/ relevant source code in the user exit get shifted into an Include program which needs to be created and replaced by its corresponding Include statement, along with the other required changes. Because of this, the user exit does not need to be adjusted anymore. The user exit is a SAP object and can also include not/ASP/ relevant modifications in the case of more changes to the function module interface. But it is important that all changes should be carried out at objects of the /ASP/ development namespace.
In releases higher than 2.1, all calls of /ASP/ functions present in the user exits for the processing of the sales document and possibly more /ASP/ relevant source code are moved to Include programs and are replaced by their corresponding Include statements.
All the user exits which are yet not adjusted in Release 2.1 needs to get adjusted correspondingly, for an upgrade from Release 2.1 to a higher release.