Setting Application Level Profiles

Use the Application Settings option to update or clear application level profiles that apply to the target application.

  To set an application level profile:

  1. Select the Setup tab, and then under Configure, select Application Settings.

  2. In Application Settings, from the Target Application drop-down, select the target application to which the application profile applies.

  3. Select application level profile settings.

  4. Optional: To clear a setting, select the value, and then click Delete.

    The value is removed but is deleted only when you save it.

  5. Click Save.

Table 3. Application Level Profile Options

OptionDescription
Application Root FolderThe Application Root folder is the root folder for storing all files used to load data to this EPM application. You can use a separate root folder for each EPM application.

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.

Selecting the Create Application Folder button 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

outox

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 Character SetSpecify 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 Image shows Search button.
Default POV LocationSpecify the default POV location.

You can also click Image shows Search button to navigate to the default POV location from the Search and Select: Default POV Location screen.

Default POV PeriodSpecify the default POV Period.

You can also click Image shows Search button to navigate to the default POV Period from the Search and Select: Default POV Period screen.

Default POV CategorySpecify the default POV Category.

You can also click Image shows Search button to navigate to the default POV Category from the Search and Select: Default POV Category screen.

User LanguageSpecify the application default language of the user version of FDMEE.

You can also click Image shows Search button to navigate to and select the language.

User Interface ThemeSet the Oracle design pattern for the applications. FDMEE uses BLAF+ as the default user interface value.

You can also click Image shows Search button to navigate to the theme.

Default Intersection ReportSpecify the type of Intersection Check Report to use as the default intersection check report at the application level. Intersection Check 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.
Default Check ReportSpecify the type of Check Report to use as the default check report at the application level. 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.

Enable Event Script ExecutionSelect 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.
Log LevelSpecify 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 Locking

Point of View (POV) Lock feature prevents data from being loaded to a selected POV by locking all locations related to a target application for a given period and category. When you select the “Lock POV” button, a pop-up is displayed with populated Category and Period values based on the profile. You can update the category and period if desired and then lock the POV.

An “Unlock POV” is also available so that you can unlock a locked POV. The POV lock is referenced in:

  • Data Load Workbench

  • Data Load Rule

  • Batch Execution

  To lock a POV:

  1. Select the Setup tab, and then under Configure, select Application Settings.

  2. In Application Settings, and then from the Target Application drop-down, select the target application to which the application profile applies.

  3. Click LOCK POV.

    The Lock POV for All Locations screen is displayed.

  4. Optional: From Category, select the category to update.

  5. Optional: From Period, select the period to update.

  6. Click OK.

    All locations for the selected target application are be locked.

    To unlock the locked POV, click Unlock.