User Guide | PUBLIC

Document Version: 2H 2022 – 2023-06-16

Managing, Monitoring, and Troubleshooting

Organizational Data Replication from Employee
Central to SAP S/4HANA On Premise
© 2023 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN  

Content

1 Introduction to Managing, Monitoring, and Troubleshooting Organizational Data Replication

from Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1 Prerequisites for Managing, Monitoring, and Troubleshooting Organizational Data Integration. . . . . . . . . . 5
1.2 Your Integration Team. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3 Target Group of This Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2 Management of Organizational Data Replication from Employee Central. . . . . . . . . . . . . . . . . . . . . 7

2.1 Scheduling of Replication Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
How Often Should the Processes Run?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.2 Scheduling of Periodic Tasks in the SAP S∕4HANA System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Scheduling the Organizational Object Query as a Regular Background Job. . . . . . . . . . . . . . . . . . . . . 9
Scheduling the Employee Master Data and Organizational Assignment Query as a Regular
Background Job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Scheduling the Database Update Programs as Regular Background Jobs. . . . . . . . . . . . . . . . . . . . . .11
2.3 Required Manual Periodic Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3 Monitoring of Organizational Data Replication from Employee Central. . . . . . . . . . . . . . . . . . . . . . 15

3.1 Monitoring Tools in the SAP S∕4HANA System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Analyzing SOAP Messages with Web Service Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Analyzing the Application Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Replication Request Monitor for Organizational Data Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Replication Request Viewers for Organizational Data Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.2 Monitoring Tools in Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Replication Request Monitor for Organizational Data Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Employee Central Data Replication Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Analyzing API Calls with the SFAPI Audit Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Analyzing API Calls with the OData API Audit Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.3 Monitoring Tools in the Middleware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Monitoring in SAP Cloud Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

4 Software Change Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

4.1 Support Packages and Patch Implementation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

5 Troubleshooting of Organizational Data Replication from Employee Central. . . . . . . . . . . . . . . . . 32

5.1 Checking Organizational Assignments Replicated to SAP S∕4HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . .32
5.2 Technical Configuration of the Web Service Runtime Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
5.3 Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Known Issue: You've Created or Changed an Employee's Organizational Assignment in Employee
Central, But This Change Is Not Reflected in SAP S∕4HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee
Central to SAP S/4HANA On Premise
2 PUBLIC Content
 Known Issue: You've Created or Changed an Organizational Object in Employee Central, But This
Change Is Not Reflected in SAP S∕4HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Known Issue: Manager Not Yet Replicated From Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . 37
Known Issue: Organizational Assignment Replication from Employee Central Creates New Position
and New Position Assignment Although a Position Assignment Already Exists in SAP S∕4HANA
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Known Issue: After You've Changed the External Code of an Organizational Object in Employee
Central, Organizational Assignments in SAP S∕4HANA Are No Longer Correct. . . . . . . . . . . . . . . . . .39
Known Issue: After Data Replication from Employee Central to SAP S∕4HANA Error Messages
Related to Positions are Shown in the Application Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Known Issue: You Have Changed the Job Classification Title or Description in Employee Central,
but Your Changes Aren't Replicated to SAP S∕4HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Known Issue: Organizational Structure Items Can't Be Replicated Because cust_toDivision and
cust_toBusinessUnit Associations Are Missing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Known Issue: "Invalid Property Name" Error Message is Shown for FOBusinessUnit/
nameTranslationNav and FODivision/nameTranslationNav. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Known Issue: Replication Request Monitor Shows Internal Server Error. . . . . . . . . . . . . . . . . . . . . . 46
Known Issue: Mandatory Field HRP1000-STEXT Was Not Mapped. . . . . . . . . . . . . . . . . . . . . . . . . . 49
Known Issue: Deletion Isn't Replicated from Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
Known Issue: Cost Center Assignments Are Deleted When You Use a Default Cost Center in SAP
S∕4HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Known Issue: Organizational Assignment Change Extends Too Far Into the Past. . . . . . . . . . . . . . . . .52
Known Issue: Staging Area Tables Contain a Large Amount of Data. . . . . . . . . . . . . . . . . . . . . . . . . 53
Known Issue: Employee is Inactive, Replicate Active Employee from Employee Central. . . . . . . . . . . . 54

6 Reporting Incidents for Organizational Data Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee

Central to SAP S/4HANA On Premise
Content PUBLIC 3
Change History

Learn about changes to the documentation for Managing, Monitoring, and Troubleshooting Organizational Data
Replication from Employee Central to SAP S∕4HANA in recent releases.

2H 2021 – Present

Type of Change Description More Info

None We did not update this document.

1H 2021

Type of Change Description More Info

Changed The SAP Cloud Platform Integration

brand has been retired. We've updated
this guide with the new SAP Cloud
Integration brand accordingly.

Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee

Central to SAP S/4HANA On Premise
4 PUBLIC Change History
1 Introduction to Managing, Monitoring,
and Troubleshooting Organizational Data
Replication from Employee Central

Find out how to keep organizational data replication from SAP SuccessFactors Employee Central to SAP S∕4HANA
up and running.

In particular, take a look at:

• Which tasks you should schedule periodically and how you can do this
• Which tools are available for monitoring the integration
• Which isues are known and how you can troubleshooting them

Prerequisites for Managing, Monitoring, and Troubleshooting Organizational Data Integration [page 5]
What needs to be in place before you can carry out the tasks described in this document.

Your Integration Team [page 6]

The implementation and integration process of SAP SuccessFactors Employee Central with SAP S∕4HANA
is a collaborative effort that leverages the skills of various experts.

Target Group of This Document [page 6]

Take a look at the target groups this document is intended for.

1.1 Prerequisites for Managing, Monitoring, and

Troubleshooting Organizational Data Integration

What needs to be in place before you can carry out the tasks described in this document.

The organizational data integration we're referring to in this document supports the Core Hybrid HXM deployment
option. Core Hybrid HXM means that Employee Central is used as the system of record holding the employee data
and reporting lines of all employees. But existing processes such as Payroll, Time Management, or custom HR
processes still run in an SAP S∕4HANA system landscape. To facilitate the Core Hybrid HXM deployment option,
you set up a regular replication of organizational data from Employee Central to SAP S∕4HANA. This replication
must be up and running. For more information, see the following implementation guides:

• Replicating Employee Master Data and Organizational Assignments from Employee Central to SAP S/4HANA
On Premise
• Replicating Organizational Objects from Employee Central to SAP S∕4HANA

Find the most current version of these guides in SAP Help Portal at http://help.sap.com/hr_ecintegration.

Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee

Central to SAP S/4HANA On Premise
Introduction to Managing, Monitoring, and Troubleshooting Organizational Data
Replication from Employee Central PUBLIC 5
1.2 Your Integration Team

The implementation and integration process of SAP SuccessFactors Employee Central with SAP S∕4HANA is a
collaborative effort that leverages the skills of various experts.

You need to pull together a team of experts for your implementation project when integrating SAP SuccessFactors
Employee Central with SAP S∕4HANA.

The following experts are typically involved in the process:

Expert What the Expert Does

SAP SuccessFactors consultant • Is the main point of contact for the entire implementation
and integration process.
• Ensures that all required system settings for Employee
Central are done.
• Works closely with the SAP S∕4HANA team, to ensure
successful data replication.

Middleware consultant Provides support on setting up the middleware.

SAP S∕4HANA consultant • Is the main point of contact for the configuration of SAP
S∕4HANA according to the needs of the customer.
• Works closely with the SAP SuccessFactors consultant to
ensure successful data replication.

1.3 Target Group of This Document

Take a look at the target groups this document is intended for.

The following groups of people will benefit from reading this document:

• Implementation partners, consultants, and Product Support, for fast support of customers and prospective
customers
• Cloud operations
• SAP-certified administrators at customer site

Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee

Central to SAP S/4HANA On Premise
Introduction to Managing, Monitoring, and Troubleshooting Organizational Data
6 PUBLIC Replication from Employee Central
2 Management of Organizational Data
Replication from Employee Central

Here's an overview of periodic tasks related to organizational data replication from Employee Central to SAP
S∕4HANA.

Scheduling of Replication Processes [page 7]

Depending on the version of organizational data integration your are using, the replication processes are
scheduled either in the middleware or in the SAP S∕4HANA system.

Scheduling of Periodic Tasks in the SAP S∕4HANA System [page 8]

You schedule various tasks to be carried out periodically in SAP S∕4HANA.

Required Manual Periodic Tasks [page 13]

It's good practice to regularly check in the SAP S∕4HANA system for replication requests that have the
status Open or Pending.

2.1 Scheduling of Replication Processes

Depending on the version of organizational data integration your are using, the replication processes are scheduled
either in the middleware or in the SAP S∕4HANA system.

Versions of Organizational Data Replication from Employee Central

And requires integration

processes to be scheduled Find more information in this
This integration version... Uses this middleware... in... integration guide...

Standard integration version – SAP Cloud Integration Both integration processes, Replicating Employee Master
for new integration projects organizational assignment Data and Organizational As­
replication and organizational signments from Employee
object replication, are trig­ Central to SAP S∕4HANA
gered by the SAP S∕4HANA
Replicating Organizational Ob­
system
jects from Employee Central to
SAP S∕4HANA

Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee

Central to SAP S/4HANA On Premise
Management of Organizational Data Replication from Employee Central PUBLIC 7
 And requires integration
processes to be scheduled Find more information in this
This integration version... Uses this middleware... in... integration guide...

Previous version – only for in­ SAP Cloud Integration The integration process for or­ Replicating Organizational
itial implementation that was ganizational assignment repli­ Data from Employee Central to
started before Q2 2017 cation is triggered by the mid­ SAP S∕4HANA (For Implemen­
dleware tation Started Before Q2 2017)

The integration process for

organizational object replica­
tion is triggered by the SAP
S∕4HANA system

2.1.1  How Often Should the Processes Run?

When scheduling the processes for replicating organizational data, take into account these considerations.

• How often do you change organizational objects and organizational assignments in Employee Central?
• How much do you depend on the SAP S∕4HANA system being up to date?
• Try to keep the organizational objects and the corresponding assignments in sync. It doesn't make sense to
replicate department assignments every hour, but the departments themselves once a week.
• Each time a process runs, an entry is written to the log. So if the processes run very often, the log becomes
more difficult to oversee.

2.2 Scheduling of Periodic Tasks in the SAP S∕4HANA System

You schedule various tasks to be carried out periodically in SAP S∕4HANA.

• If you’re using an integration version that is triggered by the SAP S∕4HANA system, the program the queries
information from Employee Central needs to be scheduled regularly.
• The programs that post the replicated data from the staging area to the database need to run regularly,
registered on an event.
• We recommend that you schedule the same programs also periodically so that they can pick up all replication
requests that couldn't be processed yet.

Scheduling the Organizational Object Query as a Regular Background Job [page 9]

Trigger queries regularly by scheduling the query program as a background job, to request organizational
objects from Employee Central on an ongoing basis.

Scheduling the Employee Master Data and Organizational Assignment Query as a Regular Background Job
[page 10]
Trigger queries to request employee master data and organizational assignments from Employee Central
on a regular basis.

Scheduling the Database Update Programs as Regular Background Jobs [page 11]
Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee
Central to SAP S/4HANA On Premise
8 PUBLIC Management of Organizational Data Replication from Employee Central
 Whenever replication requests from Employee Central are written to the staging area tables in the SAP
S∕4HANA system, an event is triggered. Schedule the programs that process the replication requests in the
staging area and post the results to the database as separate background jobs that are registered on the
corresponding events.

2.2.1  Scheduling the Organizational Object Query as a Regular

Background Job

Trigger queries regularly by scheduling the query program as a background job, to request organizational objects
from Employee Central on an ongoing basis.

Prerequisites

You’ve defined a suitable variant or several variants for the Create and Execute Organizational Object Replication
Query (RH_SFIOM_ORG_OBJ_REPL_QUERY) program.

Context

The RH_SFIOM_ORG_OBJ_REPL_QUERY program creates and sends a query to replicate organizational data from
SAP SuccessFactors Employee Central to the SAP S∕4HANA system. Schedule this program to run regularly in the
background. You can define and schedule background jobs in two ways:

• Directly from the Define Background Job (SM36) transaction. This option is best for users already familiar with
background job scheduling.
• Using the Job Scheduling Wizard. This option is best for users unfamiliar with SAP background job scheduling.
To use the Job Scheduling Wizard, choose Job Wizard in the Define Background Job transaction.

Procedure

1. Go to the Define Background Job (SM36) transaction.

2. Decide on a name for the job you’re defining and enter it in the Job Name field.
3. Select the job’s priority in the Job Class field:
• High priority: class A
• Medium priority: class B
• Low priority: class C
4. In the Target Server field, indicate whether to use system load balancing. For the system to use system load
balancing to automatically select the most efficient application server to use at the moment, leave this field
empty. To use a particular application server to run the job, enter a specific target server.
Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee
Central to SAP S/4HANA On Premise
Management of Organizational Data Replication from Employee Central PUBLIC 9
5. If spool requests generated by this job are to be sent to someone as email, specify the email address. To do so,
choose Spool List Recipient.

6. Define when the job is to start. To do so, choose Start Condition Date/Time . Enter a suitable date and
time and select the Periodic Job checkbox.

7. Define the job’s steps by choosing Step ABAP Program . Specify the variant to be used.
8. Save the fully defined job to submit it to the background processing system.
9. Release the job so that it can run.
10. Repeat these steps for each program variant.

Next Steps

When you need to modify, reschedule, or otherwise manipulate a job after you've scheduled it the first time, you'll
manage jobs from the Simple Job Selection (SM37) or Extended Job Selection (SM37C) transactions.

For more information about background processing in SAP systems, go to http://help.sap.com/netweaver and
search for background processing.

2.2.2  Scheduling the Employee Master Data and Organizational

Assignment Query as a Regular Background Job

Trigger queries to request employee master data and organizational assignments from Employee Central on a
regular basis.

Prerequisites

You have defined a suitable variant or several variants for the Create and Execute Employee Master Data and Org.
Assignment Query (ECPAO_EE_ORG_REPL_QUERY) program.

Context

You can define and schedule background jobs in two ways:

• Directly from the Define Background Job (SM36) transaction. This is best for users already familiar with
background job scheduling.
• Using the Job Scheduling Wizard. This is best for users unfamiliar with SAP background job scheduling. To use
the Job Scheduling Wizard, choose Job Wizard in the Define Background Job transaction.
Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee
Central to SAP S/4HANA On Premise
10 PUBLIC Management of Organizational Data Replication from Employee Central
Carry out the following steps for each variant:

Procedure

1. Go to the Define Background Job (SM36) transaction.

2. Decide on a name for the job you are defining and enter it in the Job Name field.
3. Select the job’s priority in the Job Class field:
• High priority: class A
• Medium priority: class B
• Low priority: class C
4. In the Target Server field, indicate whether to use system load balancing. For the system to use system load
balancing to automatically select the most efficient application server to use at the moment, leave this field
empty. To use a particular application server to run the job, enter a specific target server.
5. If spool requests generated by this job are to be sent to someone as e-mail, specify the e-mail address. To do
so, choose Spool List Recipient.

6. Define when the job is to start. To do so, choose Start Condition Date/Time . Enter a suitable date and
time and select the Periodic Job checkbox.

7. Define the job’s steps by choosing Step ABAP Program . Specify the variant to be used (see above).
8. Save the fully defined job to submit it to the background processing system.
9. Release the job so that it can run.

Next Steps

When you need to modify, reschedule, or otherwise manipulate a job after you've scheduled it the first time, you'll
manage jobs from the Simple Job Selection (SM37) or Extended Job Selection (SM37C) transactions.

2.2.3  Scheduling the Database Update Programs as Regular

Background Jobs

Whenever replication requests from Employee Central are written to the staging area tables in the SAP S∕4HANA
system, an event is triggered. Schedule the programs that process the replication requests in the staging area and
post the results to the database as separate background jobs that are registered on the corresponding events.

Prerequisites

You have defined a suitable variant for each program. These are the programs and the corresponding events:
Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee
Central to SAP S/4HANA On Premise
Management of Organizational Data Replication from Employee Central PUBLIC 11
Processing Programs and Events
Program Event

Replicate Organizational Objects from EC to ERP Org. Mgmt SAP_SFIOM_ORG_STRUC_RPRQ_CREATED

(RH_SFIOM_PROC_ORG_STRUC_RPRQ)

Replicate Employee Org. Assignments from EC to ERP Org. SAP_SFIOM_EE_ORGAS_RPPQ_CREATED

Mgmt (RH_SFIOM_PROC_EE_ORG_ASS_RPRQ)

If you use generic object replication with generic processing, we recommend that you define a separate
variant for each object type for the Replicate Organizational Objects from EC to ERP Org. Mgmt
(RH_SFIOM_PROC_ORG_STRUC_RPRQ program. One for business units, one for departments, and so on. To do
this, enter the required object type, such as 03 (Business Unit) in the EC Org. Object Type field (under Other
Organizational Object). Don't make any other settings on the program selection screen. Then save your selection as
a variant. This way you can schedule multiple jobs, which can run simultaneously, to post the different object types
independently of each other to the database.

Context

You can define and schedule background jobs in two ways:

• Directly from the Define Background Job (SM36) transaction. This is best for users already familiar with
background job scheduling.
• Using the Job Scheduling Wizard. This is best for users unfamiliar with SAP background job scheduling. To use
the Job Scheduling Wizard, choose Job Wizard in the Define Background Job transaction.

Carry out the steps described below for each program:

Procedure

1. Go to the Define Background Job (SM36) transaction.

2. Decide on a name for the job you are defining and enter it in the Job Name field.
3. Select the job’s priority in the Job Class field:
• High priority: class A
• Medium priority: class B
• Low priority: class C
4. In the Target Server field, indicate whether to use system load balancing. For the system to use system load
balancing to automatically select the most efficient application server to use at the moment, leave this field
empty. To use a particular application server to run the job, enter a specific target server.
5. If spool requests generated by this job are to be sent to someone as email, specify the email address. To do so,
choose Spool List Recipient.

6. Define when the job is to start. To do so, choose Start Condition After Event and enter the event name:
• For organizational objects: SAP_SFIOM_ORG_STRUC_RPRQ_CREATED
• For organizational assignments: SAP_SFIOM_EE_ORGAS_RPPQ_CREATED
Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee
Central to SAP S/4HANA On Premise
12 PUBLIC Management of Organizational Data Replication from Employee Central
 If you want the job to be executed only when the event was raised in a specific client of your SAP S∕4HANA
system, enter the client ID (such as 200) in the Parameter field. If you want the job to be executed in all clients,
leave the Parameter field empty.

Select Periodic Job for the job to repeat.

7. Define the job’s steps by choosing Step ABAP Program . Specify the corresponding program and variant
to be used (see above).
8. Save the fully defined job to submit it to the background processing system.
9. Release the job so that it can run.

Next Steps

When you need to modify, reschedule, or otherwise manipulate a job after you've scheduled it the first time, you'll
manage jobs from the Simple Job Selection (SM37) or Extended Job Selection (SM37C) transactions.

 Tip

In addition to the background jobs that are registered on the events as described above, we recommend
that you schedule a periodical background job for each of the database update programs, which picks up all
replication requests that couldn't be processed yet. During initial load, for example, often two events follow
each other in close succession. If this happens, the processing triggered by the second event might not be
successful if the staging area is still locked by the processing triggered by the first event.

To process open, pending, or failed requests again, schedule a background job that runs at a time when the
system load is low (for example, each night). This way, you don't need to wait until the next event is triggered
that would start the next run of the database update program.

To schedule periodical background jobs, carry out the steps described above. However, in step 6, don't select
an event. Instead, choose Start Condition Date/Time . Enter a suitable date and time and select the
Periodic Job checkbox.

For more information about background processing in SAP systems, go to http://help.sap.com/netweaver and
search for background processing.

2.3 Required Manual Periodic Tasks

It's good practice to regularly check in the SAP S∕4HANA system for replication requests that have the status Open
or Pending.

This is particularly important for the organizational objects replication, since the Employee Central Data Replication
Monitor doesn't show messages regarding this replication. You can use these tools:

• The Replication Request Monitor (Web Dynpro application SFIUI_A_REPL_REQ_MONITOR)

• The Replication Request Viewers (SFIOM_VIEW_REQUESTS for organizational assignments and
SFIOM_VIEW_ORG_REQS for organizational objects)
Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee
Central to SAP S/4HANA On Premise
Management of Organizational Data Replication from Employee Central PUBLIC 13
From all tools, you can trigger the database update programs manually for selected requests to post pending
replications manually.

For more information, see the Monitoring section. If you encounter problems, check the Troubleshooting section for
a solution.

Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee

Central to SAP S/4HANA On Premise
14 PUBLIC Management of Organizational Data Replication from Employee Central
3 Monitoring of Organizational Data
Replication from Employee Central

Find out about the tools that are available for monitoring organizational data replication from Employee Central to
the SAP S∕4HANA system.

The table shows an overview of the monitoring tools.

Monitoring Tools for Organizational Data Integration

And here's how to find this

In this system... Use this tool... To monitor... tool...

SAP S∕4HANA Web Service Utilities Incoming SOAP messages Transaction SRUTIL or
SXMB_MONI

SAP S∕4HANA Application Log Creation of inbound message Transaction SLG1

and storage of replication re­
quests in the staging area

SAP S∕4HANA Replication Request Monitor Replication requests for or­ Web Dynpro application
ganizational objects (when us­ SFIUI_A_REPL_REQ_MONITO
 Note ing generic object replication) R
You can use the Repli­ and for organizational assign­
cation Request Monitor ments
in SAP S∕4HANA as
well as in Employee Cen­
tral. To use it in Em­
ployee Central, add the
Web Dynpro application
to the SAP SuccessFac­
tors user interface us­
ing the Configure Custom
Navigation admin tool.

SAP S∕4HANA Replication Request Viewer for Replication requests for or­ Transaction
Organizational Assignments ganizational assignments in SFIOM_VIEW_REQUESTS
the staging area

SAP S∕4HANA Replication Request Viewer for Replication requests for or­ Transaction
Organizational Objects ganizational objects in the SFIOM_VIEW_ORG_REQS
staging area

Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee

Central to SAP S/4HANA On Premise
Monitoring of Organizational Data Replication from Employee Central PUBLIC 15
 And here's how to find this
In this system... Use this tool... To monitor... tool...

Employee Central Replication Request Monitor Replication requests for or­ Web Dynpro application
ganizational objects (when us­ SFIUI_A_REPL_REQ_MONITO
 Note ing generic object replication) R
You can use the Repli­ and for organizational assign­
cation Request Monitor ments
in SAP S∕4HANA as
well as in Employee Cen­
tral. To use it in Em­
ployee Central, add the
Web Dynpro application
to the SAP SuccessFac­
tors user interface us­
ing the Configure Custom
Navigation admin tool.

Employee Central Data Replication Monitor Employee organizational as­ Admin Alerts tile on the home
signment replication page or in the Admin Center,
Data Replication Monitor for
SAP ERP Integration tool in the
Admin Center

Employee Central SFAPI Audit Log Employee Central SFAPI Audit Log tool in the Ad­
CompoundEmployee API min Center
calls for organizational assign­
ment data

Employee Central OData API Audit Log OData API organizational ob­ OData API Audit Log tool in the
ject data Admin Center

SAP Cloud Integration Web-Based Monitoring Process execution in the mid­ To launch the web-based mon­
dleware itoring application, access the
URL provided by SAP in a web
browser

3.1 Monitoring Tools in the SAP S∕4HANA System

Various monitoring tools are available in SAP S∕4HANA for checking data replication results.

Analyzing SOAP Messages with Web Service Utilities [page 17]

Use Web Service Utilities to monitor incoming SOAP messages in the SAP S∕4HANA system.

Analyzing the Application Log [page 18]

Using the application log you can analyze the incoming messages for organizational data replication from
Employee Central in your SAP S∕4HANA system.

Replication Request Monitor for Organizational Data Replication [page 18]

Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee
Central to SAP S/4HANA On Premise
16 PUBLIC Monitoring of Organizational Data Replication from Employee Central
 Using the Replication Request Monitor, you can access the staging area for organizational data in SAP
S∕4HANA to check statuses, analyze errors, or process requests manually.

Replication Request Viewers for Organizational Data Replication [page 26]

Using the Replication Request Viewers, you can access the staging areas for organizational data in SAP
S∕4HANA to check statuses or process requests manually.

3.1.1  Analyzing SOAP Messages with Web Service Utilities

Use Web Service Utilities to monitor incoming SOAP messages in the SAP S∕4HANA system.

Context

Web Service Utilities (transaction SRTUTIL) in SAP S∕4HANA offers an Error Log and a Message Monitor tool, which
you can use, for example, to analyze errors in incoming SOAP messages or check the content of messages.

 Note

For more information about the tool, see Web Service Logging and Tracing in the SAP NetWeaver
documentation.

Depending on your system configuration, the SRTUTIL transaction might not be available. If it's not, use the
Integration Engine: Monitoring (SXMB_MONI) transaction instead.

Procedure

1. Choose Error Log to see information about all errors happening during the processing in the SOAP runtime.
2. Double-click an error message to see more details.
3. Choose Original XML to display the error message in the XML format.
4. Go back and choose Message Monitor to get an overview of all received messages along with their content.
5. Select the messages you want to see.
• You can, for example, specify the execution time in the Timestamp From and Timestamp To fields on the
Standard Selection tab.
• You can also filter for messages related to a specific interface by entering the interface in the Interface
Name field for the receiver.
• Or you filter for messages with a specific message ID.
6. Double-click a message to see the content that was transferred from Employee Central.
7. Choose Original XML to display the content in the XML format.
Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee
Central to SAP S/4HANA On Premise
Monitoring of Organizational Data Replication from Employee Central PUBLIC 17
3.1.2  Analyzing the Application Log

Using the application log you can analyze the incoming messages for organizational data replication from Employee
Central in your SAP S∕4HANA system.

Context

An application log is written when the incoming messages are processed and stored as replication requests in
the staging area, as well as when the entries in the staging area are being processed. Here's how to check these
messages.

 Note

You can also display the application log for selected replication requests from the replication request viewers.

Procedure

1. Go to the Analyze Application Log (SLG1) transaction.

2. Enter the PAOC_SFI_OM object and one of the following subobjects:
• REPL_REQ_PROCESSING for the log created by the replication to the SAP S∕4HANA system
• REPL_REQ_PROXY for the log created when processing the inbound message in SAP S∕4HANA
3. Make additional selections as suits your requirements and choose Execute.

3.1.3  Replication Request Monitor for Organizational Data

Replication

Using the Replication Request Monitor, you can access the staging area for organizational data in SAP S∕4HANA to
check statuses, analyze errors, or process requests manually.

The Replication Request Monitor (SFIUI_A_REPL_REQ_MONITOR) is a Web Dynpro application that allows you to
check replication requests for organizational objects and organizational assignments in all details, analyze error
message issued by the replication from Employee Central, and process replication requests manually.

The SFIUI_A_REPL_REQ_MONITOR Web Dynpro application is assigned to the role menu of the
SAP_HR_SFIOM_PROCESSING role in SAP S∕4HANA. You can also add it to the SAP SuccessFactors user
interface using the Configure Custom Navigation admin tool in Employee Central. This tool allows you to add
hyperlinks to various locations in the SAP SuccessFactors UI, enabling users to navigate from that location
to the specified URL. The URL you need to add is: <protocol><host name>/sap/bc/webdynpro/sap/
sfiui_a_repl_req_monitor.

For more information about the tool, refer to Managing Custom Navigation Links.

Selecting Replication Requests for Monitoring [page 19]

Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee
Central to SAP S/4HANA On Premise
18 PUBLIC Monitoring of Organizational Data Replication from Employee Central
 Select the replication requests that you want to check in the Replication Request Monitor by time frame, ID,
or status.

Sorting and Filtering to Show Replication Requests You're Interested In [page 20]
Adjust the results list in the Replication Request Monitor so that only the requests you want to monitor right
now are shown.

Creating a Personalized View for the Results List [page 21]

Adjust the results list in the Replication Request Monitor according to your personal preferences, for
example, to remove columns you're not interested in.

Viewing Time Slices, Job Information, and Messages for a Replication Request [page 22]
Review time slices contained in a request for organizational object replication or Job Information
assignments contained in a request for organizational assignment replication, to find out what data was
replicated. And check whether any messages occurred.

Viewing Mapped Object IDs, Message IDs, and Other Technical Details for a Replication Request [page 23]
Review details about a replication request in the Replication Request Monitor, such as what Employee
Central and SAP S∕4HANA IDs are mapped, what full transmission start date and transformation template
are used, and so on.

Exporting the Results List [page 24]

Export the results list from the Replication Request Monitor to work on it offline or share it with someone
else.

Processing Replication Requests Manually to Directly Store Updates in SAP S∕4HANA [page 24]
Post selected requests from the Replication Request Monitor manually on the database if you want to store
the contained updates immediately, without waiting for the next scheduled run of the database update
program.

Example: Checking Why the Parent Division Is Missing for a Department [page 25]
Go through this example to see how you can use the Replication Request Monitor when a replication
request wasn't successful because the associated object is missing.

3.1.3.1 Selecting Replication Requests for Monitoring

Select the replication requests that you want to check in the Replication Request Monitor by time frame, ID, or
status.

Procedure

1. Select a time frame. By default requests are shown for the past week. Available time frames are:

• Past hour
• Past 24 hours
• Past week
• Past 4 weeks
• All
Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee
Central to SAP S/4HANA On Premise
Monitoring of Organizational Data Replication from Employee Central PUBLIC 19
2. Select a status or multiple statuses. By default, failed, open, and pending requests are shown. To select

multiple statuses, choose (Advanced Options). Available statuses are:

• 01 = Open
• 02 = Pending
• 03 = Successful
• 04 = Failed
• 05 = Outdated
• 06 = Redundant
3. Select organizational objects by object type or ID or select organizational assignments by employee ID or
personnel number.
4. Choose Apply.

Results

All replication requests that match your selection criteria are shown in the results list on the Organizational Object
Replication tab or the Organizational Assignment Replication tab.

Next Steps

Next, adjust the results list so that only the requests you want to monitor right now are shown.

3.1.3.2 Sorting and Filtering to Show Replication Requests

You're Interested In

Adjust the results list in the Replication Request Monitor so that only the requests you want to monitor right now
are shown.

Prerequisites

You've selected replication requests so that the results list is shown.

Procedure

1. Select the header of a column to sort the entries in ascending or descending order.
Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee
Central to SAP S/4HANA On Premise
20 PUBLIC Monitoring of Organizational Data Replication from Employee Central
 2. Select the column header again to filter for one of the entries or to define your own filter.

Next Steps

Next, personalize the results list according to your preferences, for example, to remove columns you're not
interested in.

3.1.3.3 Creating a Personalized View for the Results List

Adjust the results list in the Replication Request Monitor according to your personal preferences, for example, to
remove columns you're not interested in.

Prerequisites

You've selected replication requests so that the results list is shown.

Procedure

1. Choose (Open Settings Dialog) to personalize the results list. For example:

• Add or remove columns

• Change the default order of columns
• Sort columns by default
• Filter columns by default
2. Save your settings as a personalized view to reuse them.

Next Steps

Next, check the time slices, job information, and messages for a replication request.

Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee

Central to SAP S/4HANA On Premise
Monitoring of Organizational Data Replication from Employee Central PUBLIC 21
3.1.3.4 Viewing Time Slices, Job Information, and Messages
for a Replication Request

Review time slices contained in a request for organizational object replication or Job Information assignments
contained in a request for organizational assignment replication, to find out what data was replicated. And check
whether any messages occurred.

Prerequisites

• You've selected replication requests so that the results list is shown.

• You've sorted, filtered, and personalized the results list if desired so that only the requests you want to monitor
right now are shown.

Procedure

1. Choose Show Details for a replication request in the results list to view the data records (time slices) replicated
for the selected object or the Job Information assignments for the selected employee, and also the message
log.
If an employee's master data wasn't replicated yet from Employee Central, no employee name is shown. In
this case, searching for the employee name in the ERP Personnel Number field in the selection criteria doesn't
produce any results either.
2. Choose Show Details for a time slice shown in the Details for <Organizational Object> section to view the
fields and field values replicated from Employee Central to SAP S∕4HANA.

You're shown, for example, the external code, the title (in all languages included in the replication), or the
parent object of an object replicated from Employee Central.
3. Choose Show Details for an assignment shown in the Job Information Assignments section to view the job info
replicated from Employee Central and the corresponding fields in SAP S∕4HANA.

You're shown, for example, the supervisor, company, business unit, position, or job classification assigned
in Employee Central and the corresponding manager, company code, organizational unit, position, or job
assigned in SAP S∕4HANA.
4. Choose Show Details for an assignment shown in the Additional Assignments section to view Job Relationship
assignments, such as a matrix manager relation.

Additional Assignments is only displayed for employees that have additional Job Relationship assignments and
only if you've enabled replication of associated employee information in the middleware (for organizational
object replication) or the SAP S∕4HANA system (for employee master data and organizational assignment
replication).
5. If an error occurred, the related messages are shown.

The Message Log section shows the messages stored for the selected replication request in the Analyze
Application Log (SLG1) transaction of the SAP S∕4HANA system.
Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee
Central to SAP S/4HANA On Premise
22 PUBLIC Monitoring of Organizational Data Replication from Employee Central
Next Steps

Next, view mapped object IDs, message IDs, and other technical details for a replication request.

3.1.3.5 Viewing Mapped Object IDs, Message IDs, and Other

Technical Details for a Replication Request

Review details about a replication request in the Replication Request Monitor, such as what Employee Central and
SAP S∕4HANA IDs are mapped, what full transmission start date and transformation template are used, and so on.

Prerequisites

You've chosen Show Details for a time slice shown in the Details for <Organizational Object> section or for an
assignment shown in the Details for Employee (<Employee ID>) section.

Context

You can view the following detailed information for a replication request:

• The ID of the object replicated from Employee Central and the mapped object ID from the SAP S∕4HANA
system
• The ID of the employee replicated from Employee Central and the mapped personnel number from the SAP
S∕4HANA system
• The ID of the web service message used to replicate this specific object or employee
• The status, creation date, and last change date of the replication request
• The unique ID of the replication request
• The full transmission start date (FTSD) used by the replication
• The transformation template group used in the replication
• Whether the generic, configuration-based or the object-specific processing of organizational objects was used
in SAP S∕4HANA
• Whether Enforce Update was set in employee master data replication
• Whether Is No-Show was set for a time slice

Procedure

Choose Show Technical Details at the bottom of the screen.

Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee
Central to SAP S/4HANA On Premise
Monitoring of Organizational Data Replication from Employee Central PUBLIC 23
3.1.3.6 Exporting the Results List

Export the results list from the Replication Request Monitor to work on it offline or share it with someone else.

Prerequisites

• You've selected replication requests so that the results list is shown.

• You've sorted, filtered, and personalized the results list if desired so that only the requests you want to monitor
right now are shown.

Procedure

Choose Export Export to Microsoft Excel to download the list.

Results

The export option downloads the plain list, without adding any details or links.

3.1.3.7 Processing Replication Requests Manually to Directly

Store Updates in SAP S∕4HANA

Post selected requests from the Replication Request Monitor manually on the database if you want to store the
contained updates immediately, without waiting for the next scheduled run of the database update program.

Prerequisites

• You've selected replication requests so that the results list is shown.

• You've sorted, filtered, and personalized the results list if desired so that only the requests you want to monitor
right now are shown.

Procedure

Select a request or multiple requests and choose Process Requests.

Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee
Central to SAP S/4HANA On Premise
24 PUBLIC Monitoring of Organizational Data Replication from Employee Central
Results

The Replication Request Monitor runs the following database update programs directly, without asking for
confirmation:

• Replicate Organizational Objects from EC to ERP Org. Mgmt (RH_SFIOM_PROC_ORG_STRUC_RPRQ) for

organizational object requests
• Replicate Employee Org. Assignments from EC to ERP Org. Mgmt (RH_SFIOM_PROC_EE_ORG_ASS_RPRQ) for
organizational assignment requests

Processed replication requests disappear from the results list in the Replication Request Monitor.

3.1.3.8 Example: Checking Why the Parent Division Is Missing

for a Department

Go through this example to see how you can use the Replication Request Monitor when a replication request wasn't
successful because the associated object is missing.

Procedure

1. Check which replication requests weren't successful since yesterday.

a. Go to the Selection Criteria section.
b. Choose the selection period Last 24 Hours.
c. Choose the statuses Failed and Pending.
d. If needed, restrict the selection to the Employee Central object type you want to monitor, such as
Department.
2. From the result list, show the details for a specific object, such as Department 2, to check which error occurred.

You’re shown this error message: FODepartment DEP_2: Target object DIV_11 for relationship
A002 does not exist
3. Check for the target object mentioned in the error message.
a. Go back to the Selection Criteria section.
b. Choose the selection period All.
c. Restrict the selection to the target object ID, DIV_11.

The Replication Request Monitor doesn't show any result for your selection – apparently division Division 011
(DIV_011) wasn't replicated yet.
4. Go to the Admin Center in SAP SuccessFactors, open the Manage Data admin tool, and check Department 2.

Department 2 has associations to two divisions: Division 011 and Division 012
5. Trigger replication of organizational objects from Employee Central to SAP S∕4HANA again.
6. Go back to the Replication Request Monitor, select the entry for Division 011, and choose Process Requests to
post the result to the database.
Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee
Central to SAP S/4HANA On Premise
Monitoring of Organizational Data Replication from Employee Central PUBLIC 25
7. Select the entry for Department 2 and choose Process Requests.
8. Check the details for Department 2 again – this time, no error is shown.

3.1.4  Replication Request Viewers for Organizational Data

Replication

Using the Replication Request Viewers, you can access the staging areas for organizational data in SAP S∕4HANA
to check statuses or process requests manually.

Organizational Objects

Replication requests for organizational objects are stored in a staging area in the SAP S∕4HANA system. To view the
requests, go to the Display Organizational Object Replication Requests (SFIOM_VIEW_ORG_REQS) transaction.

Replication Request Viewer for Organizational Objects

Organizational Assignments

Replication requests for employee organizational assignments are stored in a staging area in the SAP
S∕4HANA system. To view the requests, go to the Display Employee Org. Assignment Replication Requests
(SFIOM_VIEW_REQUESTS) transaction.
Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee
Central to SAP S/4HANA On Premise
26 PUBLIC Monitoring of Organizational Data Replication from Employee Central
 Replication Request Viewer for Organizational Assignments

Using the Replication Request Viewers

By default, in both transactions replication requests with the status Open, Pending, or Failed are displayed. You can
change the selection by pushing F9 .

You can trigger the database update manually for selected requests by choosing Process Selected Requests.

From both transactions you can go to the Analyze Application Log (SLG1) transaction and check the messages
issued for the selected replication requests.

3.2 Monitoring Tools in Employee Central

Various monitoring tools are available in Employee Central for checking data replication results.

Replication Request Monitor for Organizational Data Replication [page 28]

Using the Replication Request Monitor, you can access the staging area for organizational data in SAP
S∕4HANA to check statuses, analyze errors, or process requests manually.

Employee Central Data Replication Monitor [page 28]

Employee Central provides an admin tool for monitoring data replication to the SAP S∕4HANA system.

Analyzing API Calls with the SFAPI Audit Log [page 28]
Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee
Central to SAP S/4HANA On Premise
Monitoring of Organizational Data Replication from Employee Central PUBLIC 27
 Use the SFAPI Audit Log to monitor API calls to Employee Central.

Analyzing API Calls with the OData API Audit Log [page 29]
Use the OData API Audit Log to monitor OData API calls to Employee Central.

3.2.1  Replication Request Monitor for Organizational Data

Replication

Using the Replication Request Monitor, you can access the staging area for organizational data in SAP S∕4HANA to
check statuses, analyze errors, or process requests manually.

The Replication Request Monitor (SFIUI_A_REPL_REQ_MONITOR) is a Web Dynpro application that allows you to
check replication requests for organizational objects and organizational assignments in all details, analyze error
message issued by the replication from Employee Central, and process replication requests manually.

The SFIUI_A_REPL_REQ_MONITOR Web Dynpro application is assigned to the role menu of the
SAP_HR_SFIOM_PROCESSING role in SAP S∕4HANA. You can also add it to the SAP SuccessFactors user
interface using the Configure Custom Navigation admin tool in Employee Central. This tool allows you to add
hyperlinks to various locations in the SAP SuccessFactors UI, enabling users to navigate from that location
to the specified URL. The URL you need to add is: <protocol><host name>/sap/bc/webdynpro/sap/
sfiui_a_repl_req_monitor.

For more information about the tool, refer to Managing Custom Navigation Links.

3.2.2  Employee Central Data Replication Monitor

Employee Central provides an admin tool for monitoring data replication to the SAP S∕4HANA system.

The integration processes update the status in the Employee Central Data Replication Monitor by sending
notifications and confirmations. Use the Data Replication Monitor to check the replication status, view alerts, and
analyze error messages related to data replication from Employee Central to SAP S∕4HANA. For more information,
refer to the Employee Central Data Replication Monitor administration guide.

3.2.3  Analyzing API Calls with the SFAPI Audit Log

Use the SFAPI Audit Log to monitor API calls to Employee Central.

Context

The Employee Central CompoundEmployee API used by this integration is an employee-specific version of the
SOAP-based SAP SuccessFactors API (SFAPI). It’s provided specifically for extracting employee data (including
organizational assignments) out of Employee Central. You can monitor the SFAPI using the SFAPI Audit Log.
Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee
Central to SAP S/4HANA On Premise
28 PUBLIC Monitoring of Organizational Data Replication from Employee Central
The SFAPI Audit Log is intended to help with support and debugging of API usage. You can use it, for example, to
share information with Product Support to help resolve API-related support issues. The tool allows you to download
data from individual calls, which you could then send to Product Support.

For more information about the SFAPI Audit Log and how to access it, see Integration Tools in the SAP
SuccessFactors HXM Suite SFAPI developer guide. Find the most current version of this guide in SAP Help Portal at
https://help.sap.com/hr_foundation.

Procedure

1. Go to the Admin Center and choose the SFAPI Audit Log tool.

The Audit Log page shows the last 10,000 API calls to this system.
2. Select the button under the SOAP or HTTP columns in the log table to view the payload information for each
call.

3.2.4  Analyzing API Calls with the OData API Audit Log

Use the OData API Audit Log to monitor OData API calls to Employee Central.

Context

You can filter, display, and download the transaction history of OData APIs using the OData API Audit Log tool.
In the context of organizational data replication, OData APIs are used to retrieve data for generic objects from
Employee Central.

For more information about the OData API Audit Log and how to access it, see Enabling API Audit Logs in SAP
SuccessFactors HXM Suite OData API: Developer Guide. Find the most current version of this guide in SAP Help
Portal at https://help.sap.com/hr_foundation.

Procedure

1. Go to the Admin Center and choose the OData API Audit Log tool.

The Audit Log shows the last 10,000 OData calls to this system.
2. Select the button under the HTTP or REST columns in the log table to view the payload information for each
call.

Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee

Central to SAP S/4HANA On Premise
Monitoring of Organizational Data Replication from Employee Central PUBLIC 29
 Example: OData API Audit Log Table
3. Use the Request ID column in the log table to display the request ID for each recorded OData API call.

You can use request IDs as search criteria when needed.

3.3 Monitoring Tools in the Middleware

Take a look at the monitoring tools available for your middleware.

Monitoring in SAP Cloud Integration [page 30]

Use the monitoring features of SAP Cloud Integration to check whether any issues occurred in your
middleware processes.

3.3.1  Monitoring in SAP Cloud Integration

Use the monitoring features of SAP Cloud Integration to check whether any issues occurred in your middleware
processes.

SAP Cloud Integration provides a web-based monitoring UI that allows you to check the status of messages and
integration content artifacts for a tenant cluster. For more information, see Monitoring.

Use the log ID that you find in the monitoring to find the log of a specific process that didn't run successfully and to
filter the log for detailed information.

Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee

Central to SAP S/4HANA On Premise
30 PUBLIC Monitoring of Organizational Data Replication from Employee Central
4 Software Change Management

Ensure software maintenance for your organizational data integration system landscape.

Support Packages and Patch Implementation [page 31]

To be able to use the newest features we provide, always install the latest support package of the
integration add-on for SAP S∕4HANA and SAP SuccessFactors Employee Central (software component
version PA_SE_IN 100).

4.1 Support Packages and Patch Implementation

To be able to use the newest features we provide, always install the latest support package of the integration add-on
for SAP S∕4HANA and SAP SuccessFactors Employee Central (software component version PA_SE_IN 100).

You'll find the required support package in the corresponding integration guides, such as:

• Replicating Employee Master Data and Organizational Assignments from Employee Central to SAP S∕4HANA
• Replicating Organizational Objects from Employee Central to SAP S∕4HANA

Find the most current version of these guides in SAP Help Portal at http://help.sap.com/hr_ecintegration.

We also recommend that you regularly check the SAP Notes that are published for the LOD-EC-INT-ORG
application area using the SAP ONE Support Launchpad at https://launchpad.support.sap.com/ .

For more information about the implementation of support packages and SAP Notes, see Software Maintenance in
the SAP NetWeaver documentation.

Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee

Central to SAP S/4HANA On Premise
Software Change Management PUBLIC 31
5 Troubleshooting of Organizational Data
Replication from Employee Central

Info on how to troubleshoot organizational data replication from Employee Central to SAP S∕4HANA.

Checking Organizational Assignments Replicated to SAP S∕4HANA [page 32]

Check organizational assignments of a specific employee in SAP S∕4HANA to see whether they were
correctly replicated from Employee Central.

Technical Configuration of the Web Service Runtime Environment [page 33]

Here's an SAP Note that gives instructions on how to set up the technical configuration of the web service
runtime environment and how to check it in your SAP S∕4HANA system.

Known Issues [page 33]

Learn more about some known issues regarding organizational data replication from Employee Central to
SAP S∕4HANA, and how to troubleshoot them.

5.1 Checking Organizational Assignments Replicated to SAP

S∕4HANA

Check organizational assignments of a specific employee in SAP S∕4HANA to see whether they were correctly
replicated from Employee Central.

Context

You can check, for example, whether the employee's assignment was replicated at all and whether the Employee
Central object the employee is assigned to (such as the position) was correctly mapped to an SAP S∕4HANA
object.

Procedure

1. Go to the SFIOM_CHK_EE_ORG_ASS transaction in your SAP S∕4HANA system.

This transaction calls the Display Employee Organizational Assignment Replications

(RH_SFIOM_CHECK_EE_ORG_ASS) program.
2. Select an employee by their SAP S∕4HANA personnel number, Employee Central employee ID, or external
employee ID from Employee Central and choose Execute.

In the upper part of the screen, you're shown the employee's personnel number, employee ID, external
employee ID, and name. The mapping of the personnel number with the employee ID and the external
Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee
Central to SAP S/4HANA On Premise
32 PUBLIC Troubleshooting of Organizational Data Replication from Employee Central
 employee ID is read from the Employee Key Mapping (PAOCFEC_EEKEYMAP) table. If multiple personnel
numbers are shown, this means that the employee has several personnel assignments (for example, because
they have a concurrent employment or are on a global assignment).
3. Expand the information in the lower part of the screen to see the position assignments of this employee per
personnel number, as they exist in the SAP S∕4HANA system over time.

For each position you're shown the assignments to other organizational objects over time, such as
organizational units, jobs, manager positions, or cost centers. The mapping of the object IDs from Employee
Central to object IDs in SAP S∕4HANA. This mapping is read from the Organizational Structure Item Key
Mapping (SFIOM_KMAP_OSI) table. If an object doesn't have an Employee Centrall object ID this means that it
wasn't replicated from Employee Central. It was created directly in the SAP S∕4HANA system.
4. Select an entry with the Person object type and choose Replication Requests to find out whether there are
open, pending, or failed replication requests for the employee.

You're redirected to the staging area viewer (transaction SFIOM_VIEW_REQUESTS). The employee ID and
external employee ID of the employee are preselected so that you only see the requests for this specific
employee.

 Example

Checking the replication requests is useful, for example, when the employee was assigned a new position
in Employee Central, but you don't see this assignment in the SAP S∕4HANA system yet. In this case,
the replication request transferring the new assignment from Employee Central might not have been
processed yet in SAP S∕4HANA.

5.2 Technical Configuration of the Web Service Runtime

Environment

Here's an SAP Note that gives instructions on how to set up the technical configuration of the web service runtime
environment and how to check it in your SAP S∕4HANA system.

Go to SAP Note 1043195 to find more information.

5.3 Known Issues

Learn more about some known issues regarding organizational data replication from Employee Central to SAP
S∕4HANA, and how to troubleshoot them.

Known Issue: You've Created or Changed an Employee's Organizational Assignment in Employee Central, But
This Change Is Not Reflected in SAP S∕4HANA [page 35]
Here's how to troubleshoot organizational assignment replication from Employee Central if changes don't
show up in the SAP S∕4HANA system.

Known Issue: You've Created or Changed an Organizational Object in Employee Central, But This Change Is Not
Reflected in SAP S∕4HANA [page 36]
Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee
Central to SAP S/4HANA On Premise
Troubleshooting of Organizational Data Replication from Employee Central PUBLIC 33
 Here's how to troubleshoot organizational object replication from Employee Central if changes don't show
up in the SAP S∕4HANA system.

Known Issue: Manager Not Yet Replicated From Employee Central [page 37]
Here's how to troubleshoot organizational assignment replication from Employee Central if SAP S∕4HANA
can't determine the employee's manager.

Known Issue: Organizational Assignment Replication from Employee Central Creates New Position and New
Position Assignment Although a Position Assignment Already Exists in SAP S∕4HANA [page 38]
Here's how to troubleshoot organizational assignment replication from Employee Central if SAP S∕4HANA
can't reuse an existing position assignment.

Known Issue: After You've Changed the External Code of an Organizational Object in Employee Central,
Organizational Assignments in SAP S∕4HANA Are No Longer Correct [page 39]
Here's how to troubleshoot organizational data replication from Employee Central if organizational
assignments beome incorrect in SAP S∕4HANA.

Known Issue: After Data Replication from Employee Central to SAP S∕4HANA Error Messages Related to
Positions are Shown in the Application Log [page 40]
Here's how to troubleshoot organizational data replication from Employee Central if the error log in the SAP
S∕4HANA system shows position-related errors.

Known Issue: You Have Changed the Job Classification Title or Description in Employee Central, but Your
Changes Aren't Replicated to SAP S∕4HANA [page 42]
Here's how to troubleshoot organizational data replication from Employee Central if changes to job titles or
descriptions don't show up in the SAP S∕4HANA system.

Known Issue: Organizational Structure Items Can't Be Replicated Because cust_toDivision and
cust_toBusinessUnit Associations Are Missing [page 44]
Here's how to troubleshoot organizational data replication from Employee Central if the middleware shows
errors about cust_toDivision or cust_toBusinessUnit.

Known Issue: "Invalid Property Name" Error Message is Shown for FOBusinessUnit/nameTranslationNav and
FODivision/nameTranslationNav [page 45]
Here's how to troubleshoot organizational object replication from Employee Central if SAP S∕4HANA shows
errors about nameTranslationNav.

Known Issue: Replication Request Monitor Shows Internal Server Error [page 46]
Here's how to troubleshoot position replication from Employee Central if the Replication Request Monitor
shows an internal server error.

Known Issue: Mandatory Field HRP1000-STEXT Was Not Mapped [page 49]
Here's how to troubleshoot organizational object replication from Employee Central if SAP S∕4HANA can't
fill in the STEXT field of the Object (1000) infotpye.

Known Issue: Deletion Isn't Replicated from Employee Central [page 50]
Here's how to troubleshoot organizational object replication from Employee Central if deletions don't show
up in the SAP S∕4HANA system.

Known Issue: Cost Center Assignments Are Deleted When You Use a Default Cost Center in SAP S∕4HANA
[page 51]
Here's how to troubleshoot organizational assignment replication from Employee Central if cost center
assignments overwrite each other in the SAP S∕4HANA system.

Known Issue: Organizational Assignment Change Extends Too Far Into the Past [page 52]
Here's how to troubleshoot organizational assignment replication from Employee Central if the SAP
S∕4HANA system shows an error about changes extending too far into the past.

Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee

Central to SAP S/4HANA On Premise
34 PUBLIC Troubleshooting of Organizational Data Replication from Employee Central
 Known Issue: Staging Area Tables Contain a Large Amount of Data [page 53]
Here's how to troubleshoot organizational data replication from Employee Central if the staging area tables
in the SAP S∕4HANA system contain too much data.

Known Issue: Employee is Inactive, Replicate Active Employee from Employee Central [page 54]
Here's how to troubleshoot organizational assignment replication from Employee Central if replication fails
and the SAP S∕4HANA system shows an error message about the employee being inactive.

5.3.1  Known Issue: You've Created or Changed an Employee's

Organizational Assignment in Employee Central, But
This Change Is Not Reflected in SAP S∕4HANA

Here's how to troubleshoot organizational assignment replication from Employee Central if changes don't show up
in the SAP S∕4HANA system.

What's the issue?

In the Employee Central Data Replication Monitor the corresponding entries typically show the replication status In
Progress.

What you can do

Here's how you can check why the changes weren't replicated from Employee Central to the SAP S∕4HANA system.

Check the incoming SOAP messages

1. Go to the SRTUTIL transaction in your SAP S∕4HANA system and open the Message Monitor.
2. Specify the replication time frame.
3. In the Interface Name field for the receiver, enter the name of the employee organizational assignments
interface (EmployeeOrganisationalAssignmentReplicationRequest_In).
4. Click Execute, then check the result:
• If no entry can be found:
• Check in the middleware whether the process is scheduled and has run successfully. For more
information refer to section Monitoring Tools in the Middleware [page 30].
• Check the SFAPI Audit Log in Employee Central using the session ID from the middleware. For more
information refer to section Analyzing API Calls with the SFAPI Audit Log [page 28].
• If entries are found, double-click the relevant entry to check the transferred data.

Check the replication requests

1. Go to the SFIOM_VIEW_REQUESTS transaction in your SAP S∕4HANA system.

Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee
Central to SAP S/4HANA On Premise
Troubleshooting of Organizational Data Replication from Employee Central PUBLIC 35
2. Check whether there is an entry for the employee whose organizational assignment was changed in Employee
Central. To do so, search for relevant entries using the employee's External Employee ID or Employee ID from
Employee Central.
3. Depending on the status of the entries you find for the employee, carry out the following steps:
• If there is an entry with the status Open:
1. Double-click this entry to display the organizational assignment details.
2. Click Process Selected Requests to process the open request.
3. Refresh the result list and make sure that the entry has disappeared from the list.
• If there is an entry with the status Pending or Failed:
1. Check if there are error messages in the application log. To do so, select the entry and click
Application Log. The object PAOC_SFI_OM, the subobject REPL_REQ_PROCESSING, and the external ID
EMPLOYEE_ID_EXT (which refers to the External ID column in SLG1) are preset. In the Application Log,
check for the reason why the request has the status Pending or Failed. Typical errors are, for example,
that the employee or the assigned organizational object (such as the position) haven't been replicated
yet or that the employee has more than one position assigned. Resolve the error, then go back to
the SFIOM_VIEW_REQUESTS transaction and click Process Selected Requests to process the pending
organizational assignment requests again.
2. Check if the employee was successfully replicated to the SAP S∕4HANA system. To do so, check
whether an entry for this employee exists in the ECPAO_EE_KMAP table.
3. Check if the organizational object (such as the job classification) the employee is to be assigned to was
successfully replicated to the SAP S∕4HANA system. To do so, check in the SFIOM_VIEW_ORG_REQS
transaction if there are open replication requests containing relevant organizational objects. If yes,
click Process Selected Requests to process these requests. If the processing was successful, go back to
the SFIOM_VIEW_REQUESTS transaction and click Process Selected Requests to process the pending
organizational assignment requests again.
4. If the missing assignment refers to a manager, make sure that this manager was replicated to the SAP
S∕4HANA system before you run the organizational assignment request for the employee..

5.3.2  Known Issue: You've Created or Changed an

Organizational Object in Employee Central, But This
Change Is Not Reflected in SAP S∕4HANA

Here's how to troubleshoot organizational object replication from Employee Central if changes don't show up in the
SAP S∕4HANA system.

What's the issue?

Data of organizational objects doesn't seem to be correctly replicated to the SAP S∕4HANA system.

Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee

Central to SAP S/4HANA On Premise
36 PUBLIC Troubleshooting of Organizational Data Replication from Employee Central
What you can do

Check the incoming SOAP messages

1. Go to the SRTUTIL transaction in your SAP S∕4HANA system and open the Message Monitor.
2. Specify the replication time frame.
3. In the Interface Name field for the receiver, enter the names of the interfaces for organizational objects:
• PositionReplicationRequest_In
• JobReplicationRequest_In
• OrganisationalStructureReplicationRequest_In
4. Click Execute, then check the result:
• If no entry can be found:
• Check in the middleware whether the process is scheduled and has run successfully.
• Check the OData API Audit Log in Employee Central.
• If entries are found, double-click the relevant entry to check the transferred data.

Check the replication requests

1. Go to the SFIOM_VIEW_ORG_REQS transaction in your SAP S∕4HANA system.
2. Check whether there are entries for the organizational objects you have created or changed in Employee
Central.
3. Depending on the status of the entries you find, carry out the following steps:
• If there is an entry with the status Open:
1. Select the request and click Process Selected Requests to process it.
2. Make sure that the entry has disappeared from the list.
• If there is an entry with the status Pending or Failed:
1. Select the entry and click Application Log. The object PAOC_SFI_OM, the subobject
REPL_REQ_PROCESSING, and the external ID are preset.
2. Check for relevant error messages for the objects in question and resolve the errors.
3. Go back to the SFIOM_VIEW_ORG_REQS transaction and click Process Selected Requests to process
the replication requests again.

5.3.3  Known Issue: Manager Not Yet Replicated From Employee

Central

Here's how to troubleshoot organizational assignment replication from Employee Central if SAP S∕4HANA can't
determine the employee's manager.

What's the issue?

You are shown this error message in the application log in the SAP S∕4HANA system:

Employee <ID>: Manager <ID> not yet replicated from EC

Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee
Central to SAP S/4HANA On Premise
Troubleshooting of Organizational Data Replication from Employee Central PUBLIC 37
This can happen, for example, if you have managers in Employee Central who are assigned to other companies
than their employees.

What you can do

Make sure that the manager's company ID is transferred from Employee Central so that the SAP S∕4HANA system
can identify the manager. To do so, we recommend to enable replication of associated employee information in the
middleware.

 Remember

If you use the iFlow: EC to ERP - Employee Organizational Assignment Replication v1.0 process in the
middleware, you can set the ECERPORG_READ_MANAGER_COMPANY parameter in the process properties to X
instead of enabling replication of associated employee information. Then the process reads the company of the
manager and delivers it in the web service. But for performance reasons we don't recommend to do so.

5.3.4  Known Issue: Organizational Assignment Replication

from Employee Central Creates New Position and New
Position Assignment Although a Position Assignment
Already Exists in SAP S∕4HANA

Here's how to troubleshoot organizational assignment replication from Employee Central if SAP S∕4HANA can't
reuse an existing position assignment.

What's the issue?

If no position assignment is provided by Employee Central and the existing position assignment in the SAP
S∕4HANA system isn’t considered to be appropriate and therefore can't be reused by the SAP S∕4HANA system,
new positions and position assignments are created. Appropriate means:

• The employee mustn't be assigned to several different positions in overlapping time slices.
• The employee must be assigned to the position during the complete assignment period.
• The position mustn't be shared by several employees.
• The position itself must be valid during the complete assignment period.
• The position mustn't be mapped to an Employee Central position (which would mean that it was replicated
from Employee Central).

If these conditions aren't fulfilled, the existing assignment is delimited. A new position and a new position
assignment are created in the SAP S∕4HANA system.
Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee
Central to SAP S/4HANA On Premise
38 PUBLIC Troubleshooting of Organizational Data Replication from Employee Central
What you can do

Ensure that the listed conditions are fulfilled.

5.3.5  Known Issue: After You've Changed the External Code

of an Organizational Object in Employee Central,
Organizational Assignments in SAP S∕4HANA Are No
Longer Correct

Here's how to troubleshoot organizational data replication from Employee Central if organizational assignments
beome incorrect in SAP S∕4HANA.

What's the issue?

You change the external code of a business unit, division, department, job classification, or position in Employee
Central that is replicated to the SAP S∕4HANA system. In SAP S∕4HANA, the organizational assignments are no
longer correct after data replication.

 Example

You replicate organizational data, including the department with the external code D_1234, from Employee
Central to SAP S∕4HANA. In SAP S∕4HANA, the organizational unit 1234 is created that corresponds to
department D_1234. Then you change the external code of department D_1234 to D_5678 in Employee
Central. Now you replicate the organizational data again from Employee Central to SAP S∕4HANA. The
replication considers the existing department, which now has the new external code D_5678, to be a
new object and therefore creates a new organizational unit 5678. But the employees' assignments to the
department in Employee Central aren't automatically reassigned to the new organizational unit 5678 in SAP
S∕4HANA. In SAP S∕4HANA, the employees are still assigned to the organizational unit 1234.

What you can do

Replicate the affected employee organizational assignments again from Employee Central to clean up the
assignments in the SAP S∕4HANA system.

 Tip

To avoid this kind of error, do not change the external codes of business units, divisions, departments, job
classifications, or positions in Employee Central that are affected by the organizational data replication.

Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee

Central to SAP S/4HANA On Premise
Troubleshooting of Organizational Data Replication from Employee Central PUBLIC 39
5.3.6  Known Issue: After Data Replication from Employee
Central to SAP S∕4HANA Error Messages Related to
Positions are Shown in the Application Log

Here's how to troubleshoot organizational data replication from Employee Central if the error log in the SAP
S∕4HANA system shows position-related errors.

What's the issue?

You are shown error messages for positions in the application log in the SAP S∕4HANA system.

What you can do

When positions haven't been replicated, are invalid, or are shared

The following error messages in the application log in the SAP S∕4HANA system ...

• Pers.No. <no.>: Mapping for position <name> not found (SFIOM_PROCESSING 135)
• Pers.No. <no.>: Position <name> not found (Position ID <ID>) (SFIOM_PROCESSING 137)
• Pers.No. <no.>: Position <name> not valid (Position ID <ID>) (SFIOM_PROCESSING 136)
• Pers.No. <no.>: Position <name> is shared (SFIOM_PROCESSING 141)

... might be due to Position Management enablement in Employee Central. If Position Management is enabled,
employees' position assignments are provided by Employee Central. In this case the SAP S∕4HANA system checks
if the following conditions are fulfilled:

• The position itself must have been replicated from Employee Central so that it is available in the key mapping
table (SFIOM_KMAP_OSI) in the SAP S∕4HANA system.
• The position must be valid during the complete assignment period.
• The position mustn't be shared by several employees.

Therefore make sure that these conditions are fulfilled.

When positions are shared

The error message Pers.No. <ID>: Position <ID> is shared can also be caused by a change of the external code of a
position in Employee Central that is replicated to the SAP S∕4HANA system.

Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee

Central to SAP S/4HANA On Premise
40 PUBLIC Troubleshooting of Organizational Data Replication from Employee Central
  Example

You replicate organizational data, including the position with the external code P_1234 and the assignment of
employee EE123456 to this position, from Employee Central to SAP S∕4HANA. In SAP S∕4HANA, the position
1234 and the assignment of employee EE123456 to this position are created:

Employee Assigned to Position in SAP

Position in Employee Central Position in SAP S∕4HANA S∕4HANA

P_1234 1234 EE12345

Then you change the external code of position P_1234 to P_5678 in Employee Central. The employee EE12345
is still assigned to this position. You also create a new position that gets the external code P_1234 and assign
the employee EE67890 to this position.

Now you try to replicate organizational data again from Employee Central to SAP S∕4HANA. The replication
considers the existing position, which now has the new external code P_5678, to be a new object and therefore
creates a new position 5678. But the assignment of employee EE12345 to the position in Employee Central isn't
automatically redirected to the new position 5678 in SAP S∕4HANA. In SAP S∕4HANA, the employee EE12345
is still assigned to the position 1234. Since you have also assigned employee EE67890 to position P_1234 in
Employee Central, this would theoretically result in the following situation:

Employee Assigned to Position in SAP

Position in Employee Central Position in SAP S∕4HANA S∕4HANA

P_1234 1234 EE12345, EE67890

P_5678 5678

Since shared positions aren't supported by SAP S∕4HANA, the organizational assignment replication fails and you
get the error message Position is shared.

 Tip

To avoid this kind of error, do not change the external codes of positions in Employee Central that are affected
by the organizational data replication.

Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee

Central to SAP S/4HANA On Premise
Troubleshooting of Organizational Data Replication from Employee Central PUBLIC 41
5.3.7  Known Issue: You Have Changed the Job Classification
Title or Description in Employee Central, but Your
Changes Aren't Replicated to SAP S∕4HANA

Here's how to troubleshoot organizational data replication from Employee Central if changes to job titles or
descriptions don't show up in the SAP S∕4HANA system.

What's the issue?

When you create a new job classification in Employee Central and save it, the title and description are automatically
filled into the corresponding translation fields for the default language that has been set in Provisioning.

Viewing Default Translations

Default English Translation

When you change the title or description, the changes are not automatically reflected in the translation fields. The
entries in the translation fields stay the same as before.

Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee

Central to SAP S/4HANA On Premise
42 PUBLIC Troubleshooting of Organizational Data Replication from Employee Central
 Changing a Title

Viewing Changed Translations

English Translation Is Unchanged

The middleware process, however, uses the translated titles and descriptions. This system behavior is intended and
works as designed.

What you can do

If you want to replicate changes to job classification titles or descriptions to SAP S∕4HANA, also change them on
the Translations page.

Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee

Central to SAP S/4HANA On Premise
Troubleshooting of Organizational Data Replication from Employee Central PUBLIC 43
 Changing Translation

5.3.8  Known Issue: Organizational Structure Items

Can't Be Replicated Because cust_toDivision and
cust_toBusinessUnit Associations Are Missing
Here's how to troubleshoot organizational data replication from Employee Central if the middleware shows errors
about cust_toDivision or cust_toBusinessUnit.

What's the issue?

The data model of the new generic objects Department and Division does not contain the cust_toDivision and
cust_toBusinessUnit associations by default. If you haven't added them to the data model, you might see errors
such as the following in the middleware application log:

• Bad request – invalid property name: FODepartment/cust_toDivision

• Bad request – invalid property name: FODivision/cust_toBusinessUnit

The replication of organizational structure items needs the cust_toDivision and cust_toBusinessUnit associations to
build a correct organizational unit hierarchy in the SAP S∕4HANA system.

What you can do

Add these associations to the object definitions of the Department and Division objects when you implement
organizational structure item replication.

 Note

The data model of the former foundation objects Department and Division had included the divisionFlxNav
and businessUnitFlxNav associations by default. Existing implementations that use the divisionFlxNav and
businessUnitFlxNav associations are still supported. But if you implement organizational structure item
replication now, based on the new generic objects, these associations are no longer available.

Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee

Central to SAP S/4HANA On Premise
44 PUBLIC Troubleshooting of Organizational Data Replication from Employee Central
5.3.9  Known Issue: "Invalid Property Name" Error Message
is Shown for FOBusinessUnit/nameTranslationNav and
FODivision/nameTranslationNav

Here's how to troubleshoot organizational object replication from Employee Central if SAP S∕4HANA shows errors
about nameTranslationNav.

What's the issue?

When you run the Create and Execute Organizational Object Replication Query
(RH_SFIOM_ORG_OBJ_REPL_QUERY) program to replicate organizational objects from Employee Central to SAP
S∕4HANA, the following error messages might be shown:

• Invalid property name: FOBusinessUnit/nameTranslationNav

• Invalid property name: FODivision/nameTranslationNav

This is because the nameTranslationNav property is missing in the Employee Central OData API Data Dictionary for
the FOBusinessUnit and FODivision entities.

What you can do

Here's how you can correct this issue:

1. Go to the Admin Center in Employee Central and choose the Configure Object Definitions tool.
2. Search for the Translations object definition.
3. In the details of the defaultValue field, set the visibility to Editable.

Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee

Central to SAP S/4HANA On Premise
Troubleshooting of Organizational Data Replication from Employee Central PUBLIC 45
 Visibility of defaultValue Field
4. Go back to the Admin Center, choose the OData API Metadata Refresh and Export tool, and choose Refresh.
5. Go back and check the OData API Data Dictionary.
nameTranslationNav should now be available for the FOBusinessUnit and FODivision entities.

5.3.10  Known Issue: Replication Request Monitor Shows

Internal Server Error

Here's how to troubleshoot position replication from Employee Central if the Replication Request Monitor shows an
internal server error.

What's the issue?

When you try to process a replication request for a position in the Replication Request Monitor (Web Dynpro
application SFIUI_A_REPL_REQ_MONITOR), you might be shown a 500 SAP Internal Server Error message with
this additional info:

ERROR: No entry in table T528B for S <position ID> (termination: ERROR_MESSAGE_STATE)

Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee
Central to SAP S/4HANA On Premise
46 PUBLIC Troubleshooting of Organizational Data Replication from Employee Central
This happens if you use integration between Organizational Management and Personnel Administration in SAP
S∕4HANA (PA-PD integration) and are trying to process a replication request that refers to a position with
inconsistent data. Inconsistent means that, if PA-PD integration is active and a position is created in Organizational
Management, the system also creates an entry in the Positions (T528B) table in Personnel Administration. But the
replication request in question refers to a position for which no entry exists in this table.

The error message is shown because the Replication Reqest Monitor is trying to redirect to a different transaction,
which is not possible.

What you can do

To correct this issue, go to the Replication Request Viewer (transaction SFIOM_VIEW_REQUESTS) in the SAP
S∕4HANA system and trigger the processing of the request that causes the error from there. Then the system will
redirect you to the Maintain HR Master Data (PA30) transaction, where you can copy the organizational assignment
that has the inconsistent data.

Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee

Central to SAP S/4HANA On Premise
Troubleshooting of Organizational Data Replication from Employee Central PUBLIC 47
 Copying Organizational Assignment

Just save the suggested entries and you are done.

Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee

Central to SAP S/4HANA On Premise
48 PUBLIC Troubleshooting of Organizational Data Replication from Employee Central
5.3.11  Known Issue: Mandatory Field HRP1000-STEXT Was Not
Mapped

Here's how to troubleshoot organizational object replication from Employee Central if SAP S∕4HANA can't fill in the
STEXT field of the Object (1000) infotpye.

What's the issue?

You’re shown the error message Mandatory field HRP1000-STEXT was not mapped (SFIOM_PROCESSING 235) for
an Employee Central entity in the SAP S∕4HANA system. For example, the error message could be:

FODepartment SALES: Mandatory field HRP1000-STEXT was not mapped

FODepartment is the entity name, SALES is the ID of the entity (of the department in this case) in Employee
Central. HRP1000-STEXT is the Object Name (STEXT) field of the Object (1000) infotpye in SAP S∕4HANA.

 Note

STEXT is a required field, which must be mapped. The mapping for this field is contained in the sample content
we provide in the Define Field Mapping for Organizational Data Customizing activity.

What you can do

Depending on what causes the error, here's how you can resolve it:

• You haven't defined a language mapping.

To correct this, go to the Map Languages from Employee Central and ERP activity in Customizing of the
Business Integration Builder and enter the Employee Central locales and SAP S∕4HANA languages you’re
using. Then trigger a full load to replicate the missing names to the STEXT field.

 Note

When mapping locales and languages, make sure that you use the correct format:
• The locale identifier from Employee Central must consist of a language identifier in lowercase and
a location or country/region identifier in uppercase, linked by an underscore. For example: en_US
(English, USA), en_GB (English, UK), fr_FR (French, France), fr_CA (French, Canada).
• The language identifier from SAP S∕4HANA must be a two-character country/region ISO code. For
example: EN, FR.

 Caution

If you use two locales for the same language in Employee Central (such as en_US and en_GB), you need to
decide which of these locales you want to map to an SAP S∕4HANA language. In the SAP S∕4HANA system,
there's only one language identifier you can map (in our example: EN).

• You haven't defined a field mapping for the Object Name (STEXT) field of the Object (1000) infotype.
Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee
Central to SAP S/4HANA On Premise
Troubleshooting of Organizational Data Replication from Employee Central PUBLIC 49
 To correct this, go to the Define Field Mapping for Organizational Data activity in Customizing of the Business
Integration Builder. Map the STEXT field in the Primary Mapping view for the transformation template group
and transformation template you’re using for the entity type (the department in this case). Then trigger a full
load to replicate the missing names to the STEXT field.
• The XML of the OrganisationalObjectReplicationResponse_In web service doesn’t contain any localized name
fields such as name_en_US. Only name_localized and name_defaultValue are contained.
This can’t happen when you create new objects in Employee Central. The issue might have been caused by a
data import to Employee Central, for example, from the SAP S∕4HANA system, which didn't contain localized
fields. Or maybe by migration from foundation to generic objects. To correct the issue, change the affected
entity (the SALES department in this case) in Employee Central and replicate it again.

5.3.12  Known Issue: Deletion Isn't Replicated from Employee

Central

Here's how to troubleshoot organizational object replication from Employee Central if deletions don't show up in
the SAP S∕4HANA system.

What's the issue?

You delete a time slice of an organizational object in Employee Central (for example, of a position). The object
should be transferred to SAP S∕4HANA with the regular replication runs if it is changed. However, this change is not
replicated. The deleted time slice still exists in the SAP S∕4HANA system after the next replication run.

The cause of the problem is that the deletion history isn't enabled for the corresponding object definition
in Employee Central. Therefore, the history of deletions isn't recorded in Employee Central. As a result,
the next Last Modified Query run of the Create and Execute Organizational Object Replication Query
(RH_SFIOM_ORG_OBJ_REPL_QUERY) program in SAP S∕4HANA system doesn't recognize that there's a change
and doesn't replicate the deletion.

What you can do

Enable the deletion history in Employee Central to include deletions of time slices in the regular replication runs.

1. Go to the Admin Center and choose the Configure Object Definition tool.
2. Select Object Definition and the object in question (for example, Position).
3. In the MDF Version History field, select Delete History.
For more information, refer to Basic Configurations in Object Definition in Implementing the Metadata
Framework (MDF).
4. To replicate all deletions that weren't transferred to SAP S∕4HANA, run a full load for the object type in question
(for example, Position).
Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee
Central to SAP S/4HANA On Premise
50 PUBLIC Troubleshooting of Organizational Data Replication from Employee Central
5.3.13  Known Issue: Cost Center Assignments Are Deleted
When You Use a Default Cost Center in SAP S∕4HANA

Here's how to troubleshoot organizational assignment replication from Employee Central if cost center
assignments overwrite each other in the SAP S∕4HANA system.

What's the issue?

You replicate cost center assignments (of departments for example) from Employee Central and map all Employee
Central cost centers to one single default cost center in the SAP S∕4HANA system. Each time a new department-
cost center assignment is replicated from Employee Central, the SAP S∕4HANA delimits (deletes) the existing
organizational unit-cost center assignment (Employee Central departments are represented by organizational units
in SAP S∕4HANA). This is because the time constraint of the Cost Center Assignment (011) relationship (in our
example, the B011 relationship between cost center (object type K) and organizational unit (object type O)) is set
up in a way which doesn't allow for multiple assignments at the same time.

What you can do

Correct the time constraint of the Cost Center Assignment (011) relationship in your SAP S∕4HANA system. Two
tables in SAP S∕4HANA control time constraints – you'll find them in Customizing for Personnel Management,
under Organizational Management Basic Settings Data Model Enhancement Relationship Maintenance :

• Infotype Time Constraint (T777Z) in Customizing activity Maintain Relationships

This table defines the default time constraints for relationships.If you don't make entries in the T77ZR table,
this is the time constraint used for the relationship.
• Infotype 1001 Time Constraint (Target Object Type-Dependent) (T77ZR) in Customizing activity Define Time
Constraint Depending on Target Object Type
If you make entries here, these will override the default settings in table T777Z.

Check first if an entry exists in table T77ZR for the Cost Center Assignment (011) relationship. It might look like this:

Time Constraint in Table T77ZR

Object Type Infotype Subtype Type of Related Object Time Constraint

K 1001 B011 O 2

This means that the B011 relationship from cost center to organizational unit has time constraint 2. This time
constraint allows for only one infotype record of the same type for the same object at the same time. Meaning,
there can only be one cost center-organizational unit assignment at one point in time. All other cost center-
organizational unit assignments will be deleted. If you see such an entry, either change the time constraint to 3. Or

Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee

Central to SAP S/4HANA On Premise
Troubleshooting of Organizational Data Replication from Employee Central PUBLIC 51
delete the entry completely to use the time constraint defined for this relationship in table T777Z, which should
look like this:

Time Constraint in Table T777Z

Object Type Infotype Subtype Time Constraint

K 1001 B011 3

5.3.14  Known Issue: Organizational Assignment Change

Extends Too Far Into the Past

Here's how to troubleshoot organizational assignment replication from Employee Central if the SAP S∕4HANA
system shows an error about changes extending too far into the past.

What's the issue?

When replicating organizational assignments from Employee Central to SAP S∕4HANA, you are shown this
message:

Change for person <employee's personnel number> extends too far into past

This happens because the full transmission start date you defined for data replication is before the retroactive
accounting limit defined for the employee in SAP S∕4HANA. When determining the retroactive accounting limit for
payroll, the SAP S∕4HANA system takes three dates into account and uses the latest (that is, the most recent) of
these dates:

• The date that is stored for the employee in the Earliest Personal Retroactive Accounting Date (PRDAT) field
in the Payroll Status(0003) infotype. PRDAT defines the date up to which master and time data changes are
allowed for the employee and up to which the system carries out retroactive accounting.
• The earliest period for which retroactive accounting can be run in general (as specified for the payroll area).
• The employee's hire date.

Retroactive accounting means that previous payroll results must be corrected because payroll-relevant employee
master data or time data was changed. No changes are allowed for payroll-relevant employee master data or time
data before the retroactive accounting limit because payroll can't process the changed data. When the FTSD is
before the retroactive accounting limit, however, this means that organizational assignment replication might lead
to changes in the SAP S∕4HANA that are before the retroactive accounting limit. Since SAP S∕4HANA can't handle
these changes, you are shown the error message.

What you can do

Make sure that the FTSD is on the same date or after the date defined for the retroactive accounting limit in SAP
S∕4HANA.
Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee
Central to SAP S/4HANA On Premise
52 PUBLIC Troubleshooting of Organizational Data Replication from Employee Central
Example: Retroactive Accounting Limit (Highlighted) and Possible FTSD

Earliest Personal Retroactive Earliest Retroactive Account­

Accounting Date (PRDAT) ing Period of the Payroll Area Hiring Date Full Transmission Start Date

July 1, 2016 January 2015 January 1, 2010 July 1, 2016

empty January 2015 August 1, 2015 August 1, 2015

December 1, 2014 January 2015 January 1, 2010 February 1, 2015

5.3.15  Known Issue: Staging Area Tables Contain a Large

Amount of Data

Here's how to troubleshoot organizational data replication from Employee Central if the staging area tables in the
SAP S∕4HANA system contain too much data.

What's the issue?

Organizational data that is replicated from Employee Central is filled into a staging area in SAP S∕4HANA. A
database update program posts the organizational data from the staging area to the database. The staging area
tables holding the replication requests are filled with more and more data if you don't remove requests that are no
longer needed.

What you can do

Clean up the staging area tables regularly to minimize the number of records in these tables. That is, delete
replication requests that were processed in the SAP S∕4HANA system and are no longer needed. Use the following
programs to do this:

• Delete Organizational Object Replication Requests (RH_SFIOM_DEL_ORG_STRUC_RPRQ)

• Delete Employee Org. Assignment Replication Requests (RH_SFIOM_DEL_EE_ORG_ASS_RPRQ)

Schedule these programs to be run in the background.

Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee

Central to SAP S/4HANA On Premise
Troubleshooting of Organizational Data Replication from Employee Central PUBLIC 53
5.3.16  Known Issue: Employee is Inactive, Replicate Active
Employee from Employee Central

Here's how to troubleshoot organizational assignment replication from Employee Central if replication fails and the
SAP S∕4HANA system shows an error message about the employee being inactive.

What's the issue?

Organizational assignment replication to the SAP S∕4HANA system fails, showing the error message Employee is
inactive in ERP; replicate active employee from EC.

What you can do

This error message either means that an employee is active in Employee Central, but not (yet) active in SAP
S∕4HANA (for example, because the employee was rehired in Employee Central, but this information hasn't been
transferred to SAP S∕4HANA yet). In this case, the error will be gone after the next run of employee master data
replication.

However, the error message is also shown when the employee is actually inactive in Employee Central and their
data should no longer be transferred to SAP S∕4HANA – but the organizational assignment replication process
still tries to transfer this data. To prevent the error from happening in the latter case, filter out time slices in
which employees are inactive. To do this, enter all employment statuses that show that an employee is inactive in
Employee Central (such as Terminated) in the corresponding Ignore Employment Statuses parameter, either in the
middleware or in SAP S∕4HANA Customizing (depending on the integration version you are using).

 Note

If you've already replicated organizational assignments before, including inactive time slices, and then change
your settings to start filtering out inactive time slices, make sure that you trigger a full load after having made
the changes. This ensures that data inconsistencies that may have evolved between Employee Central and SAP
S∕4HANA are cleaned up.

Another potential issue that causes this error might be that the full transmission start date (FTSD) you've defined
for organizational assignment replication from Employee Central is before the FTSD defined for employee master
data replication from Employee Central. If this is the case, correct the FTSD for organizational assignment
replication. Always make sure that you use the same FTSD for organizational data and employee master data
replication from Employee Central to SAP S∕4HANA.

Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee

Central to SAP S/4HANA On Premise
54 PUBLIC Troubleshooting of Organizational Data Replication from Employee Central
6 Reporting Incidents for Organizational
Data Replication

What to do if you face an issue with the organizational data replication.

Procedure

1. Go to our Knowledge Base and check the Knowledge Base Articles and SAP Notes that are published for the
LOD-EC-INT-ORG (Org Integration EC to ERP On Premise) application area for a possible solution.
2. Go to Create an Incident and report an incident for the LOD-EC-INT-ORG component if you can’t find a
solution.

Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee

Central to SAP S/4HANA On Premise
Reporting Incidents for Organizational Data Replication PUBLIC 55
Important Disclaimers and Legal Information

Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:

• Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements
with SAP) to this:

• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.

• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

• Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering an SAP-hosted Web site. By using such links,
you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the
control or responsibility of SAP.

Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the
experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback
(e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and
phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example
code unless damages have been caused by SAP's gross negligence or willful misconduct.

Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities, genders,
and abilities.

Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee

Central to SAP S/4HANA On Premise
56 PUBLIC Important Disclaimers and Legal Information
Managing, Monitoring, and Troubleshooting Organizational Data Replication from Employee
Central to SAP S/4HANA On Premise
Important Disclaimers and Legal Information PUBLIC 57
www.sap.com/contactsap

© 2023 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.

Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.

SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.

Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.

THE BEST RUN