Show TOC

Example documentationExample: Different Talent Group Nominations for the Same Talent in Multiple Talent Review Meetings

 

The following graphic uses an example to show which infotype records the system creates and changes when the same talent is nominated for different talent groups in different talent review meetings.

In this example, the talent T1 is discussed in two talent review meetings at different levels. The talent review meetings each use a separate calibration grid. Therefore, the assignment of talent groups to the boxes of the calibration grid differ in the talent review meetings.

The system creates infotype records based on the first talent review meeting that takes place at a lower level. It creates new infotype records based on the second talent review meeting that takes place at a higher level and delimits the infotype records from the first talent review meeting.

The procedure is as follows:

  1. The talent review meeting TRM1 is held on March 15, 2012 for the level Middle Management.

    1. In the talent review meeting, the talent T1 is classified in a box of the calibration grid to which the talent group Top Talents is assigned.

    2. The talent management specialist TMS1 approves the assignment of the talent T1 to this grid box.

    3. For the central person (object type CP) of talent T1, the system creates a record for the infotype Relationships (1001), subtypes A743 (relationship Has Talent For) and B743 (relationship Comprises Talent) with the following data:

      • Start date: March 15, 2012

      • End date: December 31, 9999

      • Object type of the initiator of the assignment: RM (Talent Review Meeting)

      • Object ID of the initiator of the assignment: Talent review meeting TRM1

      • Assignment was nominated or approved by: ID of the central person of talent management specialist TMS1

      • Object type of the rejector of the assignment: empty

      • Object ID of the rejector of the assignment: empty

      • Assignment rejected by: empty

      • Status of the assignment: Nominated

  2. The talent review meeting TRM2 is held on April 26, 2012 for the level Top Management.

    1. The talent T1 remains assigned to the same box of the calibration grid as in the talent review meeting TRM1.

      However, in the talent review meeting TRM2, the talent group High Potentials is assigned to this grid box. The talent group Top Talents is assigned to a different box of the calibration grid.

    2. The talent management specialist TMS2 approves the assignment of the talent T1 to this grid box.

    3. The system creates a new record for infotype 1001, subtypes A743 and B743 for the central person of talent T1:

      • Start date: April 26, 2012

      • End date: December 31, 9999

      • Object type of the initiator of the assignment: RM (Talent Review Meeting)

      • Object ID of the initiator of the assignment: Talent review meeting TRM2

      • Assignment was nominated or approved by: ID of the central person of talent management specialist TMS2

      • Object type of the rejector of the assignment: empty

      • Object ID of the rejector of the assignment: empty

      • Assignment rejected by: empty

      • Status of the assignment: Nominated

    4. The system changes the existing records for the infotype 1001, subtypes A743 and B743 for the central person of talent T1 as follows:

      • Start date: March 15, 2012

      • End date: April 26, 2012

      • Object type of the initiator of the assignment: RM (Talent Review Meeting)

      • Object ID of the initiator of the assignment: Talent review meeting TRM1

      • Assignment was nominated or approved by: ID of the central person of talent management specialist TMS1

      • Object type of the rejector of the assignment: RM (Talent Review Meeting)

      • Object ID of the rejector of the assignment: Talent review meeting TRM2

      • Assignment rejected by: ID of the central person of talent management specialist TMS2

      • Status of the assignment: Nominated