Defining Direct Integration Options

When working with a direct integration, you can specify parameters specific to the direct integration source and target system. For example, for a Planning source system, you can the select cube and the period mapping type.

To select direct integration options:

From the Data Integration home page, click to the right of the direct integration, and then select Options.
From General Options, then Category, select a category.

The categories listed are those that you created in the Data Integration setup, such as "Actual." See Managing Category Mappings.
From Cube, select the plan type of the target system.

Cubes are assigned in Data Integration. You can register a custom cube as a separate application with no limit to the number of custom cube applications that can be registered.

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 method does not work when the scenario member is a shared member.
From Period Mapping Type, select the mapping type of the period.
Available options:
- Default—The integration uses the Period Key and Prior Period Key defined in Data Integration to determine the source General Ledger periods mapped to each Data Integration period when the integration is run.
- Explicit—The integration uses the Explicit period mappings defined in Data Integration to determine the source General Ledger periods mapped to each period. Explicit period mappings support additional General Ledger data sources when periods are not defined by start and end dates.
From Calendar, select the source system calendar.
In Integration Option 1-4, specify the free form text or value.

Any values you specify in the Integration Option 1-4 fields can be used when specifying run time parameters in business rules. For more information, see Using Business Rules.
In Data Extract Option, select the type of member data to extract.

Members can be extracted depending on how they have been flagged for calculation. For a member flagged as "stored," calculated data values are stored with the member in the database after calculation. For a member tagged as "dynamic calc," the member's data values are calculated upon retrieval.
Available options:
- All Data—Extracts stored values and dynamically calculated values for both the Dense and Sparse dimension.
  
  The All Data Extract option is not supported for a business process to business process data synchronization, and you cannot setup the integration in the target business process and extract the data from a remote business. For a business process to business process data synchronization, set up the integration with the All Data option in the source environment where the data is extracted, and then push it to a remote target system.
  
  Financial Consolidation and Close and Tax Reporting customers can extract dynamic calculated values by selecting the All Data option. It is a Data Integration prerequisite that the CONTROL TO-DATE VIEW STORAGE setting in Financial Consolidation and Close and Tax Reporting is enabled, or the Financial Consolidation and Close and Tax Reporting application is DSO (Dense Sparse Optimization enabled application) based, to extract dynamic calculated values. For more information, see Using the Control To Date View Option.
  
  Note:
  When pulling YTD from Financial Consolidation and Close and Tax Reporting, the optimal method is to convert the application to a DSO application, or use a DSO enabled application, and then select "All Data" as the extract data type, and then use "FCCS_YTD" as the filter for the View dimension.
- Stored and Dynamic Calculated Data—Extracts stored dynamic calculated values for the Dense dimension only and not Spare dimensions.
- Stored Data Only—Extracts stored data only. Dynamically calculated values are excluded in this type of extract.
In Data Precision, specify the number of decimal places displayed in numbers to be exported.

Data precision refers to numeric data with the emphasis on precision (accuracy). Depending on the size of a data value and number of decimal positions, some numeric fields may be written in exponential format; for example, 678123e+008. You might consider using data precision when data ranges from very large to very small values. The output files typically are smaller and data values are more accurate.

The default value for this option is 16.
In Data Number of Decimal, specify the maximum number of decimal positions to be exported.

Specify a value between 0 and 16. If no value is provided, the number of decimal positions of the data to be exported is used, up to 16 positions, or a value determined by the Data Precision option if that value is specified.

This parameter is used with an emphasis on legibility; output data is in straight text format. Regardless of the number of decimal positions in the data, the specified number is output. Note that it is possible the data can lose accuracy, particularly if the data ranges are from very large values to very small values, above and below the decimal point.

By default, 16 positions for numeric data are supported, including decimal positions. If both the Data Precision and the Data Number of Decimal options are specified, the Data Precision option is ignored.
(For General Ledger only): From Include Adjustment Period, select one of the following options for processing adjustment periods:
- No—Adjustment periods are not processed. The system processes only regular period mappings (as setup for "default" and "explicit" mappings). No is the default option for processing adjustments.
- Yes—If Yes is selected, then the regular period and adjustment period are included. If the adjustment period does not exist, then only the regular period is processed.
- Yes (Adjustment Only)—If Yes (Adjustment Only) is selected, the system processes the adjustment period only. However, if the adjustment period does not exist, the system pulls the regular period instead.
(Planning and Oracle General Ledger non-administrator only) From Replace for Non Admin Load Method, select the Replace method when loading data to a Planning application for non-administrator users.
Available methods:
- None—Performs no replace.
- Numeric Data Only—Performs replace when the load method is Numeric Data only.
- All Load Methods—Perform replace for all load methods.
Click Save.