Infotype that defines the Relationships between different objects.
You indicate that a employee or user holds a position by creating a relationship infotype record between the position and the employee or user. Relationships between various organizational units form the organizational structure in your enterprise. You identify the tasks that the holder of a position must perform by creating relationship infotype records between individual tasks and a position.
Creating and editing relationship infotype records is an essential part of setting up information in the Organizational Management component. Without relationships, all you have are isolated pieces of information.
You must decide the types of relationship record you require for your organizational structure.
If you work in Infotype Maintenance, you must create relationship records manually. However, if you work in Simple Maintenance and Structural Graphics, the system creates certain relationships automatically.
There are many types of possible relationships between different objects. Each individual relationship is actually a subtype or category of the Relationships infotype.
Certain relationships can only be assigned to certain objects. That means that when you create relationship infotype records, you must select a relationship that is suitable for the two objects involved. For example, a relationship between two organizational units might not make any sense for a work center and a job.
The report RHRLAT0 (Allowed Relationships of Object Types) reports on the relationships permitted for particular objects. The Relationship infotype screen also includes an Allow.Relationships option. If you choose that option, a dialog box displays a list of allowed relationships.
Organizational Management includes a predefined set of standard relationships. You can select from those, or you can create other relationships. For further information, see the Implementation Guide (IMG) under Organizational Management > Basic Settings > Data Model Enhancement > Infotype Maintenance.
You can create and edit numerous relationship records for a single object. An organizational unit can be related to several different organizational units: to a position, for example, as well as to a work center.
The benefit of defining relationship records lies in the reporting results that you obtain when you report on particular relationships between objects in an organizational plan.
This happens as follows: