Defining Target Options

When integrating source applications with target applications, you can select options that support how you load date including load methods, date formats, batch, and purge options.

To define target options:

  1. From the Data Integration home page, click Image shows Select icon. to the right of the integration, and then select Options.
  2. Select the application options.
    Target Option Description
    Load Method

    Select the method for loading data to the target application.

    Available methods:

    • Numeric—Loads numeric data only. Planning data security is not enforced with this method.

    • All data types with auto-increment of line item—This method requires that you define the data and driver dimensions, and unique identifiers for the Planning application. You define data load and driver dimension in the Data Dimension for Auto-Increment Line Item field and Driver Dimension for Auto-Increment Line Item field below.

      Replace Mode is not supported for the load method "All data types with auto-increment of line item."

    • All data types with security—Loads Numeric, Text, Smartlist, Date data types. If the Planning administrator loads data, Planning data security is not enforced. If a Planning non-administrator user loads data, then Planning data security is enforced. A Planning non-administrator user can load only 500,000 cells of data.

    Batch Size

    Specify the number of rows read at a time from the file to memory.

    This parameter is mainly used for performance. When data is loaded, this setting determines how many records are stored in the cache. For example, when 1000 is specified; 1,000 records are stored in cache. Similarly, when 5000 is specified, 5,000 records are stored in cache and commit.

    Determine this setting by Server Memory and adjust as needed.

    Drill Region

    Tap the slider on to enable the drill region.

    When this option is enabled, a drillable region is created to use the drill through feature.

    When loading data, the drill region is loaded to Planning data.

    Drill region by scenarios are created. For any cube (Planning cubes or Planning databases), the name of the drill region is FDMEE_<name of the scenario member>. When creating the drill region, the system checks if a dimension is enabled for the drill.

    Members of enabled dimensions selected in data loads, are included in the drill region filter. If no dimensions are enabled, the Scenario, Version, Year, and Period dimensions are enabled by default. You can enable additional dimensions, and the subsequent data load considers members of newly enabled dimensions. If you disable any dimensions which were previously included in a drill region used for drill creation, members of such dimensions are not deleted during the subsequent data loads. If needed, you can remove obsolete members manually.

    Purge Data File

    Tap the slider on to delete the data file from the application outbox directory when a file-based data load is successful.

    Tap the slider on to delete the file or tap the slider off to retain the file.

    Date format for date data

    Select the format used for loading date data.

    Use the date format based on the locale settings for your locale. For example, in the United States, enter the date using the format MM/DD/YY format.

    Data Dimension for Auto-Increment Line Item

    Select the data dimension that matches the data dimension you specified in Planning

    This option is used for loading incremental data using a LINEITEM flag. See Loading Incremental Data using the LINEITEM Flag.

    Driver Dimension for Auto-Increment Line Item Select the driver dimension that matches the driver dimension you specified in Planning

    This setting is used for loading incremental data using a LINEITEM flag. See Loading Incremental Data using the LINEITEM Flag.

    Member name may contain comma Select Yes to load data when a member name contains a comma.
    Summary Drill Behavior when more than 1000 descendants

    Select how a summary drill functions with more than 1,000 descendants.

    Available options:

    • Ignore
    • Limit

    If the number of descendants in summary drill is greater than 1,000 and the Summary Drill Behavior when more than 1000 descendants option is Ignore, then the system ignores the dimension in the filter and returns the drilled data based on filters on the other dimensions. A maximum of three dimensions can be ignored.

    If the number of descendants in summary drill is greater than 1,000 and the Summary Drill Behavior when more than 1000 descendants option is Limit, then the system considers only the first 1,000 members for the dimension while returning the data rows.

  3. From Load Method, select the method for loading data to the target application.

    Available methods:

    • Numeric—Loads numeric data only. Planning data security is not enforced with this method.

    • All data types with auto-increment of line item—This method requires that you define the data and driver dimensions, and unique identifiers for the Planning application. You define data load and driver dimension in the Data Dimension for Auto-Increment Line Item field and Driver Dimension for Auto-Increment Line Item field below.

      Note:

      Replace Mode is not supported for the load method "All data types with auto-increment of line item."
    • All data types with security— Loads Numeric, Text, Smartlist, Date data types. If the Planning administrator loads data, Planning data security is not enforced. If a Planning non-administrator user loads data, then Planning data security is enforced. A Planning non-administrator user can load only 500,000 cells of data.

  4. In Batch Size, specify the number of rows read at a time from the file to memory.

    This parameter is mainly used for performance. When data is loaded, this setting determines how many records are stored in the cache. For example, when 1000 is specified; 1,000 records are stored in cache. Similarly, when 5000 is specified, 5,000 records are stored in cache and commit.

    Determine this setting by Server Memory and adjust as needed.

  5. In Drill Region, tap the slider on to enable the drill region.

    When this option is enabled, a drillable region is created to use the drill through feature.

    When loading data, the drill region is loaded to Planning data.

    Drill region by scenarios are created. For any cube (Planning cubes or Planning databases), the name of the drill region is FDMEE_<name of the scenario member>. When creating the drill region, the system checks if a dimension is enabled for the drill.

    Members of enabled dimensions selected in data loads, are included in the drill region filter. If no dimensions are enabled, the Scenario, Version, Year, and Period dimensions are enabled by default. You can enable additional dimensions, and the subsequent data load considers members of newly enabled dimensions. If you disable any dimensions which were previously included in a drill region used for drill creation, members of such dimensions are not deleted during the subsequent data loads. If needed, you can remove obsolete members manually.

  6. In Purge Data File, tap the slider on to delete the data file from the application outbox directory when a file-based data load is successful.

    Tap the slider on to delete the file or tap the slider off to retain the file.

  7. In Date format for date data, select the format used for loading date data.

    Use the date format based on the locale settings for your locale. For example, in the United States, enter the date using the format MM/DD/YY format.

  8. From Data Dimension for Auto-Increment Line Item, select the data dimension that matches the data dimension you specified in Planning.

    This option is used for loading incremental data using a LINEITEM flag. See Loading Incremental Data using the LINEITEM Flag.

  9. From Driver Dimension for Auto-Increment Line Item, select the driver dimension that matches the driver dimension you specified in Planning.

    This setting is used for loading incremental data using a LINEITEM flag. See Loading Incremental Data using the LINEITEM Flag.

  10. From Member name may contain comma, select Yes to load data when a member name contains a comma.
  11. From Workflow Mode, select the data workflow mode.

    Available modes:

    • Full—Data is processed in the TDATASEG_T table and then copied to the TDATASEG table.

      All four Workbench processes are supported (Import, Validate, Export, and Check) and data can be viewed in the Workbench.

      Drill-down is supported.

    • Full No Archive—Data is processed in the TDATASEG_T table and then copied to TDATASEG table.

      All four Workbench processes are supported (Import, Validate, Export, and Check). Data can be viewed in the Workbench but only after the import step has been completed. Data is deleted from TDATASEG at the end of the workflow process.

      Drill-down is not supported

    • Simple— Data is processed in the TDATASEG_T table and then exported directly from the TDATASEG_T. table.

      All data loads include both the import and export steps.

      Data is not validated and any unmapped data result in load failure.

      Maps are not archived in TDATAMAPSEG.

      Data cannot be viewed in the Workbench.

      Drill-down is not supported.

      The Simple Workflow Mode is the default mode.

  12. From Enable Data Security for Admin Users, select to enable data security for administrative users.

    Enables data validation when an administrative user loads data. In this case, all data validations in the data entry form are enforced while loading data. Due to the enhanced validations, the performance of data load is slower.

    When Enable Data Security for Admin Users is set to No (default value), then data loads by the administrator are performed using the Outline Load Utility (OLU). In this case, performance is faster but you are unable to get a detailed error report for any rows that are ignored for any reason.

    When this option is set to Yes, data is validated for administrator and non-administator data loads in the same manner. Validations include: security checks, intersection validations, read-only cells, dynamic calc cells, etc.

    In addition, a detailed error list for any rows that are rejected or ignored is available and no additional Planning permissions are needed. However, performance may be slower even for administrators.

  13. From Display Validation Failure Messages, create an output file that shows rejected data cells, intersections, and the rejection reason when you load data.

    The limit for the number of rejections reported is 100. The data validation report is available for download from the Process Details page by clicking the Output link. In addition, a copy of the error file is stored in the Outbox folder.

    For more information, see Viewing Process Details

  14. (Planning and Oracle General Ledger non-administrator only) From Replace for Non Admin Load Method, select the Replace method when loading data to an 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.

    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. All Data Type load methods does not work when the scenario member is a shared member.
  15. In Drill View from Smart View, specify the custom view of columns from the Workbench when displaying customized attribute dimension member names in Oracle Smart View for Office drill-through reports.

    When the custom view has been defined, you can click the drill-through cell in Smart View and select Open as New Sheet, and the drill-through report opens based on the view defined in the Workbench.

    If no views are defined on the Application Details page, the default view is used, meaning that attribute dimensions do not display customized member names in Smart View.

    For more information about defining a custom view, see Defining a Custom View in the Workbench.

  16. Click Save.