Ansicht
Dokumentation

HRPAYAT_SV_2839 - BAdI: RPLGMBA0 - CHECK Implementation

BAL_S_LOG - Application Log: Log header data   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

With this Business-Add-In, you can replace any previous modifications to SAP standard coding by implementing the methods explained below.

BAdI method CHECK_SOLL_TAB_FOR_PERIOD is called in

CL_HRPAYAT_MB_VERG_SOLL_IST
IF_HRPAYAT_MB_VERG_SOLL_IST~VERGLEICH_SOLL_SOLL_PERNR

Lines:
151
MESSAGE e202 (hrpayat_mbgm) [GKK]
179
MESSAGE e202 (hrpayat_mbgm) [BVA]

Before the call, sy-subrc EQ 0 applies. This means that an entry was found in the target data set from an in-period that is not compatible with the currently processed payroll result (or mBGM record).
If method CHECK_SOLL_TAB_FOR_PERIOD is not implemented, the return code remains zero and error message e202(hrpayat_mbgm) is output: ("Target mBGM still exists for in-period &2.")
If this method is implemented and the return code remains zero, a user-defined error message can be included.
If the return code in the BAdI method is set to not equal to zero, no error message is output.

BAdI method CHECK_IST_TAB_FOR_PERIOD is called in
CL_HRPAYAT_MB_VERG_SOLL_IST
I2_PREAPRE_IST_TAB_VERG

Line:
1852
MESSAGE e013 (hrpayat_mbgm)

Before the call, sv_subrc EQ 0 applies. This means that the control record for the payroll area of the currently processed payroll result (or mBGM record) has already been closed with reference to the in-period and processing was continued.
If method CHECK_ABKRS is not implemented, the return code remains equal to zero, no error message is output and processing is continued anyway.
If method CHECK_ABKRS is implemented and the return code is set to unequal to zero, error message e013 (hrpayat_mbgm) or the message supplied in the BAdI is output.

BAdI method CHECK_ABKRS is called in
RPCGMBA0_FILE
FORM check_abkrs

Line:
1852
MESSAGE e013 hrpayat_mbgm)

Before the call, sv_subrc EQ 0 applies. This means that the control record for the payroll area of the currently processed payroll result (or mBGM record) has already been closed with reference to the in-period and processing was continued.
If method CHECK_ABKRS is not implemented, the return code remains equal to zero, no error message is output and processing is continued anyway.
If method CHECK_ABKRS is implemented and the return code is set to unequal to zero, error message e013 (hrpayat_mbgm) or the message supplied in the BAdI is output.

After you have called the IMG activity, proceed as follows:

1. In the following dialog box, enter in the field "Implementation" a name for the BAdI implementation and choose Copy.

If implementations have already been created for the BAdI, a dialog box with the existing implementations will be displayed. In this dialog box, choose Create.

1. In the corresponding field, enter a short text for implementation .
2. In the tab Propertiesenter filter properties - if this is a filter-dependent BAdI.
3. Choose the tab Interface.

The name of the implementing class is generated by the system based on the name of your impmlementation. You can change the name.

If the BAdI is a menu exit, the tab FCodes also appears.Enter a function here and, if necessary, additional data.

1. Save your entries and assign a package.
2. Position the cursor on a method. Call up the Class Builder by double-clicking it.
3. Between the statements method <Interface-Name>~<Name of Method>. and endmethod, enter the coding you request for the implementation.
4. Save and activate your coding, and navigate back to the screen Change Implementation.
5. Save on the screen Change Implementation.

Note: You can first create an implementation for the BAdI and then activate this later on. In this case, close the processing function at this time.

1. Choose Activate.

When the application program is executed, the coding you have created will be run.

rdisp/max_wprun_time - Maximum work process run time   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 4780 Date: 20240523 Time: 192041     sap01-206 ( 71 ms )