Ansicht
Dokumentation

PYXX_HRPAY00_NT_050 - BAdI: Authorization Check

General Data in Customer Master   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Business Add-In (BAdI) HRPAY00_NT_B_AUTH is used to carry out the authorization check for the processor and the administrator group. You can use your own implementation to make customer-specific changes to the default implementation delivered by SAP.

Tasks are assigned to a HCM localization, an area, and a subarea. The combination of these 3 criteria forms the filter value that determines the relevant BAdI implementation. The individual values are separated using the separator "/". The BAdI implementation then carries out an authorization check for the processor or the administrator group.

Filter */*/*, class CL_HRPAY00_NT_FB_AUTH)

In the standard system (SAP default implementation), the authorization check is done using class CL_HRPAY00_NT_FB_AUTH if no customer-specific class with a special filter value is found.

Process of default implementation delivered by SAP:

Method CHECK_AUTHORITY is called, which in turn calls further methods to allow special checks to be performed in the following sequence:

1. Method CHECK_WITH_PERNR

First of all, the system checks if the processor is authorized to display the master data with the personnel number linked to the task. The system also checks if the procesor has access to Organizational Assignment (infotype 0001) and Basic Pay (infotype 0008).

1. Method CHECK_CLUSR

The system then checks if the processor is not authorized as administrator at that time (Table T526_DELIMIT).

1. Method CHECK_CLGRP

As a last step, a check is carried out for the administrator group. The system checks if at least one administrator is authorized at this time for this administrator group. Table T526 and table T526_DELIMIT are evaluated.

If you only want to make a change for specific methods of the authorization check in your customer-specific class, you can derive the customer-specific class from the standard class CL_HRPAY00_NT_FB_AUTH and then redefine the method you wish to change.

If necessary, create your own BAdI implementation (CL_HRPAY00_NT_FB_AUTH) to create authorization checks that are different to the standard checks.

There are three active BAdI implementations with the following filter values:

01/ST/ELSTAM	Class ZCL_HRPAY00_NT_FB_AUTH_ELSTAM
01/ST/*	Class ZCL_HRPAY00_NT_FB_AUTH_ST
*/*/*	Class CL_HRPAY00_NT_FB_AUTH

For the following combination of HCM localization, area, and subarea, the BAdI implementation is used with the most suitable filter condition.

Combination	Most suitable filter	Class behind the BAdI implementation
01/ST/ELSTAM	01/ST/ELSTAM	ZCL_HRPAY00_NT_FB_AUTH_ELSTAM
01/ST/LSTB	01/ST/*	ZCL_HRPAY00_NT_FB_AUTH_ST
01/SV/EEL	*/*/*	CL_HRPAY00_NT_FB_AUTH

Comment: The two classes beginning with Z are fictitious customer-specific classes for this example.

BAL Application Log Documentation   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 4368 Date: 20240523 Time: 185819     sap01-206 ( 59 ms )