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/BADI_CASETYP | BAdI: Determine the Case Type in Case Management |
| Transaction Code | /SAPSLL/51000005 | (empty) |
| Created on | 20080709 | |
| Customizing Attributes | /SAPSLL/BADI_CASETYP | BAdI: Determine the Case Type in Case Management |
| Customizing Activity | /SAPSLL/BADI_CASETYP | BAdI: Determine the Case Type in Case Management |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /SAPSLL/CASE_TYPE_GET |
Use
This Business Add-In (BAdI), which lets you an alternative case type in Case Management, is used in the following areas of SAP GRC Global Trade Services:
- Releasing blocked business partners after SPL screening
- Product classification in Customs Management and Compliance Management
- Release of customs documents blocked due to blocked business partners, an embargo situation, or a missing license for a product that requires a license
If you use Case Management for the above areas, you can use this BAdI to define which case type is used in a decision case involving a document release, a partner release, or product classification. You have assigned general properties to each case type in Customizing, such as different authorization profiles for each case type. In the standard settings, the system determines the case type from your default data settings in Case Management. If you want to use more parameters to determine the case type dependent on the assigned authorizations, you can use this BAdI to determine these parameters.
Requirements
You have defined the case types that the BAdI can determine as alternative case types in Customizing for case types, under Cross-Application Components -> General Application Functions -> Records and Case Management -> Case -> Case Type.
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_CASE_TYPE_GET. 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 | 20120924 |
| SAP Release Created in | 800 |
