Defining Application Detail 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.

Note:

For information about Application Details for Oracle ERP Cloud Data Sources, see Defining Application Details for Oracle ERP Cloud Data Sources.

To define target options:

  1. From the Data Integration home page, and then Actions, select Applications.
  2. From the Application page, click Image shows Select icon. to the right of the application, and then select Application Detail.
  3. Select the Options tab.
  4. Select the option and select the needed action.
    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.

    The drill region by scenarios is 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.

    Enable Drill from Summary

    Select Yes to drill down from summary members in a Planning data form or report and view the detail source data that make up the number.

    After enabling this option and loading the data with the Create Drill Region option set to Yes, the Drill icon is enabled at the summary level. Drill is limited to 1000 descendant members for a dimension.

    Note:

    If you Enable Summary Drill, do not include the dimension you want to drill from the Parent Members in the drill region definition. If you absolutely need to include this dimension, then disable the auto drill region creation and then maintain the drill region manually using Calculation Manager user interface. Use Essbase member function like Descendants to enumerate the members you want to include in the drill region.

    Summary drill is available for local service instances only. It is not available between cross service instances or hybrid deployments.

    Note:

    In order to support a summary drill, your drill query should not include an operator in the WHERE clause of the QL. For example your query should be: WHERE COMPANY ~ENTITY~. The system determine appropriate condition (IN, LIKE) based on the number of descendants.
    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

    If the member name contains a comma, and you are loading data to one of the following services, set this option to Yes, and then load the data:

    • Planning Modules
    • Planning
    • Financial Consolidation and Close
    • Tax Reporting
    Workflow Mode

    Select the data workflow method.

    Available options:

    • 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.

      The Full Workflow Mode is the default mode.

    • 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.

    Enable Data Security for Admin 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 will be slower.

    When the ‘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-administrator 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.

    Display Validation Failure Reasons

    Enables you to report rejected data cells and the rejection reason when you load data in a data validation report.

    Select Yes to report rejected data cells and the rejected reason.

    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.

    Select No to not report rejected data cells and the rejection reason.

    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.

    Custom views are created and defined in the Workbench option in Data Integration. When the custom view has been defined and then specified in the Drill View from Smart View field, in Smart View you can click the drill-through cell 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 Options page, the default view is used, meaning that attribute dimensions do not display customized member names in Smart View.

    For more information, see Defining a Custom View in the Workbench.

    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.

    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.

  5. Click Save.