---

Export Wizard Step 1 dialog

Use this dialog to choose the Discoverer objects that you want to export to a file. You can export the entire EUL, one or more business areas, one or more EUL objects (for example, folders, item classes, workbooks, the automated summary management (ASM) policy).

For more information, see:

"About copying EULs and EUL objects by exporting and importing"

"Creating and Maintaining Business Areas"

What do you want to export?

• The entire End User Layer

  Use this option if you want to export the entire EUL to a file (that is, all business area definitions, folders, item classes, item hierarchies, date hierarchies, PL/SQL function registration information, summary folders, workbooks and the automated summary management (ASM) policy).

• Selected Business Areas

  Use this option if you want to export one or more business areas to a file (that is, selected business area definitions and their folders, item classes, item hierarchies, date hierarchies, PL/SQL function registration information, summary folders, workbooks and the automated summary management (ASM) policy).

• Selected objects in the End User Layer

  Use this option if you want to export one or more EUL objects to a file (that is, selected business area definitions, folders, item classes, item hierarchies, date hierarchies, PL/SQL function registration information, summary folders, workbooks and the automated summary management (ASM) policy).

Notes

• Note that you are only exporting the definition of the EUL, the business area, or the object being exported. You are not exporting the database containing the EUL tables, or the EUL tables themselves. Nor are you exporting the database objects referenced by the EUL objects. If 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?")