Kontakt

Ansicht
Dokumentation

< ( RELNPY_DE_PS_46C_KG )

< ( RELNPY_DE_PS_46C_KG )

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

Changes to Child Allowance

Use

Relevant for the Public Sector Germany only.

From Release 4.6C, the child allowance is calculated directly in payroll with payroll program RPCALCD0. 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 the payroll program, the Definition of Child Allowance (0119) and Child Allowance D (0232) infotypes no longer need to be maintained. For data records with validity periods up to December 31, 1995, the payroll programs still reads the child allowance amount from the Definition of Child Allowance infotype (0119).

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 SAP Library under Human Resources -> Payroll -> Payroll Germany -> Payroll for the Public Sector -> Calculation of Child Allowance.

The functions for calculating child allowance have been enhanced to include the special rule for child allowance for challenged adult children. It is now possible to make a child allowance payment of 30 DM in such cases. This child allowance amount is stored as the constant OKKGH in view V_T511P (Payroll Parameters) and can be modified in line with legal changes.

If the legal person changes during a month with a payroll split, the question arises as to which of the two employers pays the child allowance for this month:

  • Previously, the following rule applied in the system: If the Child Allowance D infotype (0232) was not changed, the second employer pays the child allowance automatically. If the first employer was to pay the child allowance, the Child Allowance D infotype (0232) had to be deleted 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 is to pay 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 is employed by the first (previous) employer.

Effects on Existing Data

The Definition of Child Allowance (0119) and Child Allowance D (0232) infotypes are neither converted nor delimited for Release 4.6C. Except for a few exceptional cases, the existing data for the Child Allowance infotype (0118) is not changed. Only if the legal person changes in a month may it be necessary to delimit or delete the Child Allowance infotype (0118) during a month. For more information, see the documentation for the conversion report RPU_UPDATE_IT118_46C.

You previously maintained the employee's entitlement to child allowance indirectly by specifying a key in the Reason field. These keys were stored in table T577 (Family Characteristics) under the country modifier 01 and the characteristic type 7. An internal key also had to be assigned to each of these reasons. This internal key defined the entitlement to child allowance. The internal key 0 indicated no entitlement, 1 a counted child, and 2 a child.

With the changes in Release 4.6C, the entitlement is now separate from the reason (for the entitlement). You now maintain both values directly in the Child Allowance infotype (0118). Based on this change, the internal keys assigned to the reasons have to be converted to the new Entitlement field.

Effects on Data Transfer

Report RPU_UPDATE_IT118_46C (Adjust Infotype 0118 After Upgrade to Release 4.6 (Public Sector Germany) 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.

To check the converted data, you can use the check program RPLKGPD0PBS (Check Consistence of Child Allowance Data After Upgrade to 4.6C). This report 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 for a personnel number, an error message is displayed. The check program thus determines 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:

Carry out the following steps immediately after the upgrade to Release 4.6C. In all cases, you must make the adjustments before master data maintenance and, in particular, before the payroll run.

  1. Start report RPU_UPDATE_IT118_46C for the data conversion.
To be able to start this report, you require authorization group RPU_118 in the assigned role for authorization object S_PROGRAM. You can also start the report if '*' is entered as your authorization group.
For details on the conversion process, see the documentation for the conversion report RPU_UPDATE_IT118_46C. If this report runs without errors for all personnel numbers, the KGU indicator is set automatically in table T5D8R (Logging of Technical Conversions). If this indicator is not set, you can display but cannot change the master data in the Child Allowance infotype (0118).
If you have the authorizations specified above and want to start the report now, choose:
Start Conversion Report RPU_UPDATE_IT118_46C
  1. Check whether the conversion was successful.
You can check samples of the converted data using the check program RPLKGPD0PBS (Check Consistence of Child Allowance Data After Upgrade to 4.6C). For details on the check, see the documentation for report RPLKGPD0PBS.
If you want to execute the check report now, choose
Start Check Report RPLKGPD0PBS.
  1. If necessary, manually modify the personnel numbers containing errors, which were identified by the check report.

Effects on System Administration

Effects on Customizing

  • The automatic default functions have been modified and enhanced according to the changed Child Allowance infotype (0118). You can modify the return value of feature KG118, which controls the automatic defaults, in Customizing under Personnel Administration -> Child Allowance -> Set Up Automatic Default Settings.
  • If you want to use the special child allowance rule for challenged adult children, you have to copy the entry for constant OKKGH in view V_T511P (Payroll Parameters) to your production client.
  • In the standard system, the subschema ((Net Part Germany (SI, Tax, Guaranteed Net Amount)) of personnel calculation schema D100 contains the function DOKIG for the calculation of child allowance using data in the Child Allowance infotype. If you use your own subschema, include the call for the calculation of the child allowance at the end of your subschema before subschema DSTB (Tax (D) Calculation) is called.
Subschema DONT:
...
DOZV ERHB Increase amount (supplementary pension)
DOKIG   Calculation of child allowance
COPY DSTB Calculation of tax
BLOCK END

Further Information

  • You define the Customizing settings for child allowance as follows:
  • The infotype settings in Customizing for Personnel Management under Personnel Administration -> Payroll Data -> Child Allowance

  • The payroll settings in Customizing for Payroll: Germany under Industries -> Public Sector -> Child Allowance






BAL_S_LOG - Application Log: Log header data   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 10720 Date: 20240603 Time: 042912     sap01-206 ( 176 ms )