Defining Application Options for Financial Consolidation and Close

When loading journal entries or data to a Financial Consolidation and Close target application, you can control many aspects of the data that is loaded such as the level of journal information:

To define Financial Consolidation and Close application target options:

From the Data Integration home page, click to the right of an integration with a Financial Consolidation and Close target application, and then select Options.
From Options, then Target option, select the target application setting and then click Save.

Available Financial Consolidation and Close target application options are shown in the following table.

Table 9-4 Financial Consolidation and Close Application Options and Descriptions

Option	Description
Load Type	Select the type of load to push to the Financial Consolidation and Close application. Available options: Data—Load numeric data only. This is the default load option. Journal—Load journals.
Journal Status	The journal status indicates the current state of the journal. The status of a journal changes when you create, submit, approve, reject, or post the journal. Available options: Working—Journal is created. It has been saved, but it may be incomplete. For example, more line items may need to be added. Posted—Journal adjustments are posted to the database.
Journal Type	Select the type of journal to load. Available options: Auto-Reversing—Loads an auto-reversing journal that contains adjustments that need to be reversed in the next period. That is, the journal posts in the next period by reversing the debit and credit. Regular—Load journals using the Replace mode, which clears all data for a journal label before loading the new journal data.
Journal Post As	Select the method for posting journal entries: Available options: Journal-to-date— A Journal-to-Date journal entry carries forward from period to period, from the first instance of the journal entry, including a carry-forward across any intervening year-ends. The only difference between a Journal-to-Date entry and a Year-to-Date entry is that in the first period of each year, the data from Journal-to-Date entries in the last period of the prior year are reversed. For Year-to-Date entries, there are no reversals in the first period of any year. Periodic—When you select the View member FCCS_Periodic, when the journal entries are posted, the data entered to the line detail is summarized and posted to the Consol cube based on the line detail POV. The data from one posted journal entry does not overwrite the data written from other posted journal entries. Year-to-date—When you select the View member FCCS_YTD_Input, you can enter a year-to-date amount in the line detail debit / credit fields. A Year-to-Date journal entry must contain year-to-date entries on all detail lines. When Year-to-Date journal entries are posted, the appropriate periodic impact on the POV across the entries is calculated and then accumulated with any accumulation from posted Periodic journal entries In the first period of any year, the year-to-date View data is the same as Periodic data. In the first period of any year, the year-to-date View data is the same as Periodic data. In subsequent periods, the periodic calculated data posted to the Periodic View member for each unique POV equals the current period year-to-date entries accumulated across all Year-to-Date journal entries, minus the prior period year-to-date entries accumulated across all Year-to-Date journal entries.
Create 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 Financial Consolidation and Close 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 Zero Loading	Select Yes to load 0 values during a multiple period load.
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 fast 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.
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. 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.
Movement	Specify the movement dimension that indicates the automated cash flow reporting dimension used through hierarchies and system calculations. By default, the system provides members in the Movement dimension to maintain various types of cash flow data, and FX to CTA calculations. If no movement, then specify as FCCS_No Movement. Otherwise, select the desired movement member. Example of Movement Dimension Members: FCCS_No Movement FCCS_Movements FCCS_OpeningBalance FCCS_ClosingBalance
Multi-GAAP	Specify the multi-GAAP dimension used to report your financial statements in both local GAAP and in IFRS or another GAAP. This dimension tracks the local GAAP data input as well as any GAAP adjustments.
Data Source	Specify the data source dimension. The default value is "FCCS_Managed Data." You can change the default member is "FCCS_Managed Data." data source member to your custom data source member as needed.
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.
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	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.
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 about defining a custom view, see Defining a Custom View in the Workbench.