Defining Application Options for Essbase

Define application and dimension details for Oracle Essbase applications.

To define application options for Essbase:

1. On the Setup tab, under Register, select Target Application.
2. In the Target Application summary grid, select a Planning target application or Essbase target application.
3. After defining the application details and dimension details in Application Detail, select the Application Options tab.
4. Complete the application options as needed.
5. Click Save.

Table 2-9 Essbase Application Options and Descriptions

Option	Description
Load Method	Select the method for loading data: Numeric—Loads numeric data only. Planning data security is not enforced with this method. 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. Data is loaded in chunks of 500K cells.
Batch Size	Specify the batch size used to write data to file. The default size is 10,000.
Drill Region	Select Yes to create a drill region. A drillable region is created to use the drill through feature. Note: Data Management does not support drilling through to human resource data. When loading data from Data Management, the drill region is loaded to Planning data. Data Management creates drill region by scenarios. For any cube (Planning plan types or Planning databases, the name of the drill region is FDMEE_<name of the scenario member>. When creating the drill region, Data Management 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 following dimensions are enabled by default: Scenario, Version, Year, and Period. 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. For more information about defining drill regions, see the "Drill Through URL" option in Registering File-Based Source Systems, and "Drill URL" option in Adding Import Formats.
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: Summary level drill downs are not available for the Scenario, Year, and Period dimensions. For these dimensions, you must perform a drill through on the leaf members. Summary drill is available for local service instances only. It is not available between cross service instances or hybrid deployments.
Purge Data File	When a file-based data load to Essbase is successful, specify whether to delete the data file from the application outbox directory. Select Yes to delete the file, or No to retain the file.
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. Note: When running any of the Workforce Incremental rules (for example, OWP_INCREMENTAL PROCESS DATA WITH SYNCHRONIZE DEFAULTS), ensure that then target option Enable Data Security for Admin Users is set to No. This option can only be set by an administrator. 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.
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. Note: When drilling into Smart View, Data Integration uses the last used view on the Drill landing page. If no last used view is found, Data Integration uses the default view selection in this setting 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
Default Import Mode	Sets the default import mode when you execute a data load rule in Data Management or run an integration in Data Integration. Available options: Append Replace
Default Export Mode	Sets the default export mode when you execute a data load rule in Data Management or run an integration in Data Integration. Available options: Accumulate (Add Data) Replace Merge Data (Store Data) Subtract