Only relevant for the Public Sector
From Release 4.6C, the child allowance is calculated directly in Payroll. The data relevant for the calculation of the child allowance is still maintained in the Child Allowance infotype (0118). However, since the child allowance amount is now calculated in payroll, the Definition of Child Allowance (0119) and Child Allowance D (0232) infotypes are no longer maintained. For data records with validity periods up to December 31, 1995, the child allowance amount is still read from the Definition of Child Allowance infotype (0119) in payroll.
The maintenance interface and the structure of the Child Allowance infotype (0118) have been changed. For a detailed description of the changed infotype and the new maintenance interface, see the SAP Library under Human Resources -> Payroll -> Payroll Germany -> Payroll for the Public Sector -> Calculation of Child Allowance .
The functions have been enhanced to include special rules for child allowance for challenged adult dependants . It is now possible to make a child allowance payment of 30DM. This child allowance amount is stored as the constant OKKGH in table T511P (Payroll Constants (Intl) ) and can be modified in line with legal changes.
If the legal person changes during a month with a payroll split, you must decide which of the two employers pays out the child allowance. If the Child Allowance D infotype (0232) was not changed, the second employer pays the child allowance. If the first employer paid the child allowance, it was necessary to delete the Child Allowance D infotype (0232) in the month of the change for the period in which the employee was employed by the second employer. From Release 4.6C, the procedure is the opposite. If the records for the Child Allowance infotype (0118) are not changed for any children, the first employer pays the child allowance. If the second employer pays the child allowance, the Child Allowance infotype (0118) must be deleted for each child in the month of the change for each period in which the employee was employed by the first (the previous) employer.
The Definition of Child Allowance (0119) and Child Allowance D (0232) infotypes are neither converted nor delimited. Apart from in a few exceptional cases, the existing data for the Child Allowance infotype (0118) is not changed. Delimitation and deletion of the Child Allowance infotype (0118) may only be necessary during a month if the legal person also changes within a month. For more information, see the documentation on conversion report RPU_UPDATE_IT118_46C.
The entitlement to child allowance was previously maintained indirectly using the Reason field in the Child Allowance infotype (0118). The key for the reason was stored in the Reason field. These keys could be stored in table T588 (Family Characteristics ) under the country modifier 01 and the characteristic type 7. It was also necessary to assign an internal key to each of these reasons. This internal key defined the entitlement to child allowance. The internal key 0 corresponded to no entitlement, 1 corresponded to a counted child, and 2 corresponds to a child. The entitlement and reason have now been separated and are stored directly in the Child Allowance infotype (0118). The internal keys assigned to the reasons must now be converted to the new Entitlement field.
Report RPU_UPDATE_IT118_46C converts the internal keys to the Entitlement field in the Child Allowance infotype (0118). This report must be run immediately after the upgrade to Release 4.6C.
The check report RPLKGPD0PBS calculates the child allowance amount using the new functions and based on the converted data. This amount is compared to the amount stored in the Child Allowance D infotype (0232). If the amounts differ, an error message is displayed. The check report basically checks whether the amount stored in the Child Allowance D infotype (0232) matched the determination reasons stored in the Child Allowance infotype (0118) before the upgrade.
Process schema for modification of child allowance functions for an upgrade to Release 4.6C:
The following steps must be carried out immediately before the upgrade. In any case, they must be carried out before master data maintenance and, in particular, before the payroll run.