There are several options for how to load metadata to an application. You must select one type of load method: merge or replace. You have the option to clear all metadata before loading the new metadata and you have the option to check data integrity. Table 21 describes how to use each type of load option.
Table 21. Metadata Load Options
Load Option | Description |
---|---|
Merge | If a dimension member exists in the load file and in the application database, then the member in the database is replaced with the member from the load file. If the database has other dimension members that are not referenced in the load file, the members in the database are unchanged. For example, a database contains entities CT, MA, and CA. You use the merge method to load a metadata file containing new information for CA only. In the database, CA is updated with the new information and MA and CT remain in the database and remain unchanged. |
Replace | All dimension members in the application database are deleted and the members from the load file are put into the database. For example, a database contains entities CT, MA, and CA. You use the replace method to load a metadata file containing new information for CA only. In the database, CT and MA are deleted and the only entity will be CA with the new info from the load file. |
Clear All Metadata Before Loading | All dimension members and corresponding data, journals, and intercompany transactions in the application database are deleted. Note: If this option is selected it overrides the function of the merge and replace methods. |
Check Integrity | Checks the metadata against the data to ensure integrity. See Metadata Referential Integrity. |
Note: | Oracle recommends that you add Financial Management to the exceptions for your Web pop-up blocker. When you perform some Financial Management tasks on the Web such as loading data, a status window pops up showing the task status. If you have a pop-up blocker enabled on your computer, the status window is not displayed. |
Note: | This option is only available if you open a Classic Financial Management application. |
In the Metadata File text box, enter the file name to load; or click Browse to find the file.
Note: | By default, metadata files use the XML or APP file extension. The load process accepts other file extensions such as TXT or CSV, however, Oracle recommends that you use the XML or APP file extension. |
If you are extracting to an APP file, in the Delimiter Character text box, enter the character to be used to separate the metadata in the file.
Delimiter characters are necessary only for ASCII files with the APP file extension. Delimiter characters are not necessary for XML files. These characters are valid:
, ~ @ $ % ^ | : ; ? \
Note: | Use a character that is not used in the file name or in any other way in the file. For example, if you use the comma in an entity description, you cannot use the comma as the delimiter. |
Optional: In the Load Options section, select Clear All Metadata Before Loading.
Note: | If you select this option, you cannot select elements in the Metadata Options section. |
Optional: Select Check Integrity to check the metadata file against the data in the current application.
It is highly recommended that you select this option as it ensures that the application is not adversely affected by the metadata in the load file.
Note: | If integrity errors occur, they are written to the metadata log file and no portion of the file is loaded into the application. |
You must fix the errors before you can continue with this procedure. See Metadata Log File Referential Integrity Errors.
In the Load Options section, select one of these load methods:
Merge
Replace
In the Metadata Options section, select the types of metadata to load.
Tip: | Use the Select All and De-select All buttons to quickly select or clear all metadata types. |
Optional: Click Scan to verify that the file format is correct.