Organizational Objects
Objects that are used to create an organizational plan in Organizational Management . The following object types are available:
Organizational plans can also include organizational objects that come from components other than Organizational Management (cost center or person (employee or user), for example) or objects defined in customizing.
You can relate organizational objects in two ways to create an organizational plan:
-
you can either relate objects of the same object type in separate hierarchies or list them in separate catalogs.
-
or you can relate objects of different object types and in so doing relate the hierarchies and catalogs.
These relationships enable you to depict multi-dimensional dependency in your enterprise's organizational plan.
It is not mandatory to use all of these objects in your plan. You do not have to define work centers, for example, if you do not find them applicable. You do not have to assign tasks to your jobs and positions. You must, however, create organizational units.
By determining a validity period for every organizational object, you can display and evaluate situations in the past, present and future.
An organizational object comprises:
-
a short and long description
-
an 8 digit ID number and a description
-
a relationship, which defines the link between the object and other objects
-
various object characteristics
-
a validity period and a time constraint
-
a status indicator
For further information on creating and maintaining organizational objects, see: