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/CUSIBD_CHECK | BAdI: Check During Creation of Customs Decl. before GR and Pre-Declaration |
| Transaction Code | /SAPSLL/51000019 | (empty) |
| Created on | 20081125 | |
| Customizing Attributes | /SAPSLL/CUSIBD_CHECK | BAdI: Check During Creation of Customs Decl. before GR and Pre-Declaration |
| Customizing Activity | /SAPSLL/CUSIBD_CHECK | BAdI: Check During Creation of Customs Decl. before GR and Pre-Declaration |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /SAPSLL/CIBD_CUHD_PERMIT |
Use
This Business Add-In (BAdI) is used in component SLL-LEG-CUS for customs management in SAP GRC Global Trade Services.
It lets you define additional checks for creating customs declarations prior to goods receipt. This means you can define the exact conditions that a transaction has to fulfill before a customs declaration can be created. Every logistics transaction that appears in the overview for creating customs declarations can generally be used to create a customs declaration.
If you want to define other conditions for creating a customs declaration, you can define them in the BAdI. The conditions could include the existence of a required document, for example, or check whether a service provider has furnished all the necessary information. As soon as the entry in the overview for creating customs declarations meets a defined condition, the user can create the desired customs declaration prior to goods receipt.
You can describe the reasons why the customs declaration cannot be created in custom error messages, to support users who try to create a customs declaration prior to goods receipt, but cannot because a condition is not met. The system prevents the creation of customs declarations when system errors from types E, A, or X occur. If you use system messages with type S and I, users can still create the customs declarations; the messages are displayed for information only.
Requirements
Standard settings
- In the standard system, there is no activated BAdI implementation.
- The BAdI is designed for multiple use. All activated implementations are 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 interface /SAPSLL/IF_CIBD_CUHD_PERMIT. 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 | 800 |
