Use the System Settings Option to update or clear System level profiles that apply to entire system. System settings can be defined only by users with “ Admin” role privileges.
To define system settings:
From the Setup tab, and then under Configure, select System Settings.
In System Settings, from 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).
Other (Use to set profiles associated with an EPMA data source, User Language, User Interface Theme, and Default Check Report.)
Point-of-View
Available profile types:
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.System setting options are described in Table 2.
Note:
When you install and configure FDMEE, 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 the ODI detail.
Table 2. System Setting Profile Options
| Profile Type | Profile Option | Profile Description |
|---|---|---|
| All | Includes all profile types | |
| File | Application Root Folder | Note: The Application Root Directory must be setup on the server, specified in this field, and the Create Application Folder options must be executed as first steps when using FDMEE. When you select the File profile type, the System Setting screen displays the “Create Application Folders” button. This features instructs the system to create a folder structure in the path specified in this field. The folder structure is (with sub-folders in each): datainbox outox Within the inbox, locations are created when they are created in the Locations option. See also FDMEE Application Architecture.When you specify a folder at the application level, scripts are saved to this folder. This is especially important for event scripts that are different between applications. When you do not set up an application level folder, then you cannot have different event scripts by application. Note: Use a Universal Naming Convention (UNC) path for the application root folder when Financial Management and FDMEE are on separate servers. Share permissions on the folder must allow access to the DCOM user for read/write operations. Contact your server administrator to define the required UNC definition. |
| File | Create Location Folder | This setting 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 then do not change it. This option 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 moved 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 the 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 settings determines how many records are to 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. This setting should be determined by Server Memory, and can be adjusted 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. Available character sets are available on the Search and Select screen by clicking . |
| File | Encrypted Password Folder | Specify the directory where the files that store passwords in encrypted form is located. This encrypted password folder is used in conjunction with the “Update Configuration File” button. For more information, see Working with Batch Scripts. |
| ODI | ODI Agent URL | Specifies the URL of the server where Oracle Data Integrator has been installed. |
| 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 it can be customized 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 it can be customized 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 it can be customized if necessary. |
| ODI | ODI Work Repository | Specifies the (execution) repository which contains run-time 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 it can be customized if necessary. You can click and select the driver from the Search and Select: ODI Master Repository Driver screen. For example, enter Oracle.jdbc.OracleDriver.. |
| 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. You can click and select the URL from the Search and Select: ODI Master Repository URL screen. 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 it can be customized 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 it can be customized 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 Note: 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:
|
| 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:
|
| 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. |
| POV | Default POV Location | Specifies the default POV location. These preferences take precedence when no equivalent settings are in Application Settings or User Settings You can also click to navigate to the default POV location from the Search and Select: Default POV Location screen. |
| POV | Default POV Period | Specifies the default POV Period. These preferences take precedence when no equivalent settings are in Application Settings or User Settings. You can also click to navigate to the default POV Period from the Search and Select: Default POV Period screen. |
| POV | Default POV Category | Specifies the default POV Category. These preferences take precedence when no equivalent settings are in Application Settings or User Settings. You can also click |
| POV | Global POV Mode | When this is set to Yes, other POVs (Application Level and User Level POVs) are ignored. |