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/LCLIC_COMM_O | BAdI: Send Licenses |
| Transaction Code | /SAPSLL/36000026 | (empty) |
| Created on | 20060720 | |
| Customizing Attributes | /SAPSLL/LCLIC_COMM_O | BAdI: Send Licenses |
| Customizing Activity | /SAPSLL/LCLIC_COMM_O | BAdI: Send Licenses |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /SAPSLL/ECMC_OUT |
Use
You can use the Business Add-In (BAdI) for the dispatch of licenses in the following areas of SAP Global Trade Services (SAP GTS), where the license technical object models several different business objects:
- Import/export licenses in SAP Compliance Management
- Securities for transit procedures and import customs processing in SAP Customs Management
- Authorizations in SAP Customs Management
- Securities and export licenses in SAP Risk Management - Restitution
- Letters of credit in SAP Risk Management - Letter of Credit Processing
The BAdI lets you use data from the licenses and prepare them for dispatch, because the licenses are integrated with the Post Processing Framework, and the BAdI is called in this context. You set up your customer-specific communication with external systems, to dispatch electronic messages, in this BAdI. SAP does not provide any programs for establishing communicator or sending license data at this juncture. Depending on which form of electronic communication you want to set up for licenses, you can configure any further processing of the license data provided in this BAdI.
You configure the dependent settings of the PPF actions for sending licenses in the following activities:
- Define Technical Medium for Messages (PFF Actions) of Licenses
- Define Condition/Output Parameter for Communication of Licenses
Requirements
Standard settings
In the standard system, there is no activated BAdI implementation.
The BAdI is designed for a single use. The activated implementation is called and executed.
The BAdI is filter-independent.
Activities
See also
The BAdI uses interface /SAPSLL/EX_IF_ECMC_OUT. 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 | 7.00 |
