2655576 - FAQ: SAP S/4HANA Cloud integration with SAP SuccessFactors Employee Central

1. Content and software related SAP Notes & KBAs:

1.1 How to transfer employees' availability information?

KBA 2902514 - Setting Up Availability IFlow to replicate Availability Data from SuccessFactors to SAP S/4HANA Cloud.

KBA 2656367 - Troubleshooting Workforce Person Replication Issues from Employee Central to SAP S/4HANA Cloud.
KBA 2772518 - Employees terminated in Employee Central are not visible in SAP S/4HANA Cloud after employee master data replication.

1.3 Where the SAP Best Practices Employee Integration - Employee Central Integration (‏JB1‏) is available?

It is available in SAP Best Practices Explorer: Employee Integration - Employee Central Integration (‏JB1‏).

1.4 What do I need to consider if I have uploaded employee data into SAP S/4HANA Cloud using the Manage Workforce app and want to use the integration scenario for replicating employees from SAP SuccessFactors Employee Central?

KBA 2555311 - FAQs - Manage Workforce app.

1.5 How can I delete employee or contingent worker data from SAP S/4HANA Cloud?

KBA 2702011 - Deleting Employee & Contingent Worker data in SAP S/4HANA Cloud.

1.6 Which other options exist to maintain employee data in SAP S/4HANA Cloud?

KBA 2646803 - How to maintain employee's data in an SAP S/4HANA Cloud.

1.7 Why did the user alias of a business user change although nobody performed a manual change of it in SAP S/4HANA Cloud?

KBA 2700434 - User Alias gets updated automatically by SAP_SYSTEM in SAP S/4HANA Cloud.

1.8 How can I avoid replication of employee payment information to SAP S/4HANA Cloud fails due to the payment information format?

KBA 2736755 - Formatting payment information replication from Employee Central to SAP S/4HANA Cloud.

1.9 Which fields are replicated from Employee Central to SAP S/4HANA Cloud and what is their mapping to the Employee Fact sheet and the Business Partner fields?

KBA 2770396 - Field mapping for employee replication from Employee Central to SAP S/4HANA Cloud.

2. Miscellaneous questions on customer cases:

2.1 What information do I need to provide?

KBA 2518330 - Basic Information to provide while reporting INT Incidents.
KBA 2563519 - SAP S/4HANA Public Cloud - How to create the perfect incident

2.2 What is the correct priority to choose?

Note 67739 - Priority of problem incidents.
KBA 2155319 - Incident Prioritization for "SFSF INTEGRATION".

2.3 How can I find the correct component for app related issues?

KBA 2489730 - How to find which component is related when you have issues on a specific App in SAP S/4HANA.

2.4 Which kind of issues require consulting instead of support?

Note 2706322 - What is Support – What is Consulting: Cloud Solutions.

2.5 Where can I discuss questions on employee integration related topics for SAP S/4HANA Cloud?

SAP S/4HANA Cloud Customer Community.

2.6 How can I provide remote access to my SAP CPI tenant for an SAP Consultant?

KBA 2339299 - Provide SAP Consultant access to Cloud Integration tenants on NEO environment.
KBA 3076689 - Provide user access to SAP Cloud Integration tenant on Cloud Foundry environment.

2.7 Why should I be careful to report maximally one issue per incident?

Note 50048 - Several queries in an incident.

2.8 In SuccessFactors Employee Central, there is External Person ID. In SAP S/4HANA Cloud, there are Personnel Number and Business Partner ID. How are those three different identifiers related?

Suppose they have hired a new employee and created their profile in SuccessFactors Employee Central. What happens? The External Person ID is specified in SuccessFactors Employee Central. Then, the Person ID External is sent to SAP S/4HANA Cloud. SAP S/4HANA Cloud stores the received Person ID External using uppercase letter. SAP S/4HANA Cloud creates Personnel Number (PERNR) in information units called information types or info types. SAP S/4HANA Cloud creates Business Partner ID as a SYNCH message type. Number ranges for all employee related identifiers in SAP S/4HANA Cloud are managed automatically. So, no additional configuration is needed. For more information, see HR Connectivity and Workforce Overview.