|
See
Also
In some cases, you might want
to change the export model of an application. For example, if you
want to exclude some business objects or tables from the exported
application, or if you want to put restrictions on the records
being exported.
For this purpose, you can do
an ad-hoc change of the export model of an application.
However
|
IMPORTANT:
|
Re-generating the Export
Model of an application overwrites the existing model,
including all your changes.
|
Always first consider to
define an application basket instead of changing the export model
of an application. This is more flexible, and leaves the original
application model intact.
On the other hand, if the
application model is changed often (e.g. in a development phase),
then changing the export model could be a strategy.
To change the export model of
an application:
| 1.
|
From the Repository Manager menu, select Define, Repository
Versions. |
The Repository Versions
window opens.
| 2.
|
Perform a query that retrieves the repository version for which
you want to change the export model. |
|
ALTERNATIVE:
|
You can also open the repository version from the catalog, by
double-clicking on the name.
|
| 3.
|
Check that this repository version has been exported, and an
export model has been generated. |
|
·
|
The Exported On field
contains the date and time of the last export. |
|
·
|
The Model Generated
field contains the date and time of the last generation. |
| 4.
|
Click the Business Areas
button at the bottom. |
The Business Areas in Repository Version
window opens.
| 5.
|
In the Business Areas Exported
part of the window, delete or
Exclude all business objects that you do NOT want to be
exported. |
| 6.
|
Likewise, for each included business object, in the Application
Tables Exported in this Business Object
part of the window, delete
or Exclude all tables that you do NOT need. |
The Export Model is adapted
automatically.
|
