Ansicht
Dokumentation

RPSPAYDE_REGISTERZENSUS - Create Registry Census

RPSPAYDE_REGISTERZENSUS - Create Registry Census

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

Purpose

This program creates the XML files that are required by payroll offices in accordance with the RegZensErpG (Registry Census Test Law) for census key date May 15, 2022.

Integration

Prerequisites

The following settings must be made before the program run:

Setting Up a Record Type

Enter the characteristics for the record type you want to use in table T77PAYDE_ZENS1 (Registry Census: Assignment of Characteristics to Record Type). The Characteristic Group field usually remains empty and is only to be filled for characteristics that are assigned to a characteristic group (PARTNER or KINDER). The correct description of the record type for the characteristic group KINDER is added dynamically in report processing. Since the program is required once in 2022, the period from January 1, 2022 to December 2022 can be used as a sample delimitation.

Setting Up a Reporting Unit

In table T596M (using view V_T596M), use subapplication ZENR (registry census) to create an entry for each payroll office (usually one). For the period of 2022, choose a reporting personnel area/subarea that you can later assign to the personnel subareas stored in the system.

The eStatistic ID and the Reporting Unit ID to be stored, as well as the record type to be used (and previously to be maintained) must be maintained in the lower area in the Census Information group box.

Use the settings options in tables T596L and T596N to assign your personnel areas and subareas to the defined reporting personnel area/subarea.

Adjustment of BAdI methods for filling the data fields

The data fields related to the record type are filled using the HR master data provided in the standard SAP system, which means that an adjustment is only necessary if you deviate from this or want to fill additional data fields.

To do this, you must first create an enhancement implementation for enhancement spot HRPAYDE_ZENSUS (individual overriding of census) (transaction SE19). Choose a name (for example: ZHRPAYDE_ZENSUS) and a short text.

For each required BAdI definition (selection according to input help), create an implementation and an implementing class. For the sample class, you can choose to inherit from the existing class CL_HRPAYDE_ZENS_FB_... . As a result, only the methods that are to receive customer-specific source code must be redefined.

Setting the Download Directory

To store the files on the application server, maintain logical file name HR_DE_DIR_RPSPAYDE_REGISTERZENSUS using transaction FILE.

Features

The program creates one or more XML files for each payroll office, which then have to be sent to the Federal Statistics Office. The data is obtained primarily from the Personal Data (0002) and Addresses (0006) infotypes and, if required, from the Family/Related Person infotype (0021) for partners and children. It is possible to use BAdIs to deviate from the standard method for determining data fields or to supplement them with additional, customer-specific master data.

Selection

The Personnel Number field is available as a preselection for test purposes or to exclude individual employees. Further selections can be added if required.

In the Platform group box, you can choose whether the XML files generated are to be stored on the application server or on the local computer.

You can create a detailed log by selecting the corresponding checkbox in the Program Control group box.

The Actual Delivery checkbox in the same group box results in a live snapshot of the data. Without this switch, files are also generated, but they contain a flag as a test file and can be sent to the Federal Statistics Office for auditing purposes.

Standard Variants

Output

If you select the Create Log checkbox, a hierarchical list with the contents of the individual data records is added to the log output, which always contains the error messages, the report statistics, and the list of files generated.

Activities

Example






rdisp/max_wprun_time - Maximum work process run time   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 5196 Date: 20240520 Time: 102529     sap01-206 ( 95 ms )