Object Relationship Model (SAP Library - Object Relationship Service)

Object Relationship Model

Definition

Set of regulations by which objects can be linked and which describes the meaning of the relationships.

Use

In the object relationship model, you maintain the connections between the different documents on a time and causal basis. The following relationships are listed in the model:

The role in which a document occurs in the relationship.
The type of the relationship between two roles in which the documents can occur.
Further attributes of your application that you additionally assign to the relationship.

The attributes can then later be displayed with the related objects.

Example

The object or document types "request for quotation" and "quotation" are in a unique predecessor-successor relationship. That is the meaning of the relationship which is defined in the model. Thus, a request for a quotation can never be linked as a successor of a quotation. The predecessor-successor relationship also applies to other object types.

For more information, see Creating Object Relationship Model.

Structure

A model consists of:

Roles (more precise: role types): You must describe what meaning an object has in a specific relationship. An object type can occur in several roles and vice versa several object types can be assigned to a specific role type.

Example

The document type "quotation" can appear in both the role of the predecessor and also in the role of the successor document.

A person can appear in both the role of the superior and also in the role of the employee.

By assigning its type to a role, a BOR object can be linked in this role. Relationships are always written between objects in specific roles.

Relationship types: You must describe what meaning the relationship has between two objects (in their roles). There are two descriptions of a relationship type according to whether the relationship from object A with respect to object B or vice versa shall be displayed.

Example

A request for a quotation causes a quotation. Oppositely, a quotation consists of a request from a quotation.

Object A belongs to object B. Inversely, object B contains object A.

You must define the application table in which the relationships of this type should be written. It must have the same structure as in table SRGBINREL.

The model restricts the assignment of roles to relationship types: Two different role types can always only be in a specific relationship to one another, represented with a specific relationship type.

Attributes for relationships (optional): You may want to describe your relationship through more parameters than just through its type.

Diagram: Example for a model