Defining Application Options for Essbase and Planning

Define application and dimension details for Oracle Essbase and Oracle Hyperion Planning applications.

After defining the application details and dimension details, for Essbase and Planning, define the application options.

Note:

The user attempting to load data to Planning must be provisioned with Essbase administrator or Planning administrator rights.

To define application options for Essbase or Planning applications:

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

Table 1-12 Essbase and Planning Application Options and Descriptions

Option	Description
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.
Prefix Dimension for Duplicate Members	When this option is set to Yes, then member names are prefixed by the Dimension Name. The member name that is loaded is in the format [Dimension Name]@[Dimension Member]. The prefixed dimension name is applied to all dimensions in the application when this option is enabled. You cannot select this option if there is a dimension in the target that has duplicate members. That is, only select this option when the duplicate members cross dimensions. If the application supports Duplicate Members and the Prefix is set to No, then the user must specify the fully qualified member names. Refer to Essbase documentation for the fully qualified member name format. Note: Planning does not support duplicate members.
Global User for Application Access	Option to override the Single Sign-On logon to the Essbase and the Planning applications. When a user name is specified for this option, this user name is used to access Essbase/Planning applications instead of the Oracle Hyperion Financial Data Quality Management, Enterprise Edition sign-on user name. Specify the user name of a user who has administrator access to the Planning application, and/or Application/Database Manager access to the Essbase applications.
Batch Size	Specify the batch size used to write data to file. The default size is 10,000.
Load Method	Specify the method for loading data from the TDATASEG staging table to Essbase. Available methods are: File—Data is written to a data file in the `outbox` directory of the application (defined in System Settings). The file name is in the format `<APPLICATION NAME>_<PROCESS_ID>.dat.` It is then loaded to Essbase. The file load method creates an application file type of ESSFILE. SQL—Uses SQL Method to load data. The SQL load method is the default. The SQL method creates an application file type of ESSSQL.
Check Entity Calculation Method	Specify the calculation method for check entities. Available methods are: dynamic—Check entity data is calculated based on the data at retrieval time. If set to dynamic, then the default Essbase calculation is executed. calculation script—Check entity data is calculated based on a predefined calculation script.
Source Language for Member Description	Select the default language for the member descriptions. To understand how languages are processed, see How Languages Are Processed.
Drill Region	Select Yes to create a drill region. A drillable region is created to use the drill through feature. Note: FDMEE does not support drilling through to human resource data. When loading data from FDMEE, the drill region is loaded to Planning data. FDMEE 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, FDMEE 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.
Date Format	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. Used for loading incremental data using a LINEITEM flag. See Loading Incremental Data using the LINEITEM Flag to an EPM Application.
Driver Dimension for Auto-Increment Line Item	Select the driver dimension that matches the driver dimension you specified in Planning. Used for loading incremental data using a LINEITEM flag. See Loading Incremental Data using the LINEITEM Flag to an EPM Application.
Member name may contain comma	To export a dimension member name containing a comma to Planning, select Yes. Otherwise, select No.
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 is slower. 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. When this options 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: If you using an incremental data load in Workforce, then Enable Data Security for Admin Users must be set to No.
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.