Objective
Grant the necessary permissions in SAP S/4HANA to the various users required to replicate and process data.
Refer to the following SAP help documentation for the required permissions and available template roles:https://help.sap.com/docs/SAP_SUCCESSFACTORS_EC_S4_HCM_INTEGRATION/ff6b495d894a4685accf7e4bfa75da1b/258eefb69ec042fda65e7babb1354a44.html
Enable the SAP S∕4HANA inbound Web Services used by data replication from Employee Central.
By activating the inbound Web services, you enable the SAP S∕4HANA system to request data from Employee Central, using the integration flows in the middleware. Refer to the following SAP help documentation for a complete list of the relevant inbound Web Services: https://help.sap.com/docs/SAP_SUCCESSFACTORS_EC_S4_HCM_INTEGRATION/ff6b495d894a4685accf7e4bfa75da1b/5efa81ead37b438aba7cacd04e3b5c72.html
By activating the outbound Web services, you enable the SAP S∕4HANA system to query data from and send confirmations to Employee Central, using the integration flows in the middleware. Refer to the following SAP help documentation for a complete list of the relevant outbound Web services: https://help.sap.com/docs/SAP_SUCCESSFACTORS_EC_S4_HCM_INTEGRATION/ff6b495d894a4685accf7e4bfa75da1b/e15e547f021447b894b437a520280b90.html
Refer to the following task for the steps required to enable and test an outbound Web service.
Determine that the new infotype framework is to be used in PA/PD integration for organizational data that was replicated from Employee Central, to improve the performance and allow for better message handling in the replication processes.
If you've activated the integration between Organizational Management and Personnel Administration (PA/PD integration) in your SAP S∕4HANA system, the organizational data is synchronized between the infotypes Relationships (1001) and Organizational Assignment (0001). Using the new infotype framework for this synchronization improves performance and enables better message handling in the replication processes. Therefore, the usage of the new infotype framework is a required prerequisite for the replication of organizational objects and organizational employee assignments from Employee Central.
Note
The new infotype framework doesn't support dynamic actions. Since the Business Integration Builder (BIB) uses the new infotype framework, you can't use dynamic actions in BIB-based data replication from Employee Central.
| Group | Sem.Abbr. | Value Abbr. | Description |
|---|---|---|---|
| PLOGI | NITF | X | For example: Update Infotype 0001 Using New Infotype Framework |
Set a T77S0 switch to enable integration between Organizational Management and Personnel Administration (PA/PD integration) in your SAP S∕4HANA system.
You can enable PA/PD integration for all employees. You can also restrict PA/PD integration to subsets of employees using the Control: Integration of Personnel Planning and Master Data Management (PLOGI) feature.
| Group | Sem.Abbr. | Value Abbr. | Description |
|---|---|---|---|
| PLOGI | ORGA | X | Enter a user-defined description, such as: Integration Switch: Organizational Assignment |
You can use integration between Organizational Management (OM) and Personnel Administration (PA), also called PA/PD integration, in your SAP S∕4HANA system to synchronize organizational data between Organizational Management and Personnel Administration.
PA/PD integration synchronizes organizational data, such as position, job, organizational unit, or cost center, between the Relationships (1001) infotype in Organizational Management and the Organizational Assignment (0001) infotype in Personnel Administration.
The Relationships infotype stores the relationships between the employee and the position (P–S) and all other position relationships, such as position to organizational unit (S–O), position to job (S–C), or position to cost center (S–K), for Organizational Management.
The Organizational Assignment infotype stores the assigned position, job, organizational unit, and cost center of the employee for Personnel Administration.
The Relationships infotype is updated either by the replication of employee data (which includes employee organizational assignments) or by the replication of organizational objects from Employee Central. Replication of organizational assignments as part of employee data replication always creates the relationship between the employee and the position. If you configure your SAP S∕4HANA system to exclude position relations from employee data replication, you can replicate the organizational objects together with their associations from Employee Central. If you make this setting, the organizational object replication creates the other position relationships. Otherwise, the replication of organizational assignments creates these relationships.
The Organizational Assignment infotype is updated either by PA/PD integration or–if PA/PD integration isn't enabled–by the replication of employee master data from Employee Central. See the SAP help documentation for more details.
Prepare for integration between Employee Central and SAP S∕4HANA by deciding on the date when the data replication is to start.
The full transmission start date (FTSD) is the date from which the data transfer from Employee Central to the SAP S∕4HANA system begins. It is used to determine from which start date on data records are provided. Only records that are valid on or after the FTSD are extracted from Employee Central. Processing in SAP S∕4HANA updates the records of all corresponding infotypes only if their validity begins at or after the FTSD.
The choice of the specific FTSD has consequences for existing data in SAP S∕4HANA. During the initial full load from Employee Central to SAP S∕4HANA, existing records in SAP S∕4HANA are cut at the FTSD if they have changes after this date. This can trigger consecutive actions on the SAP S∕4HANA side. Records that were unchanged after the FTSD aren't split by the initial load.
Deciding on the full transmission start date (FTSD) is an important step. We recommend that you work it out in an early project phase.
Note
The SAP S∕4HANA system always uses the general FTSD when querying the data from Employee Central. A country/region-specific and an assignment-specific FTSD can be defined for the same personnel number, in addition to the general FTSD that's stored for the template group. If so, the latest of the three dates is used for processing the data in SAP S∕4HANA.
If you change the full transmission start date after you've already replicated the data, the following extra steps are required:
If you move the date into the past, ensure that you initiate a full load of the data from Employee Central. To do so, run the programs Create and Execute Employee Master Data and Org. Assignment Query (ECPAO_EE_ORG_REPL_QUERY) and Create and Execute Organizational Object Replication Query (RH_SFIOM_ORG_OBJ_REPL_QUERY) with the option Initiate Full Load selected.
If you move the date into the future, no full load is required. However, you must ensure that all changes made before the new FTSD have been replicated successfully.
You can create relationships of employee positions to other objects (such as departments or job classifications) and to other positions (such as matrix manager positions) from different sources in Employee Central using different replication approaches.
You can configure position relationships in SAP S∕4HANA to be created by the replication of organizational assignments and by the replication of organizational objects from Employee Central. Both options have their pros and cons. However, you must prevent the same position relationship from being created by both replications. That is, the settings you make for organizational assignment and for organizational object replication can complement each other, but must not duplicate each other.
Position relationships in SAP S∕4HANA can originate either from Job Information or from Position Management in Employee Central.
Using organizational assignment replication, you can create position relationships based on the employee's Job Information in Employee Central.
If you want to use our sample content for organizational object replication, the appropriate sample content for this option is Organizational Data EC to ERP: Job Info Relationships (OM_WS_1).
Using organizational object replication, you can create position relationships based on Position Management in Employee Central.
The appropriate sample content for this option is Organizational Data EC to ERP: Position Mgmt Relationships (OM_WS_3).
Note
There's also a "mixed" approach, which we don't recommend, however. "Mixed" means: If a position is staffed in Employee Central), the position relationships are created based on Employee Central Job Information using the organizational assignment replication process. If a position is vacant, you replicate position relationships from Employee Central Position Management using the organizational object replication process. Don't use this "mixed" scenario if you've enabled replication of shared positions from Employee Central. It doesn't work for shared positions.
The appropriate sample content for this "mixed" option is Organizational Data EC to ERP: Job Info Relationships and Vacancies from Position Mgmt (OM_WS_2).
Job relationships of positions in SAP S∕4HANA (such as matrix manager relationships) can originate either from Job Relationships or from composite child objects in Employee Central.
Using organizational assignment replication, you can create matrix relationships of positions based on the employee's Job Relationships in Employee Central.
Using organizational object replication, you can create matrix relationships of positions based on the association of parent objects and composite child objects in Employee Central.
Here are some pros and cons of the options.
| Replication Process | Advantages | Disadvantages | Further Considerations |
|---|---|---|---|
| Organizational assignments | You don't need to synchronize Job Information to Position Management in Employee Central because all employee and organizational data is replicated from Job Information. Configuring the organizational hierarchy and filling extra fields is easier if you use configurable organizational assignment. | Configuration is less flexible because you can't use secondary (conditional) mapping and generic value conversion when configuring transformation template groups. | Relationships are delimited in the Relationships (1001) infotype when an employee leaves the assigned position or is terminated. This means that SAP S∕4HANA doesn't consider the relationships of a position if the position doesn't have an incumbent in Employee Central. |
| Organizational objects | Configuration is more flexible because you can use secondary (conditional) mapping and generic value conversion when configuring transformation template groups. | You must synchronize Job Information to Position Management in Employee Central. For more information, refer to Defining "Job Information to Position" Synchronization. Configuring the organizational hierarchy and filling extra fields is more complex. | Relationships aren't delimited in the Relationships (1001) infotype when an employee leaves the assigned position or is terminated. This means that SAP S∕4HANA retains the relationships of a position even if the position doesn't have an incumbent in Employee Central. Disable creation of the corresponding position relationship with organizational assignment replication if you create the relationship based on organizational object replication. |