Use this dialog to start the import process and monitor its status as Discoverer processes each EUL object.
When you click the Start button, the status bar at the top of the page shows the percentage of the import that has completed.
For more information, see:
"About copying EULs and EUL objects by exporting and importing"
"How to import EUL objects from a file using the Import Wizard"
Use this button to start the import process.
Use this window to monitor messages as they are displayed. Two types of message are displayed:
information messages providing information about imported objects
warning messages, providing warnings about potential problems
Use this button to specify the import log file name and location using the Save As dialog. The log file will have .txt as the suffix.
Tip: It is a good idea to give the log file a similar name to that of the export file that you are importing. A descriptive name makes it easier to locate the file later on.
Use this button to clear the messages from the Log field.
Use this button to stop the import. You might want to stop the import if there are warning messages in the Log field.
When you stop an import, everything that has already been imported is rolled back.
Use this button after a successful import to commit the import transactions to the database.
Note that you only import the definition of the EUL, the business area, or the object being imported. You are not importing the database containing the EUL tables, or the EUL tables themselves. Nor are you importing the database objects referenced by the EUL objects. When you import a business area or object into a database, the following conditions must apply before Discoverer end users can view the data referenced by the imported business area or object:
the database tables referenced by the imported business area or object must exist in the database
database users must have sufficient privileges to access the database, the EUL tables, and the database objects, that the imported business area or object reference (for more information, see "Controlling Access to Information" and "What are the data access prerequisites?")