Validating and Executing Synchronizations

When you execute a synchronization, data is retrieved from the source application, transformed according to mapping rules, and pushed to the destination application where it is committed to the application. When you validate a synchronization, the same process is followed but the data is not committed to the destination application. This enables the source and destination to process the request and resulting data to generate errors that might occur without writing the data. You can quickly identify if issues exist with the synchronization.

If your destination is an Essbase application, the Data Synchronizer uses the default values for:

  • abortOnError—Determines whether this operation should be aborted if there is error. Valid values are true or false.

  • DryRun—Determines whether it is a dry run with no actual data update. Valid values are true or false.

  • delimiter—Indicates the delimiter for the data stream.

Note:

If a shared location is used for an external file, this data file needs to be accessible by the server validating or executing the synchronization.

  To validate and execute synchronizations:

  1. Perform an action:

    To validate a synchronization:

    • In the Data Synchronizer, right-click a synchronization, and select Validate Synchronization.

    • In the Dimension Mapping, click Validate Button.

    To execute a synchronization:

    • In the Data Synchronizer, right-click a synchronization, and select Execute Synchronization.

    • In the Dimension Mapping, click Execute Synchronization Button.

  2. Select the Operator and type the Value.

    You should select the operator and enter a value if the values from the source are on a different scale than the destination. You can select Multiply, Divide, Add, or Subtract and then enter a numeric value to apply with the operator. For example, if you select the operator * (Multiply) and enter the value, 10, each data value sent to the destination will be multiplied by 10.

  3. Select the data load option Mode.

    Data Load Options for Planning and Essbase ASO and BSO applications are:

    • Add—Adds the values in the loaded data. For example, consider that the source data for “Account A” has a value of 60, and the target data for “Account A” contains a value of 100. After the data synchronization with “Add” selected, the target application data for “Account A” displays a value of 160.

    • Subtract—Subtracts the values in the loaded data. For example, consider that the source data for “Account A” has a value of 60, and the target data for “Account A” contains a value of 100. After the data synchronization with “Subtract” selected, the target application data for “Account A” displays a value of 40.

    • Overwrite—Overwrites the data in the target application with the last loaded value from the source data. For example, consider that there are two rows in the source data for “Account 1010.” The first row is the oldest and has a value of 500.00. The second row was loaded last and has a value of 1100. After the data synchronization, the data is overwritten with the last loaded value: 1100.

      Note:

      In Essbase (ASO) synchronizations, the “Overwrite” load option differs in that it accumulates the duplicate records source data, and then overwrites the target application data.

    Data Load Options for Financial Management applications are:

    • Merge—Merges the data in the target application with the most recent value from the source data and does not modify any subcubes. For example, consider that there are four rows in the source data for “Account 1000.” The first row is the oldest and has a value of 1000.00. The second and third rows also have values of 1000.00. The fourth row, which is the most recent, has a value of 2000. After the data synchronization, the data is merged with the most recent value: 2000.

    • Replace—Replaces the data with the most recent value and modifies the values in the subcubes. For example, consider that there are two rows in the source data for “Account 10.” The first row is the oldest and has a value of 5000.00. The second row has a value of 1000.00. After the data synchronization, the data is replaced with the most recent value: 1000.

    • Accumulate in Source—(Equivalent to “Accumulate in File” in Classic Financial Management) Consider these scenarios when selecting Accumulate in Source in combination with the Merge and Replace options:

      • Select Merge and Accumulate in Source—Adds the duplicate values in the source and the subcubes are not modified.

      • Select Merge and deselect Accumulate in Source—The most recent value is loaded in the source and the subcubes are not modified.

      • Select Replace and Accumulate in Source—Adds the duplicate values in the source and the subcubes are modified.

      • Select Replace and deselect Accumulate in Source—Loads the most recent value and the subcubes are modified.

    • Accumulate—Adds the values in the loaded data. For example, consider that there are two rows in the source data for “Account A.” The values are: 50.5 and 100. After the data synchronization, the value that displays in the target application for “Account A” is 150.5.

      Note:

      Selecting or clearing “Accumulate in Source” has no affect on how values are loaded if you select “Accumulate”.

  4. If the synchronization uses an external source file, enter the URL for the source, or click Upload to use a file as the source.

  5. Click OK.