Kontakt

Ansicht
Dokumentation

RPUCCONVCL - Unicode Conversion PCL2 and PCL1 Cluster PC (Table NCALE, COVER)

RPUCCONVCL - Unicode Conversion PCL2 and PCL1 Cluster PC (Table NCALE, COVER)

ROGBILLS - Synchronize billing plans   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

You use this report to convert your system to Unicode for the following application areas:

  • Payroll Austria
  • Absence valuation for all countries using the XNAB function to refine absences, and have implemented the EXIT_SAPLHRTIM00COV_HIST_004 enhancement (Determine Markers for Absences).

You convert the following files:

  • Payroll results from cluster RA on file PCL2 (table ABP)
  • Personal calendar from cluster PC on file PCL1 (table NCALE for Austria)
  • Table COVER from cluster PC on file PCL1 (provided the XNAB function is used, the EXIT_SAPLHRTIM00COV_HIST_004 enhancement has been implemented, and a critical structure in view of Unicode has been used for the marking).

Integration

The following example of Austrian payroll illustrates the necessity of a conversion.

Initial situation

In the process of Unicode conversion, data is imported and converted. The converted data then has to be stored on the cluster again.

Cluster PC of the PCL1 file contains the table NCALE (National Calendar) with the DDIC structure PCNAT. The system stores character-type data and data of type X or P in a Char25 field. This initial technical situation causes great problems in the conversion to Unicode, because the alignment of data based on the DDIC definition assumes the values are character type, and not of type X. The tables must therefore be converted.

The system uses the redefinition structure PTADC internally for the conversion.

Necessity of conversion

If the tables were not converted, it could cause the following problems when the data is processed again in payroll or other reports:

  1. A runtime error may occur when data is imported by the program.
  2. Data loss and incorrect results may be caused.
    The data may be set to initial in part by the system. For example, an absence may suddenly have 0.00 absence hours instead of the correct 7.5 hours. In this case, payroll would valuate the absences incorrectly and so determine incorrect values for payments and deductions.

Prerequisites

You have made a backup copy of the PCL1 and PCL2 files before starting the conversion.

Features

Test run parameter

You can run the report initially in a test run. The system does not make any changes to the database in a test run.

All other parameters

The other parameters are used to restrict the selection.

Examples:

If you want to run the conversion for each client, enter the relevant client in the client parameter.

If you want to run the conversion of cluster PC for individual personnel numbers and calendar years first, enter the required personnel numbers and calendar years in the selection screen.

If none of the selection paramters are filled, the conversion is run for all clients and all existing records on cluster PC (table NCALE or COVER) and cluster RA (payroll results for Austria).

Identification of data already converted

You cannot tell from the change to the version number whether the data was already realigned. The version number does not change, because not all customers will convert their system from non-Unicode to Unicode.

Only the system can determine during import by the IMPORT command the code page information under which the data was stored on the cluster. It then compares this information with the code page valid in the system. It then converts the data or excludes it from the conversion accordingly.

Refinement of absences: Conversion of the COVER table

If you use the XNAB or GPNAB function in payroll for valuating absences, the COVER table on the PC cluster is filled. The COVER table contains a 100-character marker field, to store absence markers. This report first checks whether non-character-type values are also written to the marker field. This can happen in the following situations:

  • In the standard development for your country
  • In the HRPTIMAB SAP enhancement (Absence Refinement), which you customized to suit your requirements

If non-character-type values exist, the system converts the COVER table.

If you use the HRPTIMAB SAP enhancement (Absence Refinement) to fill the COVER table on the PC cluster of PCL1 (and, in particular, use the EXIT_SAPLHRTIM00COV_HIST_004 enhancement), you have to declare a redefinition structure in the HRTIM_UCCONV_COVER Business Add-In (BAdI). This applies regardless of whether you fill the COVER table with non-character-type values or not. If the redefinition structure does not exist, the report terminates processing.

Example:
You have implemented a marker algorithm that stores the absence type, duration, or other information at a fixed position in the marker field, for your company-specific rules. For example, information relevant for social insurance as of position 10.
You now have to create a DDIC structure that reflects exactly the structure of the markers. Note: The structure must not be a deep structure.
The standard system already contains the PTADC redefinition structure for the conversion of the CHAR25 field of the NCALE table. You can use it as a model structure.
After creating the DDIC structure, return it using the HRTIM_UCCONV_COVER BAdI. If you run payroll in more than one country version in your enterprise, you will most likely have to return the DDIC structure separately for each country grouping, since the rules for absence valuation usually differ according to the country version.

This report analyzes your DDIC structure and determines whether this redefinition structure is Unicode-critical, that is, contains data of type X or P.

If so, the report converts the COVER table with the structure you specified in the BAdI. If no conversion is necessary because the DDIC structure you specified does not contain any critical data types, the report saves the COVER table unchanged.

Additional information

The report may have to be extended at a future date to encompass the conversion of payroll results of other countries. For more information, see SAP Note 573044.






CPI1466 during Backup   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 6960 Date: 20240601 Time: 060044     sap01-206 ( 92 ms )