Purpose
You use this report to convert your system to Unicode for the followingapplication areas:

• Payroll Austria


• Absence valuation for all countries using the XNAB function to refine
absences, and have implemented the EXIT_SAPLHRTIM00COV_HIST_004enhancement (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 themarking).

Integration
The following example of Austrian payroll illustrates the necessity of aconversion.
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 anddata of type X or P in a Char25 field. This initial technical situationcauses great problems in the conversion to Unicode, because thealignment of data based on the DDIC definition assumes the values arecharacter type, and not of type X. The tables must therefore beconverted.
The system uses the redefinition structure PTADC internally for theconversion.
Necessity of conversion
If the tables were not converted, it could cause the following problemswhen the data is processed again in payroll or other reports:
A runtime error may occur when data is imported by the program.
Data loss and incorrect results may be caused.
The data may be set to initial in part by the system. For example, anabsence may suddenly have 0.00 absence hours instead of the correct 7.5hours. In this case, payroll would valuate the absences incorrectly andso determine incorrect values for payments and deductions.

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

Features
Test run parameter
You can run the report initially in a test run. The system does not makeany 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 relevantclient in the client parameter.
If you want to run the conversion of cluster PC for individual personnelnumbers and calendar years first, enter the required personnel numbersand calendar years in the selection screen.
If none of the selection paramters are filled, the conversion is run forall clients and all existing records on cluster PC (table NCALE orCOVER) and cluster RA (payroll results for Austria).
Identification of data already converted
You cannot tell from the change to the version number whether the datawas already realigned. The version number does not change, because notall customers will convert their system from non-Unicode to Unicode.
Only the system can determine during import by the IMPORT command thecode page information under which the data was stored on the cluster. Itthen compares this information with the code page valid in the system.It then converts the data or excludes it from the conversionaccordingly.
Refinement of absences: Conversion of the COVER table
If you use the XNAB
or GPNABfunction in payroll for valuating absences, the COVER table on the PCcluster is filled. The COVER table contains a 100-character markerfield, to store absence markers. This report first checks whethernon-character-type values are also written to the marker field. This canhappen 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 theCOVER table on the PC cluster of PCL1 (and, in particular, use theEXIT_SAPLHRTIM00COV_HIST_004 enhancement), you have to declare aredefinition structure in the HRTIM_UCCONV_COVER Business Add-In (BAdI).This applies regardless of whether you fill the COVER table withnon-character-type values or not. If the redefinition structure does notexist, 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 forsocial insurance as of position 10.
You now have to create a DDIC structure that reflects exactly thestructure of the markers. Note: The structure must not be a deepstructure.
The standard system already contains the PTADC redefinition structurefor the conversion of the CHAR25 field of the NCALE table. You can useit as a model structure.
After creating the DDIC structure, return it using theHRTIM_UCCONV_COVER BAdI. If you run payroll in more than one countryversion in your enterprise, you will most likely have to return the DDICstructure separately for each country grouping, since the rules forabsence valuation usually differ according to the country version.
This report analyzes your DDIC structure and determines whether thisredefinition structure is Unicode-critical, that is, contains data oftype X or P.
If so, the report converts the COVER table with the structure youspecified in the BAdI. If no conversion is necessary because the DDICstructure you specified does not contain any critical data types, thereport saves the COVER table unchanged.

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