Anda di halaman 1dari 3

Evaluation path in SAP HR

organizational management
December 20, 2011

Evaluation path is a chain of relations defined for a set of objects.

This is defined in table T778A. The relation between the objects is
defined in V_T77AW. one of the standard evaluation paths is O O
S P. This gives all the persons assigned to an org unit and the
child org units with the positions. Transaction OOAW

The evaluation path O O S P is given below.

Several objects linked can represent a structure. Evaluation paths define how a structure is to be created, because objects
may have different kind of relationships.
In an evaluation path you define which objects, relationships and order the structure should display. This is done in
customizing table T778A.
Here you can see that this evaluation path will get for the root org unit, all the positions linked to it using relationship B003,
then from these positions all the employees assigned to these positions via relationship A008, and also from the org unit, all
the org units linked using relationship B002.
I can run this evaluation path with a root org unit in transaction PPSS

The way I like to describe evaluation paths is that they are like a set of directions. In an
evaluation path, you have a starting point, a list of directions on how to get where youre
going, and an ending point. With an evaluation path you tell SAP which OM object (like a
person, org unit, position, etc.) you wish to start with and give it directions to follow on a
specific path to get to another object. You can report on all the objects and values along the
way, not just the start and the end, but for this blog post we will keep it simple. Start
somewhere and end somewhere.
Suppose I want to find the Manager of an employee so what will I do.
So here are our directions:

Start at the employees org unit


Follow the Manager relationship from the org unit to the position that holds the


Once at the position, follow the holder relationship that tells me the person holding
the position.

The standard syntax used to identify a relationship is A/B 000.
Relationship defines the links between 2 objects. E.g. the description A 002 can be read as, A: bottom up
approach and 002: Relationship ->Reports (line) to similarly B 002 can be read as, B: Top Down and 002 :
Relationship -> Is line supervisor of . So, in this view T778V we can maintain both the Top Down and Bottom Up
approach descriptions of the same relationship and hence the appropriate relationship will be used when required.

Structure of Relationships
A relationship between two objects can be structured:




For example, the relationship between a senior position in an organizational unit and another
position in that same unit is hierarchical. The senior position (B 002) is line supervisor to
the lower placed position (A 002) which reports to the position above.
A lateral or flat relationship, for example, is relationship 041, which names a situation where
two jobs are equivalent, and can replace each other. One side of the relationship is A 041,
the other is B 041, but the two sides have equal standing. A relationship between a job and
a position is also a lateral relationship.
A relationship can be one-sided. For example, a relationship between an object (such as a
position) and an external object type (a cost center in Controlling, perhaps), has only one
direction and so is one-sided.