Defining Profitability and Cost Management Application Options

After registering the Oracle Hyperion Profitability and Cost Managementapplication, you can define application aptions.

To define options for a Profitability and Cost Management application:

1. On the Setup tab, under Register, select Target Application.

2. In the Target Application summary grid, select a Profitability and Cost Management target application.

3. Select the application options as needed from the table below.

Table 1-14 Profitability and Cost Management Application Options and Descriptions

Property	Value
Drill Region	Select Yes to create a drill region. A drillable region is created to use the drill through feature for Profitability and Cost Management data. Note: Oracle Hyperion Financial Data Quality Management, Enterprise Edition does not support drilling through to human resource data. The drill region URL allows Oracle Essbase, Oracle Smart View for Office, and Oracle Hyperion Financial Reporting to drill to the proper landing page. When loading data from FDMEE, the drill region is loaded to Oracle Hyperion Planning data. A drill region includes the Entity/Account/Scenario/Year/Period for Planning, a URL to get back to FDMEE, and a region name. For Essbase, you select the dimension to use for the drill region. Select Yes to enable or No to disable.
Source Language for Member Description	Select the default language for the member descriptions. To understand how languages are processed, see How Languages Are Processed.
Batch Size	Specify the batch size used to write data to file. The default size is 10,000.
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. "dynamic" is the default check entity calculation method. calculation script—Check entity data is calculated based on a predefined calculation script. If the calculation method is set to "dynamic", the default calculation is performed during Essbase consolidation. If the method is set to "calculation script", then the script name given on check entity screen is used to perform the consolidation in target system.
Prefix Dimension for Duplicate Members	When set to Yes 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 Prefix is set to No, then the user is responsible to specify the fully qualified member names. Refer to Essbase Documentation for fully qualified member name format. Note: Planning does not support duplicate members.
Load Method	Specify the method for loading data from the TDATASEG staging table to Essbase. Available methods include: 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 load method. The SQL method creates an application file type of ESSSQL.
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.