Kontakt

Ansicht
Dokumentation

CNV_TDMS_HCM_TIME_COMP - Time comparison

CNV_TDMS_HCM_TIME_COMP - Time comparison

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

Purpose

The program provides the possibility of rapidly and safely checking the correctness of the time related results. For example after:

  • TDMS HCM data transfer
  • Changes of SAP-release,
  • Installation of SAP HCM support packages
  • Changes in the customizing

The program can be executed for three distinct scenarios.

1. Package Comparison

In this case the user specifies a TDMS HCM package. The comparison is then done between source system and receiver system used in the TDMS HCM transfer. The RFC connections are those used in that transfer. The personnel numbers are also taken from that transfer.

2. Single Comparison

Two options exist here.

  • Single comparison between two distinct personnel numbers in the same system. This can be useful, for example, in the case of having set up two personnel numbers in a test system with slight differences. After time related data is entered for both employees, the program then allows checking for differences of the time related results.
  • Single comparison between two distinct personnel numbers in separate systems

3. Mass Comparison

Different usages exist for mass comparison

  • Between personnel numbers in separate systems (if no RFC-connection is given, then the same system is used; in this case there will of course not appear any difference, but it allows seeing the time result).
  • Between personnel numbers before a change and after a change within the same system. In this case, the program is executed twice. In the first run, the time related result is stored in a cluster. Afterwards, some change may occur to the time data and an update is made. Now the program is executed again. In this second run, the old time data is read from the cluster and compared to the new time data. This allows determining the changes that occurred to the time data from which existed earlier.
  • It is also possible for the above comparison to be done with an RFC connection specified for the first run of the time data. In this case, the time data stored in the cluster is the one of the remote system.

For the output the following options exist:

  • The standard output shows pairs of personnel numbers used in the comparison. The system indicates whether the time dataof two such personnel numbers are identical or different. The user can click on such a pair and is shown an overview of the tables and structures stored. Again the system indicates whether the data in tables or structures are identical or different. The user can click on a particular table or structure. A detailed screen then shows the data of the selected table or structure.
  • If the user sets the "only differences" flag, then only pairs of personnel numbers are shown that contain differences. If a pair of personnel numbers contain differences, then only those tables and structures are shown that contain differences.
  • If the user specifies wagetypes to be compared, then the comparison is based only on the data stored in the time wage types table ZL, and only the specified wagetypes are compared.
  • A special list output is generated in the case of a particular combination of output options. This list shows only differences in table ZL with local and remote data combined into a single line. This output option is particularly useful when comparing very many personnel numbers. This list may also be downloaded as Excel.

The program may also be scheduled for batch processing, if a large amount of data is involved. Scheduling in batch processing makes sense particularly in the case of a special list output for a large number of personnel numbers.

Prerequisites

You must have a valid TDMS HCM package for a package-related comparison. In the case of a package-related comparison, the report has to be executed from the source or the receiver system. It should not be executed from the control system, if the control system is a system separate from the source or receiver system.

In the case of a single comparison or a mass comparison across systems, a valid RFC connection must exist.

In the case of a mass comparison across systems, the personnel numbers existing in the local system must also exist in the remote system.

Features

Selection

1. Package Comparison

The user specifies a TDMS HCM package. The personnel numbers are determined from the package. Equally, the RFC connections are taken from the package.

The periods to be compared can be specified explicitly. They may also be distinct in the source and receiver system. The user will specify a period for the source system, and the same period for the receiver system. The year fields will typically be left blank. If the user does not specify any periods at all, then the latest existing time periods per employee are used in the comparison.

2. Single Comparison

The user specifies two personnel numbers. If an RFC-connection is specified, then the comparison personnel number is taken from the remote system.

The periods to be compared can be specified explicitly. They may also be distinct in the source and receiver system. The user will specify a period for the source system, and the same period for the receiver system. If the user does not specify any periods at all, then the latest existing time periods per employee are used in the comparison.

3. Mass Comparison

The selection depends on the specific usage of mass comparison.

a) Direct comparison

The personnel numbers are determined using the usual selection criteria of the PNP logical data base. The selection is executed in the local system.

If an RFC-connection is specified, then the comparison is done between two distinct systems. The personnel numbers in the local and the remote system must be identical.

If no RFC-connection is specified, then the comparison will of course show no differences. For that reason, this option is only useful to display the time results themselves.

The user specifies the time period to be used in the comparison. Typically, the user will specify a period.If the user does not specify any periods at all, then the latest existing time periods per employee are used in the comparison.

b) Writing timeresults to the cluster

The personnel numbers are determined using the usual selection criteria of the PNP logical data base. The selection is executed in the local system.

If an RFC-connection is specified, the time results are read from the remote system. If no RFC-connection is specified, the time results are read from the local system.

The user specifies the time period to be stored in the cluster.The user will specify a period. If the user does not specify any periods at all, then the latest existing time periods per employee are used for storage in the cluster.

c) Reading time results from the cluster and comparison

The user specifies an existing cluster ID. The "left side" of the comparison are those time results stored in the cluster. For the "right side" of the comparison, the same personnel numbers are used as stored in the cluster. The comparison time periods are usually also those stored in the cluster per personnel number. However, the user can also explicitly specify period.

The system displays the period that is specified in the selection when writing time results to the cluster of the specified ID. In addition, the user can press a display-button. The system then shows the details of the personnel numbers stored in the cluster and the time periods per personnel number.

For the output options the following parameters exist.

  • The "only differences" flag: If this flag is not then, then all personnel numbers are shown in the output, and all tables and structures of these personnel numbers are shown. If this flag is set, then only those personnel numbers with differences are shown. Also, of these only the tables and structures containing differences are shown.
  • The wagetypes selection: If wagetypes are specified for the comparison, then only table ZL is used in the comparison. And of this table only the lines referring to the specified wagetypes are used in the comparison.
  • If the "only differences" flag is set in combination with the "one line" radio button and some wagetype selection, then a special list output is produced. This is also indicated by a read-only flag in the selection-screen.

Output

Depending on the output options specified in the selection screen, different data is shown.

The standard output is for the screen to show all personnel numbers used in the comparison. The system indicates whether pairs of personnel numbers being compared are identical or whether they contain differences. On the left side are the "local" personnel numbers, and on the right side are the "remote" personnel numbers. The user can click on such a pair. The user is then shown an overview of the tables and structures stored in the time results. The system indicates which tables and structures contain differences, which ones are identical, and which one are simply identical because they do not contain any data at all.

Depending on how the user selects tables or structures, the user is shown different details. The system may show details of the data stored in the tables or structures comparing local and remote personnel number. Or the system may show details of the data stored in the tables or structures only of the local personnel number or only of the remote personnel number.

When showing a comparison in the detailed screen, then for most tables or structures, the system first shows the local data, and underneath the system shows the remote data. If "double lines" comparison is selected, then a particular line of the remote data is shown underneath the same line of the local data (here "same" is derived from the key of the lines). Independently of single line or double line comparison, the system indicates with red, if there are differences. In addition, if a line only exists in the local system, this is indicated with an "L" in the first column. If a line only exists in the remote system, this is indicates with an "R" in the first column. If a line exists both in the local system and in the remote system, then this is indicated with an "M" (for "modified") in the first column.

The user can indicate in the selection screen that only differences are to be shown. In this case no pairs of personnel numbers are shown that do not contain any differences. If a pair of personnel numbers contain differences, then only those tables and structures are shown that contain differences.

The user can indicate in the selection screen that only certain wagetypes are to be compared. In this case, the comparison is based only on the data stored in the time cluster table ZL. And only the specified wagetypes are compared. (This may also be "*", in which case all wagetypes stored in table ZL are compared.)

A special list output is shown, if the user specifies in the selection screen the following combination for the output selection:

  • The "only differences" flag is set
  • The "one line" flag is set
  • A wagetype selection is done

If this combination of output options is specified, then a special list is generated. This list shows only differences in table ZL with local and remote data combined into a single line. This output option is particularly useful when comparing very many personnel numbers. This list may also be downloaded as Excel.

In the case of mass comparison in combination with writing time results to the cluster, no output is shown. Instead, only an information message is displayed indicating that results were written to the cluster.

Particular personnel numbers specified in the selection screen may not have time results for the specified periods. In this case, this information is provided to the user in the form of an error list. This error list is shown after leaving the normal output screen.

In the case of batch processing, the normal output is written to a spool request. A second spool request may be generated in case that the error list contains data. As a result, two spool requests may have to be checked to get the complete output of the batch processing.






PERFORM Short Reference   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 13623 Date: 20240531 Time: 040808     sap01-206 ( 298 ms )