Loading the Metadata Import File

To load the metadata import file:

1. Create a metadata import file for each artifact (dimensions, smart lists, and exchange rate tables) that you want to import. See Creating the Metadata Import File.
2. Click Application, and then click Overview.
3. Click Dimensions, and then click Import.
4. On the Import Metadata page, click Create.
5. Select the location of the metadata 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 you're importing.

   • Inbox: Loads the import file or files from the server. Enter the name of the file in Import File. See Uploading and Downloading Files Using the Inbox/Outbox Explorer.

6. For File Type, select Comma delimited, Tab delimited, or Other.

   If Other is selected, 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:

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

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

   • Clear Members is unavailable in certain dimensions where members must exist and are critical to the application.

     Currently, these dimensions are Currency, Period, Scenario, Version, and Years.

   • Members that can't be deleted in the dimension editor for any reason (for example, because they're used in a form or in a validation rule) won't be deleted.

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. See Managing Jobs.

   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. See Uploading and Downloading Files Using the 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. See Duplicating Jobs.

9. Optional: If the location selected is Local, click Validate to test whether the import file format is correct.
10. Click Import to run the import operation.

If the cubes listed in the import file don't match the cube names in the application, the application will ignore unrecognized cube columns.

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.

When performing metadata loads as a part of cloning environments or importing snapshots using Migration or EPM Automate, Oracle Enterprise Performance Management 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.