Use the Environment comparison studio to get the most relevant data from different environments or companies. In the Environment comparison studio, you compare the desired data using content packages. The comparison results show all the differences between two content packages. 

When you create a comparison, it is saved. You can also save intermediate results of the comparison. You can view the comparisons on the Compare history page. 

When you process your comparison results, for each table, a separate XML file is created. In the XML files, you can change the values that you want to synchronize manually. 


Application Consultant Application Consultant Start Start End End Select the content packages for comparison Select the content packages for comparison To compare data, select two content packages. If a desired content package does not exist, import the content package. As a result, a comparison is created. Procedure 1. Go to Environment Comparison Studio > Inquires > Content packages. 2. In the list, select a content package. Note: This content package is called a content package A. 3. Click Compare. 4. In the list, select a second content package. Note: This content package is called a content package B. 5. Click OK. Analyze the comparison results Analyze the comparison results As a result of a content packages comparison, all differences between the selected content packages are shown on the Compare page. Compare results On the Compare page, the Compare results tree shows where differences between the compared content packages exist. The Compare results tree has these types of entries:  Table: This is the highest level in the Compare results tree. It represents a table with records for which data differences exist between the compared content packages.  The entry name is defined by the target record name in the applicable message mapping.  The number of data differences for the table is shown in parentheses.  Record: This is the lowest level in the Compare results tree. It represents a record for which data differences exist between the compared content packages.  The entry name is defined by the key as set up in the applicable message field mapping.  The number of data differences for the record is shown in parentheses.  Possible differences For the selected entry in the Compare results tree, the related differences are shown in the Results pane. In the Results pane, for each difference, one of these messages is shown to describe the difference:  Field values are different  Field does not exist in source  Field does not exist in target  Record only exists in source  Record only exists in target  Note:  "Field does not exist in source" and "Field does not exist in target" messages do not imply that the original data tables do not have the specified field. It implies that the applicable message mapping removed this field from the resulting XML file. Analysis Use the Source value and Target value fields to analyze the difference between the field values.  You can choose one of these options to indicate how to solve a difference:   Synchronized manually: You want to set the field value manually. You can do so in the resulting XML file.  Use source value: Use the value from the source content package as final value.  Use target value Use the value from the target content package as final value.  You can use the View source record and View target record buttons to view the full selected record details in XML format. The shown data is retrieved from either the source content package or the target content package.  Procedure 1. Go to Environment Comparison Studio > Inquires > Compare history. 2. In the list, find and select the desired comparison. 3. In the tree, expand 'the desired table entry'. Note: To get an overview of all sections, select "Compare results" in the tree. 4. Select the desired option to handle the difference. 5. In the tree, select ''Compare results' to get an overview of all selections'. 6. Close the page. Notes When you create a comparison, it is saved. You can view the created comparisons on the Compare history page. You can use a comparison to: Continue your analysis if it is unfinished. Edit an analysis at any point in time. Save finalized analysis results. To which table to apply  the selected entries? To which table to apply  the selected entries? Process using source Process using source When you analyze data differences, you can edit a record value manually. To process your analysis results, you can choose to use the source value. As a result, in the created XML file, for the fields to be edited manually, the source value is used as field value. You can manually edit the value in the resulting XML file. Procedure 1. Go to Environment Comparison Studio > Inquires > Compare history. 2. In the list, click the link of a desired record. 3. Click Process using source. Process using target Process using target When you analyze data differences, you can edit a record value manually. To process your analysis results, you can choose to use the target value. As a result, in the created XML file, for the fields to be edited manually, the target value is used as field value. You can manually edit the value in the resulting XML file. Procedure 1. Go to Environment Comparison Studio > Inquires > Compare history. 2. In the list, click the link of a desired record. 3. Click Process using target. Source Target

Activities

Name Responsible Description

Select the content packages for comparison

Application Consultant

To compare data, select two content packages. If a desired content package does not exist, import the content package. As a result, a comparison is created.

Analyze the comparison results

Application Consultant

As a result of a content packages comparison, all differences between the selected content packages are shown on the Compare page.

Compare results

On the Compare page, the Compare results tree shows where differences between the compared content packages exist. The Compare results tree has these types of entries: 

  • Table: This is the highest level in the Compare results tree. It represents a table with records for which data differences exist between the compared content packages. 
    The entry name is defined by the target record name in the applicable message mapping. 
    The number of data differences for the table is shown in parentheses. 

  • Record: This is the lowest level in the Compare results tree. It represents a record for which data differences exist between the compared content packages. 
    The entry name is defined by the key as set up in the applicable message field mapping. 
    The number of data differences for the record is shown in parentheses. 

Possible differences

For the selected entry in the Compare results tree, the related differences are shown in the Results pane. In the Results pane, for each difference, one of these messages is shown to describe the difference: 

  • Field values are different 

  • Field does not exist in source 

  • Field does not exist in target 

  • Record only exists in source 

  • Record only exists in target 

Note:

 "Field does not exist in source" and "Field does not exist in target" messages do not imply that the original data tables do not have the specified field. It implies that the applicable message mapping removed this field from the resulting XML file.

Analysis

Use the Source value and Target value fields to analyze the difference between the field values. 

You can choose one of these options to indicate how to solve a difference:  

  • Synchronized manually: You want to set the field value manually. You can do so in the resulting XML file. 

  • Use source value: Use the value from the source content package as final value. 

  • Use target value Use the value from the target content package as final value. 

You can use the View source record and View target record buttons to view the full selected record details in XML format. The shown data is retrieved from either the source content package or the target content package. 

Process using source

Application Consultant

When you analyze data differences, you can edit a record value manually. To process your analysis results, you can choose to use the source value. As a result, in the created XML file, for the fields to be edited manually, the source value is used as field value. You can manually edit the value in the resulting XML file.

Process using target

Application Consultant

When you analyze data differences, you can edit a record value manually. To process your analysis results, you can choose to use the target value. As a result, in the created XML file, for the fields to be edited manually, the target value is used as field value. You can manually edit the value in the resulting XML file.

Provide feedback