Ansicht
Dokumentation

TMC_0106 - BAdI: Activities When Approving Talents in Calibration Grid

TMC_0106 - BAdI: Activities When Approving Talents in Calibration Grid

CPI1466 during Backup   General Data in Customer Master  
This documentation is copyright by SAP AG.
SAP E-Book

This Business Add-In (BAdI) is used in the Talent Management (PA-TM) component.

This BAdI performs activities that are a result of the following actions that a talent management specialist or member of a support team performs for a talent review meeting:

  • Approve Assignment of Talents to Boxes of Calibration Grid
  • Undo This Approval (explicitly or by the talent management specialist moving the talent within the calibration grid or from the calibration grid to the screen area Open Assessments)
  • Remove Talents from the Talent Review Meeting
  • Withdraw Talent Review Meeting
  • Delete Talent Review Meeting

If you want to use the BAdI to nominate talents for talent groups, you need to have assigned talent groups to the boxes of the calibration grid. These are not Customizing entries that can be transported to other systems. Therefore, in the system of your choice, from the SAP Easy Access screen choose Human Resources -> Personnel Management -> Talent Management -> Settings. For more information, see Assign Talent Groups to the Boxes of the Calibration Grid.

For more information about the standard settings (filters, single use, or multiple uses), see the Enh. Spot Element Definitions tab in the BAdI Builder (transaction SE18).

Assignment to Talent Groups (HRTMC_RM_CA_TG_ASSIGNMENT)

This BAdI implementation effects the following activities:

  • When the talent management expert approves the assignment of talents to a box of the calibration grid, the system assigns these talents to the talent group or talent groups that are defined for the box.
In doing so, the system creates records for the infotype Relationships (1001) with the subtypes A743 and B743 for each talent. For the relationship 743 (Has Talent For/Comprises Talent), it defines the following additional data:
  • Initiator of the assignment: Object type RM (Talent Review Meeting) and ID of the talent review meeting in which the assignment was made

  • Assignment was nominated or approved by: ID of the central person of the current processor of the talent review meeting in which the assignment was made (talent management specialist or member of the support team)

  • Reason for nomination or approval: The approval reason that you defined for a grid box when assigning the talent groups to the boxes of the calibration grid

  • Status of the assignment: Nominated

The start date of the infotype record is determined by the parameter Date (IV_KEY_DATE) of the method Perform Activities (DO_ACTIVITIES). The end date of the infotype record is the system end date (12/31/9999).
  • When the talent management specialist performs one of the following actions, the system restores the previous status for the talents affected:
  • Withdraw approval of the assignment to boxes of the calibration grid

  • Move talents in the calibration grid

  • Remove talents from the talent review meeting

  • Withdraw or delete talent review meeting

In doing so, it deletes the assignments that were made by the talent review meeting concerned. If assignments were delimited as a result of the talent review meeting, the system restores these assignments.
  • If another talent group assignment is also made for the same talent in another talent review meeting, the system creates further records for infotype 1001 with the subtypes A743 and B743 for this assignment.
  • If a different talent group assignment is made for a talent in another talent review meeting with a higher level, and the original talent group in the talent review meeting with the higher level is also assigned to a box of the calibration grid, the system delimits the assignment from the talent review meeting with the lower level.
In doing so, it defines the following additional data for the delimited assignment:
  • Rejector of the assignment: Object type RM (Talent Review Meeting) and ID of the talent review meeting that resulted in the delimitation

  • Assignment rejected by: ID of the central person of the current processor of the talent review meeting that resulted in the delimitation (talent management specialist or member of the support team)

Example
In the talent review meeting RM1, the talent group TB1 is assigned to the grid box A. The talent management specialist approves the assignment of the talent CP1 to this grid box. The talent CP1 is thus assigned to the talent group TB1.
In the talent review meeting RM2, the talent group TB1 is assigned to the grid box B. However, the grid box A is assigned the talent group TB2. The talent CP1 remains in grid box A. The talent management specialist approves this assignment. The talent CP1 is thus assigned to the talent group TB2. The assignment of the talent CP1 to the talent group TB1, which was created by the talent review meeting RM1, is delimited for the date on which the talent review meeting RM2 was conducted.

Note

If a manager had already nominated a talent for a talent group, this assignment is not affected. In this case, no talent review meeting ID is stored in the additional data for the relationship 743. The BAdI implementation does not process such infotype records.

The BAdI implementation sets an exclusive lock for the talents concerned (object type CP (Central Person)). The method Activities on Saving (FLUSH) removes this lock.

For information about the implementation of BAdIs in the context of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.

If you want to use the BAdI to nominate talents for talent groups, we recommend that you use the default implementation. If you want to perform different or further actions, create a customer-specific BAdI implementation and activate this instead of the default implementation.

BAdI method documentation






ROGBILLS - Synchronize billing plans   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 8609 Date: 20240523 Time: 163016     sap01-206 ( 131 ms )