Hierarchy

⤷

⤷

IMG Activity
ID | EHSH_POH_CHECK_AUTH | BAdI: Enhanced Authorization Check for Medical Data on Person |
Transaction Code | S_PEN_05000090 | (empty) |
Created on | 20050429 | |
Customizing Attributes | EHSH_POH_CHECK_AUTH | BAdI: Enhanced Authorization Check for Medical Data on Person |
Customizing Activity | EHSH_POH_CHECK_AUTH | BAdI: Enhanced Authorization Check for Medical Data on Person |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | EHSH_POH_CHECK_AUTH |
Use
This Business Add-In (BAdI) is used in the Occupational Health (EHS-HEA) component. With this BAdI you can enhance the authorization check of the person-related medical data by adding additional checks. The BAdI is called at the end of the function module EHS00_LB20_POH_CHECK_AUTH. This function module checks the authorization object C_EHSH_POH in the transactions EHSAMBTAET, EHSSERV, EHSTERM01, and EHSSERV50 in Occupational Health.
You can use the BAdI to make the authorization check more stringent and, for example, to restrict authorization for specific health surveillance protocols in the medical service (for example, using the authorization object C_EHSH_HSP). It is not possible to make the authorization check less stringent with this BAdI.
Requirements
Create your own implementation and adapt the methods of the implementation to fulfill your requirements.
Standard settings
The BAdI is not active in the standard system.
The BAdI is not filter-dependent and not for multiple usage.
Activities
After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.
If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:
- In the dialog box, enter a name for the implementation of the Add-In and choose Create.
The system displays the initial screen for creating Business Add-In implementations. - On this screen, enter a short description for your implementation in the Implementation Short Text field.
- If you choose the Interface tab, you will notice that the system has populated the Name of the Implementing Class field automatically, by assigning a class name based on the name of your implementation.
- Save your entries and assign the Add-In to a package.
- To edit a method, double-click its name.
- Enter your implementation code between the
method <Interface Name>~<Name of Method>.
andendmethod.
statements. - Save and activate your code. Navigate back to the Change Implementation screen.
Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not perform the following step: - Choose Activate.
When the application program is executed, the code you created is run through.
Example
Methods
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 |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | EHSH_POH_CHECK_AUTH | 0 | AHR0000431 | Occupational Health |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20050429 |
SAP Release Created in | 600 |