Additional Manual Steps for FDMEE

1. If you are importing data from a flat file, create the FDMEE folder using System Settings and copy the FlatFile.txt used for import.
2. Point the ODI settings to the new source server settings.

   For example, ensure that the ARM database is properly targeted: Navigate to ODI Console http://<server_name>:19000/odiconsole. Expand Topology, Physical Architecture, Technologies, Microsoft SQL Server, ARM_DATA_SERVER_MSSQL, and then click View. Make sure the Oracle Hyperion Financial Close Management ARM database name is correct. If not, update with the correct information:

   1. Launch ODI Studio and log in to the Work Repository.
   2. Click the Topology tab and expand Technologies, then Microsoft SQL Server, and then double-click ARM_DATA_SERVER_MSSQL.
   3. Update the user and password if needed.
   4. On the JDBC Definition tab, update the JDBC URL to use the correct ARM database. For example, update jdbc:weblogic:sqlserver://serverName:port;databaseName=FCM to jdbc:weblogic:sqlserver://serverName:port;databaseName=FCM1125.
   5. Expand and double-click to open the last node, ARM_DATA_SERVER_MSSQL.<DBNAME>.dbo.
   6. From the Database (Catalog) and Database (Work Catalog) lists, select the correct ARM schema.

   7. You might also need to also set the ARM_TGT logical schema. In ODI Studio, click the Topology tab. Expand Contexts and double-click Global. On the Global tab, click Schemas and make sure the Logical Schema ARM_TGT has the correct Physical Schema, for example, ARM_DATA_SERVER_MSSQL.FCM1125.dbo, and then save your changes.

   8. Save and restart the Financial Close Management and Oracle Hyperion Financial Data Quality Management, Enterprise Edition Servers

See FDMEE Application Folder Architecture and Setting System-Level Profiles in Oracle Hyperion Financial Data Quality Management Administrator's Guide for details.