Business Object Repository

Use

The Business Object Repository contains the definition of the object type components and their implementation (hence all information about the object types).

The object types defined in the Business Object Repository can be addressed in the definition and runtime components of SAP Business Workflow.

Integration

You access the Business Object Repository and the object types therein using the Business Object Repository Browser.

Features

The Business Object Repository contains the following classes of object type:

Business object types reflected in the data model
Organizational types such as company code, plant, or sales organization
Technical object types such as text, note, work item, or archived document

You can define your own object types taking into account the naming conventions.

Assignment Between Object Type, Package, and Component

Each object type is assigned to an application component indirectly using its package. Object types stored as local objects are not assigned to any application component.

Relationships between object types

Regardless of its assignment to a package (and the resulting assignment to an application component), an object type can have various relationships to other object types:

Inheritance	Inherits from	Relationship between object types allowing common attributes and methods to be passed automatically from supertypes to subtypes. The object type from which attributes and methods are inherited is the supertype. The subtype inherits the attributes and methods from the supertype. The supertype's implementation program associated with the attributes and methods is referenced. Inherited attributes and methods can be redefined for the subtype. The interface, however, may only be extended.
Inherits to	If the attributes and methods of the supertype are known, it is only necessary to describe the differences (changes and extensions) in the subtype in question. All other attributes and methods defined once are used again which reduces the implementation work involved. The error probability when changes are made later also decreases. In this inheritance the subtype has the same key fields as its supertype, but extended functionality.
Composition	Is contained in	"Is part of" relationship between object types. Example The object type Aggregate "is part of" the object type Order. The object type Order is then the aggregate type of the object type Aggregate.
contains	In this composition, the "Is part of" object type normally has a key that is enhanced in contrast to the Aggregate Type (for example: Key of the rorder plus position) and a complemetely different functional scope. For more information about maintaining this relationship, see Interface Aggregate.
Implementing Interfaces	Implements	Relationship expressing which object types support an interface.
Implemented by	To maintain this relationship, the relevant interfaces must be entered as object type components.
Association	Is referenced	Relationship between object types resulting from an attribute referencing another object type as an object reference.
References	Example The object type Customer is referenced in the attribute SoldToParty of the object type Customer Order.