Skip to Content
Technical Articles

Role of Integration Switches in Replication of Data from SuccessFactors to SAP ERP

Introduction:

Integration is one of the most vital factor in SAP HR system. The Integration moves the data from Organization Management Tables to PA tables. It is required to keep the data consistent between the OM and PA modules of SAP HR. The Integration is maintained through a Switch which is accessed through the table T77S0, the role of this switch can be utilized in Replication from SuccessFactors to SAP ERP also when we need to allow only certain Objects of Organization Chart alone needs to be Replicated.

Role of Integration Switches in Replication from SuccessFactors to SAP ERP

Firstly, Implications PA/PD integration to integration Employee Central to SAP ERP HCM, and how can we find out whether it’s active or not.

In SAP ERP HCM system, there will be an active integration between Organizational Management (OM) and Personnel Administration (PA), called PA/PD integration. PA/PD integration synchronizes the Organizational Management data, such as position, job, organizational unit, or cost center between Organizational Management and Personnel Administration. We can use PA/PD integration if we are going for replicating the employee master data and organizational assignment data from Employee Central to SAP ERP HCM to synchronize organizational data (position, job, org unit, cost center) between the Relationships (1001) infotype in Organizational Management and the Organizational Assignment (0001) infotype in Personnel Administration.

What PA/PD integration means for integration between Employee Central and SAP ERP HCM

In Personnel Administration, a person (object type P) can be assigned to a cost center and to organizational plan data: position, job, organizational unit. The assignments are stored in the Organizational Assignment (0001) infotype.

  • If we are using the employee master data replication message only, the message updates cost center from Employee Central and fills the default position from SAP ERP HCM Customizing (using the PLOGI PRELIentry in the T77S0 table).
  • If we are using the organizational assignment replication message, the message creates relationships in infotype 1001 between:
    • person and position (P –S)
    • position and cost center (S – K)
    • position and organizational unit (S – O)
    • position and job (S – C)
  • If PA/PD integration is not active, the person (object type P) is the only link between the data stored for Personnel Administration and for Organizational Management. The objects and the relationships aren’t synchronized across the two components.
  • If PA/PD integration is active, infotype 1001 of Organizational Management and infotype 0001 of Personnel Administration are kept in sync. This means the Organizational Management fields position, job, org unit, and cost center are synchronized with the corresponding fields in infotype 0001 of Personnel Administration.
  • If the employee is a new hire, the organizational unit and the job are left empty once the employee is created. The Positionfield is filled with the default position from SAP ERP HCM Customizing. After the organizational assignment message is processed in Organizational Management, the Organizational Management fields are replicated to the fields: position, job, organizational unit and cost center in infotype 0001 in Personnel Administration by PA/PD integration.

The employee master data replication message updates fields in infotype 0001 apart from Organizational Management fields for position, job and organizational unit. These fields are updated by the organizational assignment message in Organizational Management and then synchronized by PA/PD integration.

Keep in mind!

To have organizational assignment replication requests processed, we need to schedule the database update program as a regular background job. Processing of org assignments on its part triggers PA/PD integration

If PA/PD integration is not active, the organizational data fields of infotype 0001 (such as Cost Center) are updated by employee master data replication if a corresponding field mapping is defined in Customizing, in the template group we use for employee master data replication.

If PA/PD integration is active in wer system, organizational assignment replication updates the organizational data fields in infotype 0001. 

How PA/PD integration is enabled in SAP ERP HCM Customizing

Integration between Organizational Management and Personnel Administration is active if the value of the PLOGI ORGA switch in table T77S0 is set to X. Integration can be restricted for subsets of employees using the Control: Integration of Personnel Planning and Master Data Management (PLOGI) feature.

We can find these settings in SAP Customizing for Personnel Management, under Organizational Management   Integration Iwith Personnel Administration    Set up Integration with Personnel Administration. Choose Basic Settings to set the switch or Participate in Integration to maintain the PLOGI feature.

Restrict Relations Created When Replicating Organizational Assignment

Through Configuration we can decide which relations we want to create in the Enterprise Resource Planning (ERP) system when replicating organizational assignments from SAP SuccessFactors Employee Central.

The employee’s (object type P) relation to a position (object type S) is always created, independent of the settings we make here.

By default, also the following relations are created for the employee’s position:

  • Position to organizational unit (object type O)
  • Position to job (object type C)
  • Position to manager’s position (object type S)
  • Position to cost center (object type K)

If we want to create these default relations for the employee’s position, we don’t need to make any settings here.

If we need to replicate a reduced organizational assignment, however. For example, if we use generic object replication and replicate the organizational objects together with their associations from Employee Central. In this case, we can prevent creation of some or all of the relations of the employee’s position to other objects in the ERP system.

Note:We cannot prevent the employee-position relation from being created. If we switch off creation of all relations of the employee’s position to other objects, the relation of the employee to the employee’s position is still created in ERP.

Prevent creation of relations of the employee’s position to other objects by setting the value of these switches to X:

  • SFSFI OANSO- Don’t Create Position to Org. Unit Relation

Using this switch we can prevent the relation of an employee’s position to an organizational unit from being created in the Enterprise Resource Planning (ERP) system when replicating employee organizational assignments from SAP SuccessFactors Employee Central.

If we want to have the relation of the employee’s position (object type S) to the organizational unit (object type O) created by default, leave the switch value blank.

If we don’t want to have this relation created, set the switch value to X. Make sure to do so if we use generic object replication to replicate the position together with its association to the department, division, or business unit from Employee Central. Departments, divisions, and business units from Employee Central all correspond to organizational units in ERP. That’s why in this case we should prevent the relation of the employee’s Position to the organizational unit from being created by organizational assignment replication in the ERP system.

  • SFSFI OANSC -Don’t Create Position to Job Relation

Using this switch we can prevent the relation of an employee’s position to a job from being created in the Enterprise Resource Planning (ERP) system when replicating employee organizational assignments from SAPSuccessFactors Employee Central.

If we want to have the relation of the employee’s position (object type S) to the job (object type C) created by default, leave the switch value blank.

If we don’t want to have this relation created, set the switch value to X. Make sure to do so if we use generic object replication to replicate the position together with its association to the job classification from Employee Central. In this case, we should prevent the relation of the employee’s position to the job from being created by organizational assignment replication in the ERP system.

  • SFSFI OANSS -Don’t Create Position to Manager Position Relation

Using this switch we can prevent the relation of an employee’s position to the position of the employee’s manager from being created in the Enterprise Resource Planning (ERP) system when replicating employee      organizational assignments from SAP SuccessFactors Employee Central.

If we want to have the relation of the employee’s position (object type S) to the manager’s position (object type S) created by default, leave the switch value blank.

If we don’t want to have this relation created, set the switch value to X. Make sure to do so if we use generic object replication to replicate the position together with its association to the manager’s position from Employee Central. In this case, we should prevent the relation of the employee’s position to the manager’s position from being created by organizational assignment replication in the ERP system.

  • SFSFI OANSK -Don’t Create Position to Cost Center Relation

Using this switch we can prevent the relation of an employee’s position to a cost center from being created in the Enterprise Resource Planning (ERP) system when replicating employee organizational assignments from    SAP SuccessFactors Employee Central.

If we want to have the relation of the employee’s position (object type S) to the cost center (object type K) created by default, leave the switch value blank.

If we don’t want to have this relation created, set the switch value to X. Make sure to do so if we use generic object replication to replicate the position together with its association to the cost center from Employee Central. In this case, we should prevent the relation of the employee’s position to the cost center from being created by organizational assignment replication in the ERP system.

1 Comment
You must be Logged on to comment or reply to a post.