Ansicht
Dokumentation
OHADOE597 - BAdI: Check Data Records of IT0699 at Start/End of Prohibited Activities
Vendor Master (General Section) ROGBILLS - Synchronize billing plansThis documentation is copyright by SAP AG.
Business Add-In (BAdI) HRPAYDE_MUSCHG_BV_P0699 checks if the data record is available for the start or end of the split periods in accordance with the prohibited activities in infotype Pension Provision Act (0699). This check is relevant for the data records of infotype German Pension Reform D (0699) with at least one financing type of the regular ER/EN module.
To do this, you use method PRUEFEN_P0699_IM_MONAT_BV in interface IF_HRPAYDE_MUSCHG_BV_P0699 (check IT 0699 in the case of prohibited activities with a mid-month start or end).
This method checks the financing type of the employer and the employee from the regular payments (field Financing from table T5DR4 (AVmG: Characteristics of the Modules), see also AVmG: Set Up Modules in Customizing). If at least one financing type of the regular ER/EN module is found and if subapplication MGBS (Adjustment of AVmG Statement Wage Types in Fictitious Calculation MBV2) has been activated, the validity of the data record is checked. If the infotype record of infotype German Pension Reform D (0699) covers the period of prohibited activities, it is relevant for the distribution of the AVmG wage types. Otherwise, the "Infotype 0699 must be processed manually" warning message is still issued.
The infotype records of infotype German Pension Reform D (0699) only financed by one-off ER benefits or with just a remuneration conversion from a one-off payment are removed from the validity check at the start/end of prohibited activities and remain irrelevant for the automatic distribution of AVmG wage types.
If you want to see an error message or no message instead of a warning in the payroll program, you can override these individually by creating a customer-specific BAdl implementation, whereby the class of the implementation inherits from the fallback class CL_HRPAYDE_MUSCHG_BV_P0699. In this customer-specific class, you can redefine the method SEND_MESSAGE_075 and depict the logic according to your requirements.
If you do not activate a customer-specific implementation, the system calls the methods of fallback class CL_HRPAYDE_MUSCHG_BV_P0699, which performs the standard checks described above. We recommend that you use the standard implementation of the BAdI.
Create a customer-specific implementation if the specifications provided in the standard SAP system do not meet your requirements.
For information about the implementation of BAdls within the framework of the enhancement concept, see SAP Library for SAP NetWeaver under BAdls Embedded in the Enhancement Framework.
The method PRUEFEN_P0699_IM_MONAT_BV for interface IF_HRPAYDE_MUSCHG_BV_p0699 contains the following parameters:
- IV_PERNR: Personnel Number
- IV_BEGDA: Start of payroll period
- IV_ENDDA: Payroll period Enda
- IS_MUSCHG_BV
- IT_WPBP: The WPBP data of the current payroll period
- IT_P0699: Infotype 0699 German Pension Reform D (0699)
- IO_MESSAGE_HANDLER: Instance of the message handler.
- ET_INTERVALLE_P0699: Data records with at least one ER module of infotype German Pension Reform D (0699).
- EV_IS_OK: Export Parameter. Indicates whether the method was executed without an error. If this parameter is initial, the system terminates further processing and displays the error messages of the message handler.
If you create a customer-specific implementation, make sure to set parameter EV_IS_OK to 'X' (ABAP_TRUE). Otherwise, the system assumes there is an error and aborts the processing. You can transfer error messages that occur during customer-specific processing to the calling routine by calling method IF_HRPBS00_MESSAGE_HANDLER~ADD_MESSAGE. In this case, you must set parameter EV_IS_OK to SPACE (ABAP_FALSE).
CL_GUI_FRONTEND_SERVICES - Frontend Services Vendor Master (General Section)
This documentation is copyright by SAP AG.
Length: 5098 Date: 20240523 Time: 224547 sap01-206 ( 88 ms )
