Hierarchy
SLL-LEG (Software Component) SLL-LEG 901: Add-On Installation⤷
SLL-LEG (Application Component) Global Trade Services⤷
/SAPSLL/CORE_LEGAL (Package) Legal Services: Core Functions
IMG Activity
| ID | /SAPSLL/CUS_EVENTMGT | BAdI: Activation of Forwarding of Events to SAP Event Management |
| Transaction Code | /SAPSLL/24000018 | (empty) |
| Created on | 20100712 | |
| Customizing Attributes | /SAPSLL/CUS_EVENTMGT | BAdI: Activation of Forwarding of Events to SAP Event Management |
| Customizing Activity | /SAPSLL/CUS_EVENTMGT | BAdI: Activation of Forwarding of Events to SAP Event Management |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /SAPSLL/EM_CUS_DOC |
Use
This Business Add-In (BAdI) is used in the SLL-LEG-CUS component for customs declarations for imports and exports with Customs Management in the system for Global Trade Services (GTS).
The BAdI lets you activate the use of SAP Event Management (SAP EM). When you activate it, you enable the system to supply the event handler in SAP EM with events from customs import and export declarations through an interface that you can call through a Remote Function Call (RFC). This lets you track events from the customs declarations directly in SAP Event Management. You define in Customizing which events you want to list in SAP EM.
You can also use this BAdI to evaluate new and existing information from the customs declarations that trigger a call to SAP EM. Based on this comparison, you can decide whether you want to execute the call immediately or to reduce or extend the information that you pass on to SAP EM.
The BAdI is filter-dependent. The filter value corresponds to the type of business process in SAP EM. You can define which type of business process you assign to a document type in the definition of document types in Customizing of the GTS system. The system can then collect the events from GTS documents for each business process type in SAP EM.
Requirements
To use the functions in SAP EM, you also have to configure the following settings:
- In addition to the basic activation through the BAdI, you can also specify activation for each document type for customs import and export declarations. To do so, set the activation indicator in the document type definition for customs declarations in Customizing activity Define Document Types for Application Areas.
- Define the scenarios for tracking in the GTS system. To start the Customizing activities for integrating SAP EM with the system and its processes, choose Integration with Other SAP Components -> Interface to Event Management
- Configure system communication with the SAP EM system in your GTS system. You configure these settings in Customizing under Global Trade Services -> System Communication and in the area menu of the application under System Administration -> System Communication.
- In addition to the settings in your GTS system, you also have to configure intersystem communication and configure the scenarios in the system with SAP EM.
For more information about SAP EM, the integration of systems, and the corresponding settings, see the SAP Library under SAP Business Suite -> SAP Event Management.
Standard settings
- The standard system contains the BAdI implementation /SAPSLL/EM_CUS_DOC_IMPL (Implementation: Interface to SAP Event Management). If you activate the implementation, the default coding is executed automatically.
- The BAdI does not support multiple implementations. You can use the provided implementation or replace it with your own implementation.
- The BAdI is filter-dependent.
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 interface /SAPSLL/IF_BADI_CUS_DOC. For more information, display the interface in the Class Builder.
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 | SAP | 20120920 |
| SAP Release Created in | 900 |
