Ansicht
Dokumentation

RPCJUDI0 - Report for CUD 2007 form management (Obsolete)

General Data in Customer Master   General Data in Customer Master  
This documentation is copyright by SAP AG.

Description

Program for CUD 2005 calculation.

For full documentation related to this program see SAP note no. 792875.

For sections unchanged comparing to previous years, specifications of SAP note 456456 are still valid.

The instructions for the user-exits for INPDAP relating to CUD 2005 are included in SAP note 813902.

Comparing to 2004, the form includes the following changes and improvements:

1. Part B: CUD 2004 boxes no. 70-74 are now boxes 71-75; as a result, the corresponding table codes have been changed;
2. Part C, Section 3: the new box 55 (Bonus L.243/2004) is included, and the relating record (wage type) can be entered in table V_T5ITW5;
3. Part C, Section 4: CUD 2004 boxes no. 55-60 are now boxes 56-61; wage type fields 58-61 and relating records in table V_T5ITW5 (select: Section 4-SOLA) are, as a consequence, identified through these numbers;
4. Part C, Section "INPDAP and IPOST Social Security and Welfare Data": box 61 ("Institution") is now box 107; the new boxes 103-105 include on hold salaries for 2002, 2003 and 2004 respectively; the new box 106 includes the trade union leave percentage. These new boxes are based on wage types values and you can valuate relating records in table V_T5ITW5, code number: 103-106.
5. Notes: CUD 2005 compels the obligation to identify each note through a specific code; when the program generates a note (similarly to the previous years), it also provides the new specific code relating to it. For further information, see SAP Note 792875.
6. New feature for boxes based on wage types values: you can assign field Sum / last of table V_T5ITW5 a new value.

Requirements

In order to use program RPCHUDI0 for CUD 2005 calculation, the following requirements must be met:

• The SAP system has calculated employees' payroll relating to full year 2004 and the results in cluster (RI/B2/PC) are consistent;

• Clusters RI/B2/PC have not been changed, but for payroll through program RPCALCI0

• Master data has not been changed without carrying out corresponding payroll (for example in info-types 0154, 0156 or 0160);

• If the SAP TM form is not in use, it is necessary to use interfaces and user exits in order to use report RPCHUDI0;

• It is important that function INAB is NOT set, so that the percentage "company benefit" is = 0 (when it should be 100%) -> section 3 of the form's social security section;

• This program should be run using the same value date set in cluster RI (calculation results): should that not be the case, the error due to rounding could be consistent.

In case you use the deferred month solution:

1. CUD 2005 tax part is based on the cash criterion; there is no inconvenience for the deferred month users;
2. CUD 2005 social security part is based on the accrual criterion; in this case, the contributions generated in the deferred month must be correlated to the previous month, not to the current;
3. Use passive wage types only (generated by program RPCALCI0 during normal/not deferred month in accordance with contributions due in that month); in this way, contributions and period will always be based on the accrual criterion.

In case you use RPCHUDI0 without SAP TM (Time Management):

All relevant boxes are filled using a layout interface.

File for calculation results overwriting:

After calculating each box value for the employee indicated in the initial selection screen, program RPCHUDI0 enables you to overwrite the value in each box for specific employees reading a layout file containing the new value and indication of the employee and of the box that should be changed;

Bitmap file:

With program RPCHUDI0 you can upload a bitmap file with the Euro sign for the first form page and a bitmap file with the employer's signature for the second page. These files are not provided by SAP but can be uploaded by the user through transaction SE78 as of release 4.6B. Uploaded and named objects (windows file ".bmp") can subsequently be called and entered in the relevant field in CUD 2005 form selection screen.

Output

Program RPCHUDI0 functionalities:

This program enables CUD 2005 form processing (personal details, tax section and INPS/INPDAI section of social security part).

It also enables the user to work on different 'depth levels', for example the "company" level, a generic level, or on 'deeper' levels, for example "INPS indicator" or "Workplace".

For boxes 19, 20, 21 of Part B of the form, the data produced by payroll function ITCAF is considered and amendments and integrations are supported, whether necessary.

User exits

For user exits activation, please see the dedicated chapter.

Interface files

Program RPCHUDI0 does not manage ALL possible circumstances that can occur for all employees for any type of company, therefore in some cases the use of output results change interfaces is required.

For employees undergoing company changes there are three scenarios (and relevant solutions):

1. Rehiring by the same company:
   The same PN must be kept;
   No change in payroll takes place;
   For CUD calculation this event's date is not important;
   The procedure requires the same treatment implemented in case of a hold on salary payment occurring once/several times in a year; the output will include normal splits of CUD 2005 form social security and SI sections; CUD refers to the whole period (year);
   The system supports this solution.
2. Company change due to collective operations:
   It can imply disappearance of the old company;
   It is currently not supported by the system.
3. Company change due to individual operations:
   Creation of a new PN and use of info-type 0305 as "previous employer" is required; this operation is possible only at the beginning of the month (first day of each month); it is also necessary to use info-type 0031 following changes' time series.
   CUD procedure implies a different CUD form for each employee; it usually involves two employees with a CUD form for the old company and a CUD form for the new company (the old company is the previous employer); in this case too there will be splits in the social security section and in the SI section;
   CUD refers to company period only (e.g.: a CUD for the old company January-April and a CUD for the new company May-December);
   As changes regarding this point are possible in the near future, we recommend you read the note before you make any changes;
   The system supports this solution.

Background processing:

A background run is possible with a layout file via transaction SE38 -> menu -> program -> run -> background.

Calculation description

Note 792875 describes the solution in detail, focussing on changes comparing to the previous year.

&User exits&

The different user-exits (INPDAP) available for CUD 2005 form are described in notes 813902 and 792875.

We recommend you read documentation relating to user-exits in the notes, as well as the documentation relating to transactions SMOD and CMOD used for user-exits activation.

In order to display user-exits documentation, call the transaction (for example CMOD) and, in the menu, Help-> Application Help, bearing in mind that their technical name is EXIT_RPCHUDI0_XXX.

Further notes

Ministerial guidelines that should be given the employee are not included in this program print, as they are the same for each employee.

For SAPScript format changes see notes 202204 and 306219. 2005 form name is HR_IT_CUD_2005. Note 581935 contains information on bitmap upload.

CAF-connected data: for documentation relating to this section, see notes 350082 and 337931.

As for settings, see the note 792875 chapter dedicated to this issue, explaining in detail how to set the system in the various form sections (for example, in the section relating to settlements or SI-indemnity data) and instructing on how to carry out settings for unchanged parts comparing to the previous year.

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 9010 Date: 20240520 Time: 133736     sap01-206 ( 169 ms )