Hierarchy

⤷

⤷

IMG Activity
ID | /SAPSLL/BADI_IFEMM0A | BAdI for Mapping and Enrichment of Data from Purchasing Documents (MM0A) |
Transaction Code | /SAPSLL/23000408 | (empty) |
Created on | 20060510 | |
Customizing Attributes | /SAPSLL/BADI_IFEMM0A | BAdI for Mapping and Enrichment of Data from Purchasing Documents (MM0A) |
Customizing Activity | /SAPSLL/BADI_IFEMM0A | BAdI for Mapping and Enrichment of Data from Purchasing Documents (MM0A) |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | /SAPSLL/IFEX_MM0A_R3 |
Use
The Business Add-In (BAdI) for adjusting purchasing document data is relevant for the areas SAP Compliance Management and SAP Risk Management - Preference Processing of SAP Global Trade Services (SAP GTS).
You can use the BAdI to edit the result of the standard mapping of purchasing documents before they are transferred to the interface. For areas based on the customs document of SAP GTS, you can also transfer customer-specific data to the enhanced interface. In this way, you can enhance the customs document in SAP GTS.
Requirements
- You have set up system communication correctly.
- You have set up the technical activation for the transfer of purchasing documents and the transfer control options for purchasing documents.
Standard settings
- In the standard system there is no active BAdI implementation.
- The BAdI is intended for use multiple times. All activated implementations will be 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.
There are BAdIs available in the Implementation Guide of SAP GTS to enable you to receive and use customer-specific data in SAP GTS. For SAP Compliance Management, you can find the relevant BAdI under SAP Compliance Management -> Business Add-Ins for SAP Compliance Management and then under the enhancement spot -> Transfer External Data to Customs Document.
See also
The BAdI uses the interface /SAPSLL/IF_EX_IFEX_MM0A_R3. For more information, display the interface in the Class Builder.
Note
The BAdIs for editing the mapping for document transfer comprise the functional scope of function module EXIT_SAPLSLL_LEG_CDPIR3_002 from user exit enhancement project SLLLEG01, and also offer extended structures for customer data. 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 |