FDMEE Application Folder Architecture

Oracle Hyperion Financial Data Quality Management, Enterprise Edition uses a set of folders that are created under the application root folder. The application root folder is created by the system administrator on the server where FDMEE is installed, and then defined in the System Settings under Configure in FDMEE.

To create the basic file structure, click the Create Application Folder button from the System Settings screen. In addition, application folders and location folders can also be created. If application folders are not used, then location folders are created in the top-level inbox. When application folders are used, then location folders are created in the related application folder.

Here is an example of a possible folder structure:

Image shows Application Folder structure.

The standard FDMEE application uses the following folder structure:

Table 1-1 FDMEE Application Folder Structure

Folder	Descriptions
`data`	The `data` folder contains a copy of each file that is loaded by the system. It is also the root folder for the scripts directory. Each file in this folder is assigned a unique name, and can be opened from the Data Load Workbench by clicking an amount or from the Drill-through screen.
`scripts`	This is the top folder for the `custom`, `event`, and `import` folders. Scripts of these types are stored in these folders.
`custom` `event` `import`	`custom`—Contains custom scripts written in Visual Basic or Jython script. `event`—Contains scripts that are executed for the specified system event and are written in Visual Basic or Jython script. `import`—Contains scripts that are associated with an import format and are `executed` during the import processing step. These scripts are only written in Jython.
`inbox`	Use the `inbox` default directory from which to import source files or as a central repository for all ledger extract files. Because source files can be retrieved from any accessible directory, you are not required to place import files in this directory. When you select the option to create a folder for every location created by the user, they are created in the `inbox`. The `inbox` includes the `batches` and `archivestore` directory.
`archivestore`	Reserved for future use.
`batches`	`batches` is a top-level folder only and it is not used to store files.
`openbatches`	`openbatches` is the location where files are stored by the system. These files contain the "Point of View" in the name so that one or more files can be picked up by the system and loaded without needing to set the POV in the user interface. This is very useful when you need to load many files at a single time.
`openbatchesml`	Similar to the `openbatches` folder; however, these files contain multiple periods in a single file.
`outbox`	The `outbox` folder stores export files created by FDMEE, any error log files from a target application, drill region load files, and drill load logs from the target.
`archivestore`	Reserved for future use.
`logs`	Stores logs generated by the load processes in the format `EPM-APPLICATION-NAME_PROCESS-ID.log`. These logs can be viewed using the Show Log link in the Process Details page of FDMEE.
`reports`	The `reports` folder stores report output generated by the batch reporting process in PDF, HTML or XLS. This folder also includes output from reports run in offline mode.

Note:

To create the folder structure for applications, define the root folder on the Application Settings screen, and then select the Create Application folders option. For example, when you want to run a set of scripts for a specified application, then the use of the application folders is required.