Understanding the OVFS Import Function

You can use the OVFS import function to upload data that was created in another environment and then downloaded to a zip file. To import the OVFS components from the zip file, access the import function for the component type you are working with. For example, if you are importing row definitions, use the import function available in the Row Definitions program.

When you export OVFS components to a zip file, the system creates a readme.txt file in the zip file. Oracle recommends that you review the readme.txt file before you begin the import process.

If all of the components in the zip file are new to the import environment, the system downloads them when you click the Load button and does not notify you of the names of the components that were downloaded. During the import process, the system does not display the names of new components; it displays only the names of components that have corresponding components in the import environment. The system determines which components in the zip file have corresponding components in the import environment by comparing the key fields of the components.

If the zip file contains only corresponding components, or a mix of new and corresponding components, the system displays the Import Option form, which allows you to select how to download the components. The Import Option form lists only the corresponding components. You must use the readme.txt file to identify the new components.

The Import Options form lists the row, column, and statement definitions; the statement versions; and the BI Publisher Layout Editor files that are in the zip file and that have corresponding records in the import environment. Not all components will exist in all zip files. The contents of the zip files are different for the different components that you can export from one environment and import to another. For example, if you are importing records created using the export function for row definitions, the Import Options form lists only row definition records that exist in both the zip file and the import environment. New components might also be available for download, but the Import Options form does not list new components.

You can import selected files from the zip file, or you can import all of them. If you select an option to import the corresponding components, the system replaces the existing component record in the import environment.

See Contents of the Export Zip File for Row and Column Definitions andContents of Export File for Statement Definitions.

The Import Options form includes the following buttons:

  • Cancel

    Use this option to stop the import and exit the form.

  • Replace

    Use this option to import without reviewing each replacement record. If you want to review each replacement record, use the Prompt option instead of the Replace option.

    When you use this option, the system will also import the new components, if any exist in the zip file.

  • Prompt

    Use this option to have the system prompt you to confirm each replacement record before it imports and overwrites existing records. When you select this option, the system opens the Verify Update form so that you can confirm the import or skip the record.

    When you use the Prompt option, new records are automatically inserted into the appropriate tables. The system prompts you to confirm whether to insert a record for only those records that will overwrite an existing record.

  • Skip

    Use this action to have the system perform only additions. When you use this option, the system does not overwrite any existing data and does not prompt you to confirm or skip records.

You must have write permissions for the location to which you import the files. For example, records for layouts are written to the BI Publisher server. If you do not have permissions to write to that server, you cannot import layout records.

You must also have permissions to work with the financial statement components that you want to import. For example, if you do not have permissions to create statement definitions, then you cannot insert new statement definition records.