Hierarchy
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials⤷
EHS-SAF (Application Component) Product Safety⤷
CBUI (Package) Company Environment Information System
IMG Activity
| ID | BADI_EHSS_AUTH_CHEK | BAdI: Additional Authorization Checks for Specifications |
| Transaction Code | S_EE6_85000066 | (empty) |
| Created on | 20100910 | |
| Customizing Attributes | BADI_EHSS_AUTH_CHEK | BAdI: Additional Authorization Checks for Specifications |
| Customizing Activity | BADI_EHSS_AUTH_CHEK | BAdI: Additional Authorization Checks for Specifications |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | BADI_EHSS_AUTH_CHECK |
Use
This Business Add-In (BAdI) is used in the Specification Management (EHS-BD-SPE) component.
You can use this BAdI to define additional authorization checks that the system performs when it accesses specification data.
Requirements
Standard settings
For more information about the standard settings (filters, single or multiple uses), see the Enh. Spot Element Definitions tab page in the BAdI Builder (transaction SE18).
The BAdI is not delivered with a default implementation.
The BAdI always uses the same instance within an internal session.
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.
Note
If you access specification data again from within the BAdI implementation (for example, using the specification API), this can result in an infinite loop if you do not include appropriate logic to prevent this in your implementation. Depending on the scope of the additional authorization check, we recommend that you save the result of the authorization check in a local buffer for performance reasons.
For more information, see the documentation for the example implementation CL_EXM_IM_EHSS_AUTH_CHECK.
Example
You can find the example implementations in the BAdI Builder on the Enh. Spot Element Definitions tab page in the Implementation Example Classes area.
The example implementations CL_EXM_IM_EHSS_AUTH_CHECK are available.
This example contains the following options:
- Determine the current change number and the key date in the BAdI
- Prevent an infinite loop
- Buffer the result of the extended authorization check
You can view the objects of this example class in the Class Builder transaction (SE24).
See also
The following methods exist for the different authorization objects:
- AUTH_CHECK_SHES_TRH
Authorization objects C_SHES_TRH and C_SHES_TR2
- AUTH_CHECK_SHES_TDU
Authorization objects C_SHES_TDU and C_SHES_TD2
- AUTH_CHECK_SHES_TST
Authorization objects C_SHES_TST and C_SHES_TS2
- AUTH_CHECK_SHES_TVH
Authorization objects C_SHES_TVH and C_SHES_TV2
These methods are called immediately after the authorization check of the respective authorization object.
You can use the AT_SAVE_CHECK method to run authorization checks when specification data is saved.
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| Mandatory / Optional | 3 | Nonrequired activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | BADI_EHSS_AUTH_CHECK | 0 | HLA0003436 | Specification Management |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20100914 |
| SAP Release Created in | 606 |
