Hierarchy
⤷ PY-XX-RS (Application Component) Reuse Services for Country Development
⤷ P99D (Package) Human Resources Department: Cross-Country Objects Germany
IMG Activity
ID | OHADUM0005 | BAdI: Authorization Check Using Transaction Code and Personnel Area |
Transaction Code | S_L4H_49002414 | (empty) |
Created on | 20110921 | |
Customizing Attributes | OHADUM0004 | BAdIs for Authorization Check |
Customizing Activity | OHADUM0005 | BAdI: Authorization Check Using Transaction Code and Personnel Area |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | HRPAY00_B_AUTH_WERKS |
Use
The BAdI is called in reports for which a personnel area/subarea can be used for the authorization check. For example, the authorization object P_ORGIN can be used, as in the implementation HRPAY00_AUTH_WERKS. To control the behavior of the BAdI separately for different reports, the ID (consisting of program ID, object type, and object name) that is transferred when the BAdI is called can be used.
The following reports call the BAdI:
Report Report Name Program ID Object Type Object Name
RPCBDVD0_OUT Create Notifications for Company Data Maintenance R3TR PROG RPCBDVD0_OUT
RPCBDLD0 Administrator List for Notifications for Company Data Maintena R3TR PROG RPCBDLD0
RPCBDLD0_DISPLAY Display of Business Data Maintenance Notifications R3TR PROG RPCBDLD0_DISPLAY
RPCBDHD0_IN Import Notifications for Business Data Maintenance R3TR PROG RPCBDHD0_IN
RPCBDHD0_OUT Create Notification Files for Business Data Maintenance R3TR PROG RPCBDHD0_OUT
Requirements
Standard settings
The authorization object S_TCODE is checked. The parameters transferred for personnel area/subarea are ignored. If the authorization object P_ORGIN is to be used for the authorization check, the enhancement implementation HRPAY00_AUTH_WERKS must be activated. Alternatively, a separate enhancement implementation can be developed and activated.
Activities
Example
If the authorization check is not to be executed for reports that use the BAdI, a new custom BAdI implementation can be defined. This does not need to contain any source code other than the method body. Since an exception is never triggered in this case, the authorization check grants authorization in all cases.
Business Attributes
ASAP Roadmap ID | 209 | Establish Authorization Management |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | I | Valid for countries specified |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20110921 |
SAP Release Created in |