An application object (business object) is often related to particular users in the system (such as MRP controller, laboratory, sales group, purchasing organization, or planner group) by virtue of its master data. The SAP system usesOrganizational Object Types to depict this relationship. These are object types from the Business Object Repository for which the Organizational Type flag is set.
The corresponding business object type must have an attribute that refers to this organizational object type. The organizational object type also has an attribute that refers toOrganizational Management Objects.
In this rule category, the system evaluates this dependency to determine the responsible agents for a business object. Concrete Organizational Management objects (for example, positions or organizational units) must be assigned to the organizational object.
Rule resolution returns one or several Organizational Management objects as a result.
There are some changes required to be made to material master data.
This task should be performed by an employee in the Laboratory/Design Office that is stored in the material master data. SAP delivers the rule LABOR as an example of a rule for agent determination using SAP Organizational Objects. For more information, see
For more information, see
This step must always be performed because you set up Organizational Management objects in a specific way for your enterprise. For more information, see
The corresponding rule container is automatically generated, and contains only the container element
The rule for agent determination that you created is complete and can be used in SAP Business Workflow. When using this rule, you must define binding from the workflow or task container to the rule container. For further information, seeBinding Definitions from Workflow Container and Binding Definitions from Task Container.
For an example of this kind of rule, see theRule to Determine Design Office.