Troubleshooting Data Replication from SAP SuccessFactors Employee Central

Objectives

After completing this lesson, you will be able to:
  • Resolve common issues related to data replication
  • Using the check tool for SAP SuccessFactors Employee Central to SAP S/4HANA integration checks

Excluding Employee Records with Errors from Data Replication

It is possible to suspend the processing of the data replicated for a specific employee from Employee Central when an exceptional error occurs. This enables the data of the other employees replicated with the same package to be processed in SAP S∕4HANA.

Prerequisites

You must have permission to access the ECPAO_IN_QUAR transaction. The permission is included in the template role that we provide for a user who is to analyze the replication and troubleshoot it if necessary: SAP_HR_ECPAO_ANALYSIS.

You can use the Identify to Exclude from Processing (ECPAO_IN_EE_EXCP) transaction to find the employee for whom the exception occurred.

Note

You can also use the Identify to Exclude from Processing transaction as an alternative to the Exclude Employees from Processing transaction because it also allows you to temporarily exclude employees from processing.

Context

With the Exclude Employees from Processing (ECPAO_IN_QUAR) transaction, you can exclude an individual employee for whom an exceptional error occurred from processing in SAP S∕4HANA. The other employees can be processed and their data can be updated in the corresponding infotypes.

Procedure

  1. Go to the Exclude Employees from Processing (ECPAO_IN_QUAR) transaction in your SAP S∕4HANA system to run the Temporarily Exclude Employees from Processing of Replicated Data (ECPAO_MNTN_ECPAO_IN_QUAR) program.

    The program calls the Employees Temporarily Excluded from Productive Processing (ECPAO_IN_QUAR) view.

  2. Choose New Entries.
  3. Choose the value help (for example, by pressing the F4 key).
  4. Search for the external employee ID from Employee Central.
  5. Double-click the person GUID found to copy it to the view.

    We use the person GUID because it is unique.

  6. Save your entries.

Results

When you try to process the replication request of an employee whose person GUID has been added to the Employees Temporarily Excluded from Productive Processing view, the request gets the status Failed. The application log displays a corresponding error message. The replication requests of the other employees can be processed as usual.

Note

When the processing is simulated, the employee is not excluded from the processing. In the simulation mode, the exception still stops the processing of the complete processing run.

Next Steps

Analyze and fix the problem. You can, for example, process the replication request for the employee in question again in the staging area to find out more about what caused the exception and how to solve it. After you've fixed the error, go to the ECPAO_IN_QUAR transaction again (or go to the ECPAO_IN_EE_EXCP transaction) and remove the employee's person GUID from the Employees Temporarily Excluded from Productive Processing view to enable the processing of their data again.

Performance Optimization and Recommendations

Here are some best practices to help you improve the performance of data replication from Employee Central.

Replication of employee master data (including organizational assignments) and organizational objects from Employee Central is triggered by SAP S∕4HANA. The SAP S∕4HANA system initiates a process in the middleware, which requests data from Employee Central and sends it back to SAP S∕4HANA. The following recommendations can help you improve the performance of this replication.

Parallelization

We don’t recommend parallelizing data replication from Employee Central because parallelization wouldn’t improve the performance significantly.

It would be a possible approach to parallelize data replication by triggering the same integration process multiple times from the SAP S∕4HANA system and defining appropriate selection parameters to make sure that each of these process instances transfers a different set of data. But because the middleware sends the data asynchronously to the SAP S∕4HANA system, SAP S∕4HANA rather than the middleware is the limiting factor.

Package Size

We recommend that you use the default setting of 400 configured in the middleware. If you want to change the package size, we recommend that you don't send very small packages because this generates numerous inbound calls to your SAP S∕4HANA system. A large number of calls can interfere with the processing queue, thus impacting the performance.

Scheduling

We don’t recommend trying to achieve a real-time integration by using very short replication cycles (such as replicating every minute). If you need to replicate a specific employee immediately, use push replication.

If you replicate different types of data from Employee Central to your SAP S∕4HANA, we recommend that you schedule the replication processes with the same interval but with different timelines to avoid running multiple replication processes at the same time.

Define the schedule for replication of organizational objects by object type, based on how frequently changes are being made in Employee Central.

Server-Side Paging

We don’t recommend that you have server-side paging disabled in SAP SuccessFactors Provisioning. Employee master data and organizational assignment replication uses the CompoundEmployee API to request data from Employee Central. The API uses server-side paging to optimize the performance if large amounts of data need to be read.

Configuration in SAP S∕4HANA

We recommend that you use as few transformation template groups as possible. Combine as many entities as possible in one template group. For replication of organizational objects, you can use the filtering to differentiate between entities if necessary. This configuration reduces the number of subsequent queries being sent by the SAP S∕4HANA system.

Confirmations

You can disable sending confirmations for replicated employees from SAP S∕4HANA to Employee Central during the initial load. You can enable the confirmations again when the initial load is complete and you switch to delta replication.

To disable confirmations, go to Customizing for the Business Integration Builder and choose Employee Data→ Configuring the Selection of Employee Data for Replication→ Define Parameters for Employee Master Data and Org. Assignment Query. Then select the No Confirmation checkbox. Even if confirmations are disabled, you can analyze errors that occur during the initial load using the application log in the SAP S∕4HANA system.

Logging

We recommend that you disable extended logging in the middleware. Enable extended logging only if there is a problem with analyzing the issue during the replication.

Caution

For data protection reasons, enable the extended log for troubleshooting purposes only. Make sure that you disable the parameter again afterward.

If you enable the extended log, the complete message payload containing all data that is to be transferred is stored in the log. Make sure that you configure permissions in a way that only authorized persons can view the payload in the log. Also ensure that you're compliant with the data protection and privacy regulations so that your data gets the highest level of protection.

General Recommendations

Hint

Check your firewall and proxy for restrictions on the maximum package size. If necessary, adjust the firewall and proxy settings or the package size according to your integration.

Deactivate integration processes that you no longer use.

By the latest when you switch from your development and test environment to your production environment, disable all integrations that you have set up for development and testing purposes. Trigger them only on demand.

Check whether an integration really needs to run 24/7. For some data types it might be sufficient to replicate only from time to time. You can increase the time interval for the affected processes to replicate this data less frequently.

If an error occurs during the integration, stop the scheduler. It does not make sense to continue a replication that constantly generates error messages. Running the replication merely overloads the logs and makes error analysis more difficult.

Configuration Options in SAP SuccessFactors Employee Central

Learn how to use the check tool to find potential issues that have impact on the SAP SuccessFactors Employee Central to SAP S/4HANA replication.

Prerequisites

Before using the check tool, complete the following steps:

  1. Enable Metadata Framework.
  2. Assign Access Check Tool and Allow Configuration Export to your role in Role-Based Permissions (RBP).
    • Access Check Tool authorizes users to access the tool.
    • Allow Configuration Export authorizes users to attach configuration information to a ticket.
  3. Some checks have a quick fix, which can be used to immediately correct any issues found by that check. If you want to use the Quick Fix feature for the checks that have it, assign the Allow Check Tool Quick Fix permission.

Tip

Refer to Guided Answers for the Check Tool for a guided navigation through the available check tool checks and more information on each check.

Context

The SAP SuccessFactors check tool helps you identify and resolve issues when your system doesn’t work as you expect. When you run the check tool, you can see the list of issues in your configuration or data, the severity of each issue, and the solution or recommendation to address the issue.

Use the check tool to perform the check in Employee Central for any configuration issues that might impact the integration process.

To access the check tool from the SAP SuccessFactors Admin Center page, complete the following steps:

  1. Go to Admin Center.
  2. In the tools search field, type Check Tool.
  3. In Application, select EC ERP Replication.

    Note

    All Applications runs checks in all your applications.

    You see the checks for the application you selected. The description for each check describes the situation you hope to find in running the check. For example, in running the check Employee Central Position Management feature is enabled, you hope to find that the Position Management Switch is indeed enabled.

  4. To run all checks, select the checkbox in the top left-hand side of the table. To run some checks but not others, select the check you wish to run.

    Note

    To understand what a check does, right click the Check ID. The system then displays some information on the check.

  5. Click Run Checks to check your applications for the checks you selected.

Log in to track your progress & complete quizzes