Show TOC
Create
Relationships
In this step, you make the settings that are
required for creating relationships.
By creating relationships between objects, you
can display all the structures that exist in Personnel Management.
Relationships are special
subtypes of infotype 1001. Each relationship has two
relationship types , indicated by A and B. For each relationship
created (A or B), the corresponding inverse relationship is automatically set
up.
You can make the following settings:
- You can create new relationships.
- You can control the response of the system
(error messages, warnings, information) if the 100% mark is exceeded in the
case of "weighted" relationships.
- You can show or hide the weighting percentage
of a relationship and, if required, define additional data for a relationship.
You can specify, for example, in the view 'Additional relationship info'
whether the recursiveness check should be active for your own relationships or
not.
Caution!
Apart from
controlling the weighting, you should consult SAP before making any other
changes to this view.
- You can define the object
types that are allowed for each relationship and inverse
relationship.
- You can set up external
relationships.
External
relationships are relationships between external object types i.e. object
types that are not stored in the PLOG database in Personnel Development and
Planning. (See also the step
"Maintain object types").
- You can enter a time
constraint for each relationship.
- You can change the "alias" name (semantic
abbreviation) of a relationship.
Note
You can create 3-character relationships in the
range "AAA" to "ZZZ". You should only use letters for this!
Example
| Relationship |
Inverse relationship |
| A002 reports to |
B002 is line supervisor of |
| A003 belongs to |
B003 incorporates |
| A007 describes |
B007 is described by |
Requirements
Before you create a new relationship, it should
already have been created as a subtype of infotype 1001 "Relationships" in the
step
"Maintain subtypes".
Activities
1. Create new
relationships, if necessary.
2. Specify
whether an error message, a warning or an information message should be issued
when a weighted relationship exceeds 100%.
3. Specify
whether the weighting percentage of a relationship should be displayed or
hidden in the infotype 'Relationship'.
4. Deactivate
the recursiveness check, if necessary.
5. Specify
which relationships should be allowed for which object types.
6. If you have
created external object types, you may have to create the required external
relationships.
7. Enter a time
constraint for each relationship and inverse relationship.
8. Only change
the relationship abbreviation ("alias" name) if it is absolutely
necessary.
Note
The "Not maint."
field in the view "Allowed relationships" does not have any effect on
Customizing settings. This field (if it is set) merely specifies that the
relationship in question cannot be maintained using the standard
transactions.