Example: Person "is assigned to" Cost Center
The relation Person „is assigned to“ Cost Center is an example of an 1:n relationship. A person is assigned to one cost center, a cost center may have more than one person assigned to it.
The relation uses the attribute CostcenterId, which is the Primary Key in the CostCenter business object, and a Foreign Key in the Person business object.
Side of Relation
|
Attribute
|
Value
|
Meaning
|
Source:
|
Relation attribute may be empty
|
true
|
Relation is optional. You may document that a person is assigned to a CostCenter, but it is not mandatory
|
|
Instances are relation dependent
|
false
|
Instances are not relation dependent. It is possible to change the CostCenter of a person (without deleting).
|
Target:
|
Relation attribute may be empty
|
true
|
Relation is optional. You may document that a person is assigned to a CostCenter, but it is not mandatory. A cost center may have no persons assigned.
|
|
Instances are relation dependent
|
false
|
Instances are not relation dependent. It is possible to change the assignment (without deleting).
|
|
Relation attribute is collection
|
true
|
More than one person may be assigned to a CostCenter
|
The result is a section for „CostCenter“ in the business object editor for Person (assuming the relation is configured into the view in the View Customizer).
The usual options for processing relations New, Delete, Edit and Search are available to change the cost center.
|