Setting System-Level Profiles

Use system settings to update or clear system level profiles that apply to entire system.

To define system settings:

On the Setup tab, under Configure, select System Settings.
In System Settings, in Profile Type, select the specific profile to list on the System Settings screen.
Available profile types:
- All
- File—In addition to file-specific system settings, selecting the File profile type displays the "Create Application Folders" button. This feature instructs the system to create a folder structure in the path specified in the Application Root Directory setting.
- ODI—Use to set ODI password and repository connection information. When this information gas been added or changed, you can click Check ODI Connection to view if connection to the ODI agent was made successfully.
- Other—Use to set profiles associated with an EPMA data source, User Language, User Interface Theme, and Default Check Report.
- Point-of-View
The profile type that you select determines the settings that you can add or modify on the screen.
Select the option and add the new value in Value.

If is displayed in the Select field, you can search on the value.

Note:

When you install and configure Oracle Hyperion Financial Data Quality Management, Enterprise Edition, Oracle Data Integrator is automatically installed and configured for you. The database for Oracle Data Integrator is in the same database as FDMEE and the Oracle Data Integrator agent deployed to the FDMEE Managed Server. You should be familiar with Oracle Data Integrator and review the Oracle Data Integrator documentation set before specifying or changing the installation defaults.
Click Save.

Table 1-8 System Setting Profile Options

Profile Type	Profile Option	Profile Description
All	Includes all profile types
File	Application Root Folder	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): `data` `inbox` `outbox` Within the `inbox`, locations are created when they are added in the Locations option. See also FDMEE Application Folder Architecture. 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 Note: An "8.3" notation does not exist in the Microsoft operating systems, although it is accepted as an alias. Also note that it cannot be used as a substitute for the correct UNC path for folder names that include spaces.
File	Create Location Folder	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.
File	Archive Mode	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. When the file is moved to the archive location, it is renamed as follows: `<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`.
File	Excluded File Upload Wild Cards	Specify file extensions that cannot be uploaded. Enter . to disallow all file uploads.
File	Batch Size	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.
File	File Character Set	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. Click to view available character sets. 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.
File	Encrypted Password Folder	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.
File	Workbench Export to File Format	When exporting data, select the desired file format. Available file formats are: CSV (.csv) Excel (.xls) The default file format for exports is CSV.
ODI	ODI User Name	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.
ODI	ODI Password	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.
ODI	ODI Execution Repository	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.
ODI	ODI Work Repository	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.
ODI	ODI Master Repository Driver	Specifies the driver of the ODI master repository. This setting is defined automatically when ODI is configured, but you can customize it if necessary.
ODI	ODI Master Repository URL	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`.
ODI	ODI Master Repository User	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.
ODI	ODI Master Repository Password	Specifies the Oracle Data Integrator master repository password. This setting is defined automatically when ODI is configured, but you can customize it if necessary.
Other	EPMA Data Source Name	Specifies the EPMA Data Source name for the EPMA Interface Data Source.
Other	User Language	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.
Other	User Interface Theme	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.
Other	Default Check Report	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.
Other	Default Intersection Report	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.
Other	Batch Timeout in Minutes	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.
Other	Enable Event Script Execution	Select Yes to enable the execution of application events such as before loading data (BefLoad) or after validation (AftValidate). Select No to disable the execution of application events.
Other	SQL Server Database Provider	Specify the name of the SQL Server database provider. Available SQL Server database providers: SQLOLEDB SQLNCLI10 (SQL Server 2008) SQLNCLI11 (SQL Server 2012)
Other	Log Level	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.
Other	Check Report Precision	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.
Other	Display Data Export Option "Override All Data"	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."
Other	Enable Map Audit	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.
Other	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.
Other	Map Export Delimiter	Sets the column delimiter value when exporting member mappings. Available delimiters are: ! (exclamation mark) , (comma) ; (semi-colon) \| (pipe)
Other	Map Export Excel File Format	Select the Excel file format to use when exporting member mappings: Excel 97-2003 Workbook (.xls) Excel Macro-Enabled Workbook (.xlsm)
Other	Map LCM Format	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.
Other	Drill Type UI	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
POV	Default POV Period	Specifies the default POV Period. These preferences take precedence when no equivalent settings are in Application Settings or User Settings.
POV	Default POV Category	Specifies the default POV Category. These preferences take precedence when no equivalent settings are in Application Settings or User Settings.
POV	Global POV Mode	When this is set to Yes, other POVs (Application Level and User Level POVs) are ignored.