Ansicht
Dokumentation

IUUC_RECON_F2F - IUUC: Reconciliation Field to Field Comparison

Vendor Master (General Section)   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Purpose

In the context of a Near-Zero-Downtime (NZDT) or an Incremental Upgrade and Unicode Conversion (IUUC) project data will be replicated (=delta replay) from one system (=sender) to another system (=target). The relevant tables are summed up in a mass transfer. The aim of the field to field comparison is to check whether the data between sender and target system is consistent by comparing the field values of the relevant tables with each other (= Verification of the delta replay). Note, in case the length of a field is different between source and target, e.g. by enlargement of the material number in case of a S4 conversion, the field values are excluded from comparison.

Integration

Prerequisites

Existence of a mass transfer, a sender and target system (inclusive RFC connections).

Features

Selection

Parameter area 'Selection'

Define the table set for which the field to field comparison is performed. You can choose between three different scenarios via a radio button. In scenario "Check all tables" first of all the field to field comparison is performed for all tables of the entered mass transfer. You can define filter options to check only tables with a special process option and/or table class. If you choose the "Check individual tables" scenario, you can define any set of tables to be processed. Do this via the select-option for table names. The third scenario is "Check transferred tables". A table that has been changed in the sender system and whose changes have been replicated in the target system (tables for which migration objects have been generated) is called a "transferred table". In this scenario you can optionally select a subset of all transferred tables by the select-option for table names.

Parameter area 'Settings'

Parameter "Selection Size (Rows)" defines the number of rows which will be checked in one portion. This setting can be set table specific in the Recon Monitor (see below).
If you want to check only sample date of each table, you can define the maximum records to be check for each table. In this case the comparison is stopped as soon as by the next portion the defined number of records is exceeded.
In order to parallelize change the parameter "Parallel Tasks" to the number of tasks you want to be started for the comparison processing. Note, that tasks are dialog work processes. Enough of them must be available in the application server.
Per default only those records will be checked which are part of the receiver logging table (only changed records). If you want to check the complete table you have to activate the Flag "Check Complete Table". In this case all records in the receiver system are checked.
If flag "Check Deletions" is active also records marked with last process option DELETE are check if they really don't exist in the sender and receiver system.
If you activate the flag "Check Keyfields only" the field to field check only compares the values of the key fields.

Parameter area 'Unicode Mode'

In case of a MDMP to Unicode conversion some records cannot be compared as the values are not converted back correctly from Unicode to MDMP. In this case the Unicode Conversion mode should be activated which provide additional parameters. If the Unicode Mode is active, field differences which occur due to character conversion errors (conversion error during RFC transfer from Unicode Receiver System to non Unicode MWB/Central System) are detected. If a record contains only difference due to conversion errors, the differences can either be ignored or displayed in a separate column. As the comparison of RAW fields between a non Unicode and a Unicode system normally leads to difference, you can also remove RAW fields from the comparison

Parameter area 'Execution Mode'

It is possible to either crate a Run ID or choose a existing one. For existing Run IDs you can start the check in execution mode restart, completed tables or completed portions of partly completed tables will not be checked again. If you start the program in execution mode rerun, the check results of the selected tables will be reset and the check is executed again.

Standard Variants

Output

Activities

Result

You can see the results and the current status in the Recon Monitor (Program IUUC_RECON_MONITOR) - Tabstrip Field to Field Comparison.

In the administration tab of the Recon Monitor, you can decide whether to use the Sender or Receiver Logging Table as Source of the keys to be checked (we recommend to use the receiver logging table). When selecting button "Individual Table Settings" a new screen appears where you can define the portion size per table. The field Number of parallel jobs is not implemented and therefore has no effect yet.
You can define a different size for the number of keys and data handled in one portion. A differentiation of the key and data portions size makes sense for cluster tables as a physical cluster key can contain several logical data records. In this case the key portion will be split again into several sub portions if necessary. For cluster tables we recommend to limit the key portion to 100.

BAL Application Log Documentation   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 5662 Date: 20240520 Time: 074201     sap01-206 ( 148 ms )