Hierarchy
SLL-LEG (Software Component) SLL-LEG 901: Add-On Installation⤷
SLL-LEG (Application Component) Global Trade Services⤷
/SAPSLL/LEGAL_CON_CORE (Package) Legal Services: Legal Control - Basic Functions
IMG Activity
| ID | /SAPSLL/CON_BAD_LCRL | BAdI: Release Blocked Documents |
| Transaction Code | /SAPSLL/04000055 | (empty) |
| Created on | 20040709 | |
| Customizing Attributes | /SAPSLL/CON_BAD_LCRL | BAdI: Release Blocked Documents |
| Customizing Activity | /SAPSLL/CON_BAD_LCRL | BAdI: Release Blocked Documents |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /SAPSLL/CUHD_RELEASA |
Use
This Business Add-In (BAdI) is used in the Legal & Logistics Services (SLL) component of SAP Global Trade Services (SAP GTS). You can use this BAdI to perform actions for released documents, in addition to updating the worklist for the follow-up functions in the ERP system.
You can also change or reduce the number of licenses displayed (license master records) to manually assign export or import licenses.
General Information on Releasing Documents
If you have configured checks for feeder system documents in your SAP GTS system, the system performs these checks when you save a document in the feeder system. For example, you may have activated the following checks for feeder system documents:
- SAP Customs Management
- Sanctioned party list screening
- Embargo check
- Check for export or import licenses
- SAP Risk Management
- Checks for letter of credit processing
- Checks for restitution
If one of the checks for a document in SAP GTS produces a negative result, the system blocks this document in the feeder system to prevent further processing. As a result, a goods receipt cannot be posted for an inbound delivery in ERP.
In SAP GTS, specific users are authorized to release these blocked documents under certain circumstances to enable further processing. When a user releases a document, SAP GTS determines the document references of the feeder system document affected by the release and writes this reference to a worklist.
You can export the worklist automatically and trigger further processing of the released documents by running the corresponding report in the background with a batch job in each feeder system.
If you want to prevent the document release from being transferred to the feeder system for certain application levels or have to adapt the structure of the data (such as the document numbers of the feeder system) to the requirements of the feeder system, you can implement the document release methods for this BAdI.
For more information about the interface and methods for this BAdI, see the Interface Description.
Requirements
Standard settings
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.
Example
The system replicates sales documents in CRM as customs documents, for example, for the checks in SAP Compliance Management. Negative check results cause the document to be blocked. When a user with a special authorization profile releases a blocked document, the system does not immediately update the document status in the feeder system. Instead, it creates an entry in the worklist. You can manually run the report program /SAPSLL/CRM_ORDER_RECHECK or execute it in the background to examine the worklist and update the document status in the feeder system. In addition, the system performs the active checks in SAP GTS again to ensure that the documents have not been changed in the meantime. If there were no document changes, the system releases the blocked sales documents in CRM to enable further processing.
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 | 300_620 |
