Running an Integration

11 Running an Integration

You run an integration to extract the data from the source system, and then view and verify the results. If the data has been transformed correctly, you can push it to the target system.

The Run Integration page consists of two tabs: Options and Filters.

The Options tab enables you to select general and target options for the selected integration at the transformation stage. Note that the period selections on this page depend on the target system.

The Filters tab enables you to quickly add or modify filters at runtime and execute them rather than modifying the integration definition every time. Filters are used to query the data from the data sources. The changes to the filters are not saved and used for that execution only.

Watch this tutorial for information about running integrations: Setting File-Based Data Integration Options and Running Integrations in Enterprise Planning Cloud.

To run an integration:

From the Data Integration home page, select an integration, and then click .
Select the Options tab.
Select Import Source to import the data from the source system, perform the necessary transformation, such as import, map, and validate the data.
Select this option only when:
- you are running an integration for the first-time.
- the data in the source system has changed. For example, if you reviewed the data in the workbench after the export, and it was necessary to modify data in the source system.
In many cases, source system data may not change after you import the data from the source the first time. In this case, it is not necessary to keep importing the data if it has not changed.
Select Recalculate to skip importing the data, but re-process the data with updated mappings.
From Import Mode, select the method for importing data.
Available import modes:
- Append—Keep existing rows for the POV but append new rows to the POV. For example, a first-time load has 100 rows and second load has 50 rows. In this case, 50 rows are appended. After this load, the row total for the POV is 150.
- Replace—Clears all data for the POV in the target, and then loads from the source or file. For example, a first-time load has 100 rows, and a second load has 70 rows. In this case, 100 rows are removed, and 70 rows are loaded to TDATASSEG. After this load, the row total is 70.
  
  For a Planning application, Replace clears data for Year, Period, Scenario, Version, and Entity that you are loading, and then loads the data from source or file. Note that when you have a year of data in the Planning application, but are only loading a single month, this option clears the entire year before performing the load.
  
  Note:
  When running an integration in Replace mode to an ASO cube, if the scenario member is a shared member, then only a Numeric data load is performed. Be sure to specify the member name with fully qualified name including complete hierarchy. The All Data Type load methods does not work when the scenario member is a shared member.
  
  Note:
  Replace Mode is not supported for the load method "All data types with auto-increment of line item."
- Merge—(Account Reconciliation only). Merge changed balances with existing data for the same location.
  
  Merge mode eliminates the need to load an entire data file when only a few balances have changed since the last time data was loaded into Account Reconciliation. If mappings change between two loads, customers must reload the full data set.
  
  For example, a customer might have 100 rows of existing balances for one number account IDs, each which has an amount of $100.00. If the customer runs the integration in merge mode and the source has one row for one account ID with an amount of $80, then after running integration, there are one hundred rows of balances, 99 each of which have a balance of $100.00, and 1 which has a balance of $80.00.
- No Import—Skip the import of data entirely.
- Map and Validate—Skip importing the data but reprocess the data with updated mappings.
From Start Period, select the first period for which data is to be loaded.
You can filter periods by simply typing the character(s) to filter by. For example, type J to filter by months beginning J such as June or July. You can also click the drop down and specify additional filter criteria in the edit box shown below More results available, please filter further.

This period name must be defined in period mapping.
Note:

Use a Start Period and End Period that belong to a single Fiscal Year. If a period range crosses fiscal years, you run into the following issues:
- When loading data in replace mode, the system clear data for both years
- When exporting data, you will get duplicate data
The above is applicable for all modes of data load including standard and quick mode.
From End Period, select the last period for which data is to be loaded.

This period name must be defined in period mapping.
From Period, select the period for which to load data.

If a POV period has been selected on the Home page, then the selected period defaults here. If no POV period is selected, then the system defaults to the last used period based on browser cache.

You can select another period when an unlock icon ( appears next to it.

When the Global POV mode is enabled in System Settings in Data Management, then the period defaults to the Global POV Period and a customer is not allowed to select another period. In this case, a lock icon (appears next to the Period drop-down.
Select Export to target to export the data to the target application.
Select Execute Check to generate the data, and then run the Check Report.
From Export Mode, select the method for exporting data to the target application.
Available options:
- Merge—Overwrite existing date with the new data from the load file. (By default, all data load is processed in the Merge mode.) If data does not exist, create new data.
- Replace—Clears all data for the POV in the target, and then loads from the source or file. For example, a first-time load has 100 rows, and a second load has 70 rows. In this case, 100 rows are removed, and 70 rows are loaded to the staging table. After this load, the row total is 70.
  
  For a Planning application, Replace clears data for Year, Period, Scenario, Version, and Entity that you are loading, and then loads the data from source or file. Note that when you have a year of data in the Planning application, but are only loading a single month, this option clears the entire year before performing the load.
- Accumulate—Accumulate the data in the application with the data in the load file. For each unique point of view in the data file, the value from the load file is added to the value in the application.
- Subtract—Subtract the value in the source or file from the value in the target application. For example, when you have 300 in the target, and 100 in the source, then the result is 200.
- Dry Run—(Financial Consolidation and Close and Tax Reporting only) Scan a data load file for invalid records without loading data it to the target application. The system validates the data load file and lists any invalid records into a log, which lists 100 errors or less. For each error, the log indicates each record in error with its corresponding error message. Log details are available in Process Details.
  
  Note:
  Dry Run ignores the Enable Data Security for Admin Users target option and always uses the REST API for the administrator user.
- No Export—Skip the export of data entirely.
- Check—After exporting data to the target system, display the Check report for the current POV. If check report data does not exist for the current POV, a blank page is displayed.
Click Filters
Add or modify the filter(s) to execute at runtime.

Filters are used to query the data from the data sources. Filter specified on the Run Integration page are not saved and used for that execution only.

For more information, see Defining Filters.
File-Based Integrations Only: If no file profile has been selected for the integration, in File, specify the file to use at run time.

If a file has been selected when the integration was created on the General page, the selected file profile is shown in this field and you can't upload a different file at runtime with another file profile.
Click Run.