Business objects are the main actors in a company. They split up into real things such as partners and goods and organizational terms used in accounting such as warehouses, costs, money-depots or contracts.
On principle quite "dumb" data containers. Direct modelling of the real world, little abstraction possible. Conforms to traditional relational entities, since data organization should be prioritized within and among the entities.
Inherent attributes:
- can be arbitrarily structured (os_list structures: REL_MN zu CX_STRUCTURED)
- can be arbitrarily allocated (os_set allocations: REL_MN zu CX_ALLOCATION)
If an object gets back-referenced via CX_SINGLE_ALLOCATION::object, this
object is used by the allocator. E.g. use in a higher-level part,
specification of percentages for cost allocation,...
If an object gets back-referenced via CX_ALLOCATION:allocator, this
object describes its resources: bills of material, job schedule,
capacity bond ...
- can be arbitrarily controlled (os_list monitors)
- can be arbitrarily allocated to clearing objects (os_list clearingObjects)
- has got data extension (CX_GENERAL_TERMS* generalTerms)
Fat interface functions:
Customer()
Supplier()
Overloaded functions:
Condition() --> tries to get data/call functions as intelligent as
possible in connection with CX_CONDITION, CX_GENERAL_TERMS.
IntelligentData() --> uses provided connections, such as CX_PARTNER <-> CX_PARTNER_CAST
| Module | Brief Description |
|---|---|