Loading the Metadata Import File

To load the metadata import file:

1. Create an import file for each artifact (dimensions, smart lists, and exchange rate tables) that you want to import. See Creating the Metadata Import File.
2. On the Home page, click Application.
3. Click Overview, then click the Dimensions tab, and then click Import.
4. On the Import Metadata page, click Create.
5. Select the location of the import file or files:

   • Local—Loads the import file or files from a location on your computer. For Import File, click Browse to select the import file on your computer for the artifact that you’re importing.

   • Inbox—Loads the import file or files from the server. Enter the name of the file in Import File.

6. For File Type, select an option:

   • Comma delimited

   • Tab delimited

   • Other. Enter the delimiter character that is used in the import file. For a list of supported delimiter characters and exceptions, see Other Supported Delimiter Characters.

7. Select Clear Members to delete members not explicitly specified in the load file before performing the import.

   Note the following guidelines:

   • Any member not specified is deleted from the outline after importing the dimension unless it is an ancestor of a member that was specified, or it is a base member of a shared member that was specified.

   • If Clear Members is not selected, the import process will only add or update existing members. Oracle recommends loading the metadata file without selecting Clear Members to make sure that the file loads successfully. Then, select Clear Members and execute the import process again.

   • If you add accounts manually in a metadata load file with the Exchange Rate Type as Amount Override or Rate Override, make sure the Clear Members option is not selected, so that the shared entries are created correctly under Historical accounts.

8. Optional: If the location selected is Inbox, click Save as Job to save the import operation as a job, which you can schedule to run right away or at a later time. You can't select this option if Local is selected.

   Saving an import operation as a job is useful to batch a load sequence; for example, import metadata, then import data, and then run rules when the data load is complete.

   Note:

   • Saving an import operation as a job is useful to batch a load sequence; for example, import metadata, then import data, then run rules when the data load is complete.

   • You can run up to five import jobs at one time.

   • If you want to review the data that was rejected during the metadata import job, you can specify an Error File on the Save as Job dialog. This file will provide information about the metadata records that were not imported for each dimension. If an error zip file is specified, a separate error file is created for each dimension, then the error files are zipped together, and the zip file is stored in the Outbox where you can download the file using Inbox/Outbox Explorer.

   Tip:

   To streamline the job creation process for subsequent Import Metadata jobs, you can duplicate an existing job using the Save As option, then update it.

9. Optional: If the selected location is Local, click Validate to test whether the import file format is correct.
10. Click Import to run the import operation.
    After importing the metadata, the file is deleted from the Inbox/Outbox folder.

    If the import fails, a Failed status will display in the Last Validate/Import column. Click Failed to view the detailed status. If the import is successful, a Completed status will display in the Last Validate/Import column. To view details about the successful import, click Completed, and then in the Show drop-down, select All.

11. If the import process is successful, the Refresh Database dialog box prompts you to refresh the database. To refresh, click OK.

You can view the import status in the Jobs console. See Viewing Pending Jobs and Recent Activity.

When performing metadata loads as a part of cloning environments or importing snapshots using Migration or EPM Automate, EPM Cloud uses the multi-pass solution. This solution automatically initiates another load of the same metadata input file if the previous metadata load resulted in rejected records. For Financial Consolidation and Close, multi-pass also resolves issues with forward referencing of plug accounts.