Hierarchy

⤷

⤷

IMG Activity
ID | /SAPSLL/BADI_CTRMM0A | BAdI to Control Interface Calls from Purchasing Documents (MM0A) |
Transaction Code | /SAPSLL/23000407 | (empty) |
Created on | 20060510 | |
Customizing Attributes | /SAPSLL/BADI_CTRMM0A | BAdI to Control Interface Calls from Orders (SD0A) |
Customizing Activity | /SAPSLL/BADI_CTRMM0A | BAdI to Control Interface Calls from Purchasing Documents (MM0A) |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | /SAPSLL/CTRL_MM0A_R3 |
Use
The Business Add-In (BAdI) that controls the transfer of purchasing documents is used in the SAP Compliance Management area of SAP Global Trade Services (SAP GTS).
You can use the BAdI to specify settings for the transfer of purchasing documents that lead to the structures of the standard interface between mySAP Enterprise Resource Planning (mySAP ERP) as feeder system and SAP GTS being filled. In this way, you can adapt document transfer for purchasing documents to meet your requirements and restrict the data volume to the minimum required.
If you use the Preference Processing service of SAP Risk Management in SAP GTS, you must be aware that restricting document transfer impacts the setup of the worklist of long-term vendor declarations on the vendor side.
Requirements
- You have set up system communication correctly.
- You have set up the technical activation for transfer of purchasing document.
Standard settings
- In the standard SAP system, the BAdI implementation is not active.
- The BAdI is intended for using multiple times. All activated implementations are called and executed
- The BAdI is filter-independent.
Activities
For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.
Siehe auch
The BAdI uses the interface /SAPSLL/IF_EX_CTRL_MM0A_R3. For more information, display the interface in the Class Builder.
Hinweis
The BAdIs to control the transfer of documents comprise the functional scope of function module EXIT_SAPLSLL_LEG_CDPIR3_001 from user exit enhancement project SLLLEG01 ab. Because the BAdIs will replace the user exits, we recommend converting to the BAdI technology in the medium term.
Example
Business Attributes
ASAP Roadmap ID | 257 | Create User Exits |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | POLLOCZEK | 20060510 |
SAP Release Created in | 700 |