Hierarchy
SLL_PI (Software Component) GTS Plug-In⤷
SD-FT (Application Component) Foreign Trade⤷
/SAPSLL/PLUG_IN_R3 (Package) Legal Services: PI Functions and PI Services
IMG Activity
| ID | /SAPSLL/BADI_CTRSD0C | BAdI to Control Interface Calls from Billing Documents (SD0C) |
| Transaction Code | /SAPSLL/23000418 | (empty) |
| Created on | 20060512 | |
| Customizing Attributes | /SAPSLL/BADI_CTRSD0C | BAdI to Control Interface Calls from Billing Documents (SD0C) |
| Customizing Activity | /SAPSLL/BADI_CTRSD0C | BAdI to Control Interface Calls from Billing Documents (SD0C) |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /SAPSLL/CTRL_SD0C_R3 |
Use
The Business Add-In (BAdI) for controlling the transfer of billing documents is used in the areas SAP Customs Management and SAP Compliance Management of SAP Global Trade Services (SAP GTS).
You can use the BAdI to specify settings for the transfer of billing documents. These settings 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 billing documents to suit your requirements and reduce data volume to a minimum.
Bear in mind that SAP GTS uses the billing document as the basic document for various services SAP GTS and that your filter settings affect all activated services in SAP GTS. For example, customs processing in SAP Customs Management or preference processing in SAP Risk Management are based on the billing document.
Requirements
- You have set up system communication correctly.
- You have set up the technical activation for transfer of billing documents.
Standard settings
- In the standard system, there is no active BAdI implementation.
- The BAdI is intended for use multiple times. All active 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.
See also
The BAdI uses the interface /SAPSLL/IF_EX_CTRL_SD0C_R3. For more information, display the interface in the Class Builder.
Note
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 | 20060512 |
| SAP Release Created in | 700 |
