Connection to the Object Relationship Service

Use

Use of the object relationship service in your application therefore makes sense if the relationships do not posses any of the attributes sent out using the relationship semantics and the semantics of the roles. For example, the relationship between the document header and the document items should be retained in separate application tables in this way, if attributes of the individual items are to be directly accessible at header level.

Prerequisites

The objects that are to be related have to be created as business objects in the Business Object Repository or as business classes.

Process

1. Create runtime tables for the relationships

   Create the table with a 16 RAW GUID as the primary key. The tables have to receive two indices so that the relationship records can be accessed using one of the two business references. Use the following tables as templates for your relationship tables:

   SROBLBREL template table for binary relationships

   SROBLROLB persistent roles in the BOR

   SROBLROLC persistent roles in the class library

2. Creating an object relationship model

   For information on this step, see the Creating Object Relationship Model.

3. Including relationships in your application

   You can create, call and delete relationships with the methods of the CL_BINARY_RELATION class interface. For more information, see the method descriptions of the CL_BINARY_RELATION class.