Business Object Repository (SAP Library - BC - SAP Business Workflow

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).

Only 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 via 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, development class and component

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

Relationships between object types

Regardless of its assignment to development class (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. 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.
	Passes on to
Composition	Is contained in	"Is part of" relationship between object types. The object type OrderItem "is part of" the object type Order . The object type Order is then the aggregate type of the object type OrderItem . With composition the "is part" object type normally has a key that is an extended version of that of the aggregate type (for example the order key plus the item) and completely different functionality. For further information about maintaining this relationship, refer to Interface Aggregate.
	Contains
Interface implementation	Implements	Relationship expressing which object types support an interface. To maintain this relationship, the relevant interfaces must be entered as components of the object type.
	Is implemented by
Association	Is referenced	Relationship between object types resulting from an attribute referencing another object type as an object reference. The object type Customer is referenced in the attribute OrderingParty of the object type SalesOrder .
	References