SAP Knowledge Base Article - Public

2882329 - Common issues during the SF -> S/4HC replication

Symptom

You are integrating, testing or operating a process integration scenario of SAP S/4HANA Cloud (S/4HC) with SAP SuccessFactors Employee Central (SF) via SAP Cloud Platform Integration (CPI).

You configured your scenario according to SAP Best Practices for the JB1 Scope Item and the Communication Arrangement SAP_COM_0001.

The process of the Employee replication from SF to S/4HC can be, roughly, separated in two processes:

  1. The Replication from SF to S/4HC (the expert area of this process is LOD-EC-INT*)
  2. The synchronization from the HR master data in S/4HC to the Business Partner (BP) in S/4HC (the expert area of this process is CA-HR-S4)

Both processes have to be successful to have a consistent replication process. The errors regarding the first process can be checked in the Data Replication Monitor in SF, for the second option you have to check the Monitor Data Synchronization app in the S/4HC.

Once the following issues are solved, it's recommended to execute the replication / synchronization process again for the affected employees. To trigger manually Employee-BP synchronization please follow this KBA 2800835, for triggering manually Employee Master Data and Organizational Assignments replication from EC to S/4 HANA Cloud please follow this KBA: 2848659.

We recommend to arrange an Schedule An Expert session to investigate if there's any issue in the system once both systems are correctly configured. In this case, please refer to this FAQ to involve expert engineers in this topic.

If any problem remains despite this FAQ, please report an incident for your S/4HANA Cloud system and also provide SF instance ID and admin user ID.

The common issues are:

  1. Errors that appear in the Data Replication Monitor (DRM), both Employee Replication and Employee Organizational Assignment:
    1. Cost center XXXX/XXXXXX does not exist on MM/DD/YYYY
    2. No work schedule rule for key X//XX/YB00 YB0/XXXXXXXX
    3. No entry in T001P for personnel area XXXX / Pernr XXXXXXXX: Infotype 0001 with error
    4. Status changing actions cannot be performed on the same day for XXXXXXXX.
    5. Entry XK does not exist in T005 (check entry) / Pernr XXXXXXXX: Infotype 0002 with error
    6. No entry in table T503 for 1 Y3 / Pernr XXXXXXXX: Infotype 0001 with error
    7. Postal code XXXXX must have the length X / Pernr XXXXXXXX: Infotype 0006, subtype 1 with error
    8. End date MM/DD/YYYY is not permitted; It would cause a gap Pernr XXXXXXXX: Infotype 0001 with error
    9. Employment percentage must be > '0' / Pernr XXXXXXXX: Infotype 0007 with error
    10. Infty 0001: Move of start to past allowed only w/o data change / Pernr XXXXXXXX: Infotype 0001 with error
    11. Action Organizational reassignment is not a hiring action
    12. Personnel Area XXXX does not exist in view V_T500P
    13. Postcondition Violated error affecting infotype Personal Data (0002)
    14. Cost center AAAA/XXXXXXXXXX blocked against direct postings on MM/DD/YYYY
    15. Employee XXXXXXXX not found
    16. Associated information for manager XXXXXXX missing
    17. Manager XXXXXXX not found or Manager XXXXXXX has no position assigned
    18. The Employee Master Data or Employee Organizational Assignment replication is In Progress for a long time
    19. Entry XXXX XXXXXXXXXX does not exist in CSKS (check entry) / Pernr XXXXXXXX:Infotype 0001 with error
    20. Start date after initial entry date (01/01/2020) / Pernr XXXXXXXX: Infotype 0002 with error
  2. Errors that appear in the Monitor Data Synchronization:
    1. Employee: XXXXXXXX - Employee is already replicated via another source system
    2. Entry XXXX XXXXXXXXXX does not exist in SKB1 (check entry) / AKONT: Invalid value (foreign key check failed) / G/L account XXXXXXXX does not exist in company code XXXX / LFB1-AKONT: Plausibility check failed
    3. Bank number and bank account number cannot be generated / Pernr XXXXXXXX: Infotype 0009, subtype 0 with error
    4. Payment method X is not defined in country XX / Payment method  in XX not allowed for payments to persons / Please do not enter bank data for payment method XX / Pernr XXXXXXXX: Infotype 0009, subtype 0 with error
    5. Enter a value for field Last Name of Business Partner (Person) / Errors occurred during call of function module BUPA_CREATE_FROM_DATA
    6. Employee: XXXXXXXX - Invalid EmailAddress XXX
    7. Country for Country Dialing Code XXX not found
  3. Other issues and questions:
    1. How can I change the country-specific checks?
    2. Error "Deactivation of Excl. Org Assgmt not possible. Please contact SAP" in the Communication Arrangement SAP_COM_0001
    3. Error "Appl job cannot be scheduled as 'Exl. Org Assgmt Repl' is set as 'X'" when scheduling a job of type Replicate Organizational Objects
    4. Employee Organizational Assignment appears with status IN PROGRESS in the Data Replication Monitor in EC
    5. Why only one payment information is sent to the BP in S/4HC if I maintained two bank data in SF?
    6. Is the validity of the employee the same as the validity of the user?
    7. Can I reuse the already created employees via Import Employee?
    8. The message "No results to display" is appearing in the DRM but I sent several employees to be replicated
    9. Where can I check the restrictions of this scenario? And the Release Information?

 

Environment

Success Factors integrated with S/4 HANA Cloud

Resolution

The resolution for these common issues are explained here:

  1. Errors that appear in the Data Replication Monitor (DRM), both Employee Replication and Employee Organizational Assignment:

    1. Cost center XXXX/XXXXXX does not exist on MM/DD/YY
      The Cost Center is not created or is not valid in the specific period. In the S/4 HANA Cloud, go to the tile Manage Cost Centers. If the Cost Center is delimited, please consider to extend the validity of the Organization data if the employee has this requirement. If the Cost Center does not exist, please check if the assignment is correct, in this case, create a new Cost Center. Further information in this KBA: 2881816 - Error "Cost center XXXX/XXXXXX does not exist on MM/DD/YYYY"

      Regarding the begin date / end date of the Cost Centers, please ensure to keep the validity in consistency with the relationships of the employees belonging to that Cost Center. If the validity of the Cost Center ends before the relationship of an employee with that Cost Center, the error Pers.No. XXXXXXXX: XXXX not valid (XX XXXX) (Message no. SFIOM_PROCESSING163) will appear.

    2. No work schedule rule for key X//XX/YB00 YB0/XXXXXXX / Pernr XXXXXXXX: Infotype 0007 with error
      The root cause of this error message is that the workschedule sent from SF has more than one word. Currently the system is not prepared to receive more than one word in the worschedule code.

    3. No entry in T001P for personnel area XXXX / Pernr XXXXXXXX: Infotype 0001 with error
      In S/4HC is mandatory to create a Personal SubArea for each Personal Area for each Company Code (all of them with the same ID). This can be configured in S/4HC in the app Manage Your Solution > Configure Your Solution > Organization > Organizational Structure . Further information in the resolution section of this KBA: 2746954 - Error "Invalid CompanyCode" when Importing Employees

    4. Status changing actions cannot be performed on the same day for XXXXXXXX
      Several job information with the same start date are sent from EC. E.g. the following events from an employee are sent to S/4 HANA Cloud:

      Job information 1:
      <event>AA</event>
      <start_date>2020-01-29</start_date>
      <end_date>XXXX-XX-XX</end_date>


      Job information 2:
      <event>BB>/event>
      <start_date>2020-01-29</start_date>
      <end_date>XXXX-XX-XX</end_date>

      The solution is changing the start date of one of the job information to a previous or later date.

    5. Entry XK does not exist in T005 (check entry) / Pernr XXXXXXXX: Infotype 0002 with error 
      Kosovo is not yet an official ISO code – XK is only temporary. If you need this value to be added to your system, please raise a ticket in XX-S4C-SRV-CON requesting it (if you're not able to select that component, please raise a ticket in LOD-EC-INT* or CA-HR-S4 referring to this documentation).

    6. No entry in table T503 for 1 Y3 / Pernr XXXXXXXX: Infotype 0001 with error
      This error can be raised with different value combinations. The standard mapping is defined in the JB1, this error is raised when the employeeClass, the employmentType or the combination between them is wrong.

    7. Postal code XXXXX must have the length X / Pernr XXXXXXXX: Infotype 0006, subtype 1 with error
      The length and requisites for each postal code can be checked in this link. Please check if the information for the employee and the company is correct.

    8. End date MM/DD/YYYY is not permitted; It would cause a gap Pernr XXXXXXXX: Infotype 0001 with error
      This error message is raised when the action type is incorrectly configured or when the working time percentage is 0 for an active period (for the checks regarding the employment percentage, please check the next question).

    9. Employment percentage must be > '0' / Pernr XXXXXXXX: Infotype 0007 with error
      Please check the employment percentage in SF and enter a value greater than 0 if the employee has status Active.

    10. Infty 0001: Move of start to past allowed only w/o data change / Pernr XXXXXXXX: Infotype 0001 with error
      This error appears when you're changing some relevant information of the employment of the employee, for example, extending the validity of the employment to a previous date and this new inserted data is different than the current employee's information. You cannot add a new previous record that changes the hiring date with new information. But you can change the hiring date and later change the employment data in case of any typo error.

    11. Action Organizational reassignment is not a hiring action
      Please check if the Event Reason is mapped to a Hiring action instead of an Organizational reassignment. It's not possible to add a Hiring action if the employee is currently active.


    12. Personnel Area XXXX does not exist in view V_T500P
      The Personal Area is not defined for the Company Code. The solution should be add the entities like explained here: 2746954 - Error "Invalid CompanyCode" when Importing Employees

    13. Postcondition Violated error affecting infotype Personal Data (0002)
      Possible cause for this behavior is that an incorrect birth date prior to 01.01.1800 has been informed for the employee in SF Employee Central. As this date is less than the SAP minimum date possible, the system fails with Postcondition Violated when it tries to replicate the employee into S/4HANA Cloud system. Please ensure correct birth date has been informed for the employee and replicate it again. (Information took from 2656367)

    14. Cost center AAAA/XXXXXXXXXX blocked against direct postings on MM/DD/YYYY
      When replicating the employee into S4HC the cost center will be assigned, and the requirement is that this cost center should not be locked for primary postings on the assignment period. If you find this error you should either remove the lock for primary postings in the cost center master in Cost Center app in S4HC, or either assign another unlocked cost center to the employee in SF. (Information took from 2656367)

    15. Employee XXXXXXXX not found
      What most likely happened is that there was some delay in the Employee Master Data replication which then temporarily affected the subsequent attemp to process the Organizational Assignment replication (because the organizational assignment needs the employee to exist). In order to solve this, first the Employee Master Data replication should be completed correctly and the employee created in target S/4HANA Cloud system. (Information took from 2656367)

    16. Associated information for manager XXXXXXX missing
      This error appears if the manager of the employee for whom organizational assignments are replicated is not active during the relevant assignment period. To further analyze this situation, check the corresponding manager data in SF Employee Central, to see if there is a termination or some period of inactivity. Then check the corresponding subordinate employee in SF Employee Central. In the job information, the corresponding assignments to the manager should be done in periods where the manager is only active. This is a requirement for correct replication of this managing relationship. If the manager is assigned but not active during the whole assignment period, then such data should be adjusted in EC and subordinate, manager and their organizational assignments should be replicated again. (Information took from 2656367)

    17. Manager XXXXXXX not found or Manager XXXXXXX has no position assigned
      Ensure that the manager is successfully replicated before subordinate employees can be replicated, and check ensure the manager has a position assigned in each of the active job information time slices. (Information took from 2656367)




    18. The Employee Master Data or Employee Organizational Assignment replication is In Progress for a long time
      If the Employee Master Data replication is successful but the Employee Organizational Assignment is In Progress, probabaly the Manager of the Employee is not yet replicated or any Object with a direct relationship with the Employee is not yet replicated.
      If both replication types are In Progress for a long time, maybe there was an specific error which caused a dump in the replication system. If after following the steps mentioned in the JB1 to Reset Employee Master Data and Organizational Assignment Replication, the next replication process is still In Progress, please raise a ticket in LOD-EC-INT*.



    19. Entry XXXX XXXXXXXXXX does not exist in CSKS (check entry) / Pernr XXXXXXXX:Infotype 0001 with error
      The Cost Center must exist in the S/4HC side. With the tile Manage Cost Centers you can see the available Cost Centers. Please maintain consistently the SF data and the S/4HC data.




    20. Start date after initial entry date (01/01/2020) / Pernr XXXXXXXX: Infotype 0002 with error
      An employee cannot be hired without any Personal Information (like Name, Gender, Nationality...). Please check in SF whether the start date of the Personal Information is older than the hiring date of the Job Information, this is not allowed. To solve this issue, please align the validity of both sections and replicate the employee again.


  2. Errors that appear in the Monitor Data Synchronization:

    1. Employee: XXXXXXXX - Employee is already replicated via another source system
      The employee was already replicated from SF and it cannot be updated via Import Employee. In case you want to maintain the master data for an employee, the changes have to be done in the source system of information. If this employee was replicated from SF, the changes must be done there. Further information in this KBA: 2882261 - Error "Employee: XXXXXXXX - Employee is already replicated via another source system."

    2. Entry XXXX XXXXXXXXXX does not exist in SKB1 (check entry) / AKONT: Invalid value (foreign key check failed) / G/L account XXXXXXXX does not exist in company code XXXX / LFB1-AKONT: Plausibility check failed
      The G/L Account External ID for this Company Code is not configured correctly in the S/4HC side. Please go to the tile Manage G/L Account Master Data and create the relationship between the G/L Account and the Company Code.

    3. Bank number and bank account number cannot be generated / Pernr XXXXXXXX: Infotype 0009, subtype 0 with error
      This error could be raised in case of invalid IBAN or wrong configuration of the checks. Please confirm the vailidty of the IBAN and the configuration depending on the country, the Country-specific checks for the bank must fulfill the configuration detailed in this Note: 1012293 - IBAN and maintenance of bank master data. This configuration can be changed in the SSCUI 102592 - Set Country Specific Checks by following this KBA: 2784057 - How to Define Country-Specific Checks in S/4HANA Cloud. 

    4. Payment method X is not defined in country XX / Payment method  in XX not allowed for payments to persons / Please do not enter bank data for payment method XX / Pernr XXXXXXXX: Infotype 0009, subtype 0 with error
      The configuration of the bank details is wrong. There are some countries with limitations like no foreign bank transfer is supported. This configuration can be changed in the SSCUI 101972 - Set Up Payment Methods per Country for Payment Transactions, further information in this KBA: 2879389 - Error "Please do not enter bank data for payment method XX" (RP568) for Bank Transfer payment method

    5. Enter a value for field Last Name of Business Partner (Person) / Errors occurred during call of function module BUPA_CREATE_FROM_DATA
      The Last Name field is a mandatory field for the creation of the Business Partner, this value is commonly retrieved from the Last Name of the employee. Please fill this Last Name in the SF side.

    6. Employee: XXXXXXXX - Invalid EmailAddress XXX
      The Email Address has to be a valid address, that's to say, it must contain an email prefix and an email domain, both in acceptable formats, only one @, without spaces, among other requisites.

    7. Country for Country Dialing Code XXX not found
      In S/4HC the country dialog is not properly maintained or the data in SF for the dialing code is wrong. 

  3. Other issues and questions:

    1. How can I change the country-specific checks?
      This configuration can be changed in the SSCUI 102592 - Set Country Specific Checks by following this KBA: 2784057 - How to Define Country-Specific Checks in S/4HANA Cloud. 

    2. Error "Deactivation of Excl. Org Assgmt not possible. Please contact SAP" in the Communication Arrangement SAP_COM_0001
      This error appears when this parameter was set to 'X' during system setup and there are entries from SF in key mapping table (this means, there're employees already replicated with this setting in the S/4HC system). This parameter cannot be changed again. As this would lead to inconsistency. This is explained in the section "Create Communication Arrangement SAP_COM_0001" of the JB1 -> If you've entered X and have already replicated employee data, you cannot reset the value X anymore.

    3. Error "Appl job cannot be scheduled as 'Exl. Org Assgmt Repl' is set as 'X'" when scheduling a job of type Replicate Organizational Objects
      The value 'X' in the settings of the Communication Arrangement SAP_COM_0001 for the property name Excl. Organizational Assgmt Replication means that the replication of organizational assignment data to S/4HANA Cloud is limited to the manager and cost center assignments only, hence you don't need the iFlow for replicating generic object data at all, since no corresponding organizational assignment data will be replicated to S/4HANA Cloud. So, the replication of Organizational Objects is not allowed as it's not used at all in the target system.

    4. Employee Organizational Assignment appears with status IN PROGRESS in the Data Replication Monitor in EC
      This generally means that the organizational assignment replication could be saved in target S/4HANA Cloud, but the post processing logic has not yet been executed or has failed, and therefore the confirmation message has not yet been received in SF.

      To discard known causes, please ensure from the S/4HANA Cloud that the corresponding job is properly scheduled. If the job is not scheduled the organizational assignment will remain unprocessed. This configuration is explained in the JB1 guide, in the section Scheduling Process Organizational Assignments. (Information took from 2656367)

    5. Why only one payment information is sent to the BP in S/4HC if I maintained two bank data in SF?
      The payment information in S/4HC is only needed for the expense payout, as there's no payroll in S/4HC. Therefore if there's any EXPENSE pay type, this will be synchronized, and not MAIN. (As there's no payroll in S/4HC, the MAIN bank is not needed if there's any expense payment data). If you want to have only MAIN considered, please don't use EXPENSE in SF. You maybe can re-use one of the other pay types (like BONUS) if payroll is not in scope. So, changing the pay type (not reusing EXPENSE) is currently the only solution. Furthermore, in the Section Setting Up Payment Information of the JB1 you can see that SAP S/4HANA Cloud does require payment informationfor handling expense payments to employees in SAP S/4HANA Cloud or if an employee shall obtain an automatically generated supplier. Such a supplier is a prerequisite for integrating SAP S/4HANA Cloud with SAP Concur or SAP SuccessFactors Employee Central Payroll.

    6. Is the validity of the employee the same as the validity of the user?
      By default, if an employee is terminated in SF and replicated to S/4HC, the employee will be terminated (and the validity wil be delimited (probably the employee won't appear when searching for it because the CDS view consumed in the Search bar filters out the inactive employees), but the user associated to this employee is still valid. In case you want to change this behavior, please follow the indications of 2821839 - Employee is terminated but his user is still valid in S/4HANA Cloud

    7. Can I reuse the already created employees via Import Employee?
      Yes. By following the recommendations of this KBA: 2813743 - Considerations when activating Employee Integration (JB1) with already existing Employees in S/4 HANA Cloud, you will be able to link an existing employee in the S/4HC to the corresponding employee existing in SF.

    8. The message "No results to display" is appearing in the DRM but I sent several employees to be replicated
      This message could appear if the replication process is not being executed for any reason. Please reset the query of the replication process by following the section Reset Employee Master Data and Organizational Assignment Replication in the JB1 guide and check again. If after changing the status the issue is still appearing, please delete the queries and execute a Full Load.


    9. Where can I check the restrictions of this scenario? And the Release Information?
      In the Important SAP Notes of the main page in SAP Help for SAP S/4HANA CLOUD, in the Release Restriction Note link. In the KBA you will see the Human Resources section. There is also a link for the Release Information Note.

 

See Also

SAP Help Portal for S/4 HANA CLOUD

2646803 - How to maintain employees data in an S/4HANA Cloud

2800835 - How to trigger manually Employee-BP synchronization in S/4HANA Cloud systems

2848659 - How to trigger manually Employee Master Data and Organizational Assignments replication from EC to S/4 HANA Cloud

2655576 - FAQ: SAP S/4HANA Cloud integration with SFSF EC

2555311 - FAQ - Import Employees app

Keywords

00058, F2081, CVI_API007, CVI_API001, /SHCM/EMP_PASEIN_CL024, PG058, ECPAO_IN_PROCESSING076, BF00013, ECPAO_IN_PROCESSING080, R11401, R11 401, R11335, R11 335, /SHCM/EMP_PASEIN_CL004, FS4BPU_EMPL_MINIMSTR046, ECPAO_IN_PROCESSING055, Query can't be created; last modified date goes back more than 3 months, Message no. ECPAO_IN_QUERY032, 00058, ECPAO_IN_PROCESSING076, PG210 , KBA , LOD-EC-INT-EE , Employee Integration EC to ERP On Premise , CA-HR-S4 , Cross-Application HCM Objects in S/4HANA , CA-GTF-INT-EC , with SFSF EC (JB1, 1NL) , LOD-EC-INT-ORG , Org Integration EC to ERP On Premise , LOD-SF-INT-SAP , Please use LOD-EC-INT* , How To

Product

SAP S/4HANA Cloud all versions