The Application Root Directory must be set up on the server, specified in this field, and the Create Application Folder option must be executed as first steps when using FDMEE.

The Application Root folder identifies the root directory of the FDMEE application. This folder is located on the FDMEE server and functions as the root folder for all FDMEE activities. Based on this parameter, FDMEE saves log files, generated files and reports to the appropriate folder under this root directory. Parameters must be set up on the server separately from this setup step.

When you select the File profile type, the System Setting screen displays the Create Application Folder button. This feature instructs the system to create a folder structure in the path specified in this field. The folder structure is (with sub-folders in each):

inbox

outbox

When you specify a folder at the application level, and select the Create Application Folders option, a set of folders is created for the application that includes a scripts folder. Create scripts specific to an application in this folder. This is especially important for event scripts that are different between applications. If you do not set up an application level folder, then you cannot have different event scripts by application.

If you specify a Universal Naming Convention (UNC) path, share permissions on the folder must allow access to the DCOM user for read/write operations. Use a Universal Naming Convention (UNC) path for the application root folder when Oracle Hyperion Financial Management and FDMEE are on separate servers. Contact your server administrator to define the required UNC definition.

If a UNC path is not entered, then you must enter the absolute path. For example, specify C:\Win-Ovu31e2bfie\fdmee

Instructs the system to create a location folder in the inbox when a location is created. Available values are Yes or No. Set this option once and do not change it. This setting is optional but recommended.

Specifies whether archived files are copied or moved to the archive location. Enter Copy, Move, or None.

If you select Copy, then the file is left in the inbox.

If you select Move, then the file is copied to the archive folder and deleted from the inbox.

The folder named data is the archive folder.

<Process ID><Year><Month><Day>.<Original Extension>

For example, if the source file name is BigFile.csv, and it was loaded for period Mar-07 with a period key of 03/01/2007, and if the process id was 983, then the resulting file name is 98320070301.csv.

Specify file extensions that cannot be uploaded.

Enter *.* to disallow all file uploads.

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; the system stores 1,000 records in cache. Similarly, when 5000 is specified, the system stores 5,000 records in cache and commit. Determine this setting by Server Memory and adjust as needed.

Specify the method for mapping bit combinations to characters for creating, storing, and displaying text.

Each encoding has a name; for example, UTF-8. Within an encoding, each character maps to a specific bit combination; for example, in UTF-8, uppercase A maps to HEX41.

Encoding refers to mapping bit combinations to characters for creating, storing, and displaying text.

Convert the encoding to UNICODE if your source file is not in one of the supported formats.

Specify the directory where the files that store passwords in encrypted form is located.

This encrypted password folder is used with the "Update Configuration File" button. See Working with Batch Scripts.

When exporting data, select the desired file format.

Available file formats are:

• CSV (*.csv)
• Excel (*.xls)

The default file format for exports is CSV.

Specifies the Oracle Data Integrator user name used to access the Oracle Data Integrator master repository. For example, enter Supervisor.

This setting is defined automatically when ODI is configured, but you can customize it if necessary.

Specifies the Oracle Data Integrator database schema used to access the Oracle Data Integrator master repository. For example, enter Master.

This setting is defined automatically when ODI is configured, but you can customize it if necessary.

Specifies the repository where all scenarios are stored. For example, enter ERPI_REF.

This setting is defined automatically when ODI is configured, but you can customize it if necessary.

Specifies the (execution) repository which contains runtime objects (for example, scenarios). The work repository can be linked with only one Master Repository.

For example, enter FDMEE_WORK_REF.

Specifies the driver of the ODI master repository.

This setting is defined automatically when ODI is configured, but you can customize it if necessary.

Specifies the URL of the server where the Oracle Data Integrator master repository is installed.

This setting is defined automatically when ODI is configured, but it can be customized if necessary.

For example, enter jdbc:oracle:thin:@serverdatabase.oracle.com:1521:orcl.

Specifies the Oracle Data Integrator master repository user name.

This setting is defined automatically when ODI is configured, but you can customize it if necessary.

Specifies the Oracle Data Integrator master repository password.

This setting is defined automatically when ODI is configured, but you can customize it if necessary.

Specify the system default language of the user version of FDMEE.

FDMEE uses the user language to query the language data, for example, column titles, segment name, and so on.

The default theme contains all the colors, styles, and general-use icons that are displayed in the user interface. FDMEE uses BLAF+ as the default value.

Specify the type of Check Report to use as the default check report. The following are pre-seeded check reports, but you can create a new one and specify it here:

• Check Report—displays the results of the validation rules for the current location (pass or fail status).

• Check Report Period Range (Cat, Start per, End per)—Displays the results of the validation rules for a category and selected periods.

• Check Report by Val. Entity Seq.—Displays the results of the validation rules for the current location (pass or fail status); sorted by the sequence defined in the validation entity group.

• Check Report with Warnings—Displays the results of the validation rules for the current location. Warnings are recorded in validation rules and shown if warning criteria are met. This report does not show rules that passed the validation.

Specify the type of Intersection Check Report to use as the default intersection check report at the system level. Intersection reports identify data load errors and are generated as part of the data validation step in the Data Load Workbench. The reports are available in two formats: Dynamic Column or Fixed Column format. The Fixed Column displays up to four custom dimensions.

When a batch job is run in sync mode (immediate processing), specify the maximum time the job can run. In sync mode, FDMEE waits for the job to complete before returning control.

Specify the name of the SQL Server database provider.

Available SQL Server database providers:

• SQLOLEDB

• SQLNCLI10 (SQL Server 2008)

• SQLNCLI11 (SQL Server 2012)

Specify the level of detail displayed in the logs. A log level of 1 shows the least detail. A log level of 5 shows the most detail.

Logs are displayed in Process Details by selecting the Log link.

Specify the total number of decimal digits for rounding numbers, where the most important digit is the left-most nonzero digit, and the least important digit is the right-most known digit.

Specify Yes to display the Override All Data option in the Export Mode drop-down located on the Execute Rule screen.

When you select to override all data, the following message is displayed "Warning: Override All Data option will clear data for the entire application. This is not limited to the current Point of View. Do really want to perform this action."

Set to Yes to create audit records for the Map Monitor reports (Map Monitor for Location, and Map Monitor for User). The default value for this setting is No.

Access to Open Source Document

When drilling down to the FDMEE landing page, this setting determines access to the Open Source Document link (which opens the entire file that was used to load data).

• Administrator—Access to Open Source Document link is restricted to the administrator user.

• All Users—Access to the Open Source Document link is available to all users. All Users is the default setting.

Sets the column delimiter value when exporting member mappings.

Available delimiters are:

• ! (exclamation mark)

• , (comma)

• ; (semi-colon)

• | (pipe)

Select the Excel file format to use when exporting member mappings:

• Excel 97-2003 Workbook (*.xls)
• Excel Macro-Enabled Workbook (*.xlsm)

Sets the export option for data load mappings to Migration (Lifecycle Management).

Available options:

• Individual Data Load Mapping— maps are exported individually for each location and imported individually for each location. If you have a large number of maps for each location, use this method since it allows loading of maps in smaller sets by location. This method is also useful to migrate maps for certain locations selectively. With this method, existing maps are deleted and replaced by new maps in the snapshot.
• Combine Data Load Mapping for All Locations—maps are exported in a single artifact for all locations. With this method, maps from the snapshot are merged to the existing maps in the target system. This is the default setting.

Select the type of drill through user interface to use when drilling down in Oracle Enterprise Performance Management Cloud.

Available drill types:

• Classic—The user interface of the drill through landing includes the standard source and target tabs, which includes the General Ledger accounts and the hyperlinked balances that were used to populate the cells in the application. In the classic user interface, users cannot create a custom view of the drilled data.

• Simplified User Interface—In addition to the standard source and target tabs on the landing page, users can add a custom view of the drilled data.

  For more information on using a custom view for the drill through, see Adding a Custom View to the Drill Through Landing Page

Specifies the default POV Period.

These preferences take precedence when no equivalent settings are in Application Settings or User Settings.

Specifies the default POV Category. These preferences take precedence when no equivalent settings are in Application Settings or User Settings.

When this is set to Yes, other POVs (Application Level and User Level POVs) are ignored.