Defining Data Contents

Previous Next

See Also

Defining data contents consists of the following steps:

1. 1. State the table objects with their attributes.

The order line object, for example, contains the attributes needed to order one type of article in a certain quantity within an order.

You can proceed in two ways:

· Create the table object in the repository and then refer to it in the data-content of this business object.


· State that the table object has to be created. You cannot refer to it however, as it does not exist yet. Enter it as "Temporary Content".


If you define a business object with subtypes in the structure, calculate/add data contents, and export this business object, then the subtype definition and presentation are not added to the export file.

If you add the supertable directly to the export definition, and define include subtype tables, then the subtype tables, definition, and presentation are added to the export file.

2. Inter-object relationships

For example, express that an order is meant for delivery of order lines.

Again you can either:

· Define the inter-object relation in the repository


· Only state the need for such an inter-object relation in the data contents of the business object. Again you have to provide an alternative identifier in the data contents.

There is a special mechanism in the repository to link inter-object relationships to business objects automatically.

3. Domains

Attributes in table objects are based on domains. The domains are therefore needed in the repository before the table object can be created. It is not necessary to define all these domains as data contents of the business object beforehand. There is an add data contents facility that can be used to generate the domain data contents later.

It is not always necessary to define the domains as data contents at all. If you want to shop a business object from one repository to the other make sure that all domains are included in the business objects data contents.