2023-03-03
2578294
2578294 - FAQ - Employee to Business Partner
synchronization in S/4HANA OnPremise
Version
61
Type
SAP Knowledge Base
Article
Language
English
Master
Language
English
Release
Status
Released to Customer
Category
How To
Component
CA-HR-S4-OP-BP (HCM Business Partner
Integration)
Released On
02.03.2023
Please find the original document at https://launchpad.support.sap.com/#/notes/2578294
Symptom
You are triggering the synchronization between the employees and the Business Partners in an S/4HANA
system with the solution documented in attached guide in note 2340095.
During the process you found one or more doubts or problems.
Proceed to the resolution section of this FAQ -Frequently Asked Questions- article for the answers of the
following:
1. Initial considerations when using Business Partner synchronization in S/4HANA OnPremise.
2. How to configure the system for this new integration? And what about the former integration from
HRALXSYNC (HRALX/PBPON flag from T77S0 view, etc.)
3. Which are the recommendations to trigger the INITIAL synchronization?
4. How to check SLG1 log for the synchronization between Employees and Business Partners in
S/4HANA OnPremise?
5. How to fill or change data for the Business Partner during the synchronization, which is outside the
scope of delivered standard?
6. How to replace an incorrect user assignment to Employee/BP after the synchronization was already
executed?
7. How can the automatic generation of role FLVN00 be avoided in S/4HANA synchronization, leaving
only the creation of BUP003 role?
8. Is there any synchronization triggered to BP Customer role?
9. How can the employee BPs be maintained in BUP003 role without any connection to HCM?
10. How to handle performance issues during the synchronization?
11. How to block or unblock the vendor role when the employee becomes inactive or active ?
12. Vendor was not generated properly by the S/4HANA Employee to BP synchronization
13. CALL_FUNCTION_REMOTE_ERROR dump received from BP synchronization
14. Messages "HCM001 identification Category Type is missing" and "HCM001 Address Type is missing"
appear in SLG1 log
15. Message R1000 "Error_Time Dependency_Addresses ADVW_VALIDITY_ERROR" appears in SLG1
log
16. Message R1279 "Business partner category 1 is not allowed for BP role ******" appears in SLG1 log
17. Message R11119 "Business partner GUID is blank" appears in SLG1 log
18. Message R11245 "Error for validity periods of address usages" appears in SLG1 log
19. Message /SHCM/EMPLOYEE_BL107 "Vendor-BP *** of Vendor *** is not in Person Category"
appears in SLG1 log
© 2023 SAP SE or an SAP affiliate company. All rights reserved
1 of 11
2023-03-03
2578294
20. Message /SHCM/EMPLOYEE_BL100 "Employee ***: Two different CP linked to the same
employee(P-CP,CP-BP)" appears in SLG1 log
21. How to configure the system to maintain the same number between the Business partner and the
employee.
22. Message CVI_MAPPING043 "Vendor & already exists" appears in SLG1 log.
23. SAPSQL_DATA_LOSS Runtime Error dump received from BP synchronization.
24. Message /SHCM/EMPLOYEE_BL073 "Employee &1 : There is no valid CP-P relationship maintained."
appears in SLG1 log.
25. Message AM653 "Postal code & must have the length &" appears in SLG1 log.
26. Message R11401 "Enter a value for field Last name of business partner (person)" appears in SLG1
log.
27. Message R1286 "Business Partner XXXXXXXX already exists".
28. Message /SHCM/EMPLOYEE_BL074 "Employee XXXXXXXX :Infotype 0001 is not available or has
incorrect data on YYYYMMDD".
29. Message AM049 "Person could not be deleted as it is still used".
30. Message AM056 "Specify a valid address use (ADDRESS_REFERENCE)"
31. Message AM057 "Specify a valid person use (PERSON_REFERENCE)" or MESSAGE_TYPE_X
exception with CALL_FUNCTION_REMOTE_ERROR dump
32. Data from the business user associated to the employee has been removed from table view
USER_ADDR.
33. Issues with BP number related to employees sent via ALE iDocs from another system
34. Creating employees via LSMW does not trigger synchronization so the Business Partner will not be
created.
35. Message R1137 "'Valid-From' date may not be greater than 'Valid-To' date" appears in SLG1 log
36. Message R1477 "Number XXXXXXXX is already assigned to partner XXXXXXXXXX for ID type
HCM001"
37. Message R1212 "Grouping XXX does not exist"
38. Message R1225 "Bank details with ID HC01 already exists"
39. Several PERNRs are connected to the same CP. One PERNR is inactive while other is still active.
However, the role BUP003 shows "Expired".
40. Huge number of change pointers are generated in table CDPOS due to synchronization.
41. Message HRALX00_ORG301 "HR integration is not active".
42. Message /SHCM/EMPLOYEE_BL072 "The USER to assign XXXXX does not exist. Please create the
USER in SU01".
43. Business Partner cannot be archived.
44. How to see logs of the synchronization that is triggered during changes in HR master data records (for
example, via tcodes PA30/PA40)?
For additional FAQ information, you can also refer to note 2409229.
Environment
• S/4HANA OnPremise edition
• Integration from the Employee to the Business Partner
Resolution
1. Initial considerations when using Business Partner synchronization in S/4HANA OnPremise
S/4HANA Employee to Business Partner Synchronization reads the Employee data and synchronizes
to BP/Vendor: It also links the User to the BP in case an User was linked to the employee via 0105
infotype (0001 subtype). The consecuence of this process is the employee will become the unique
© 2023 SAP SE or an SAP affiliate company. All rights reserved
2 of 11
2023-03-03
2578294
source for information and, therefore, it will not be possible to update/overwrite user data via, for
example, transaction SU01. In case it is necessary to modify user data, the employee must be updated
with the new information and the BP Synchronization be triggered afterwards.
2. How to configure the system for this new integration? And what about the former integration
from HRALXSYNC (HRALX/PBPON flag from T77S0 view, etc.)
First of all here it is important to remark that there are two different types of Employee-BP integrations.
This separation was needed because the data model is different in an S/4HANA system compared to
previous ERP model. For all details about the configuration check Employee-Business Partner
Synchronization section of the S/4HANA Installation guide or alternatively the document attached in
note 2340095.
As part of the setup you will need to configure some HRALX switches in the table T77S0 : HRAC,
PBPON, PNUMB. From 1709 SPS1 or after applying the SAP notes 2535438 and 2549563 in 1709, it
is needed to set HRALX HRAC to ‘X’ and HRALX PBPON to ‘ON’ to synchronize Employee
information. On the other hand in former releases, HRALX PBPON should be set to OFF. More details
can be found in the installation guide.
Also other configuration settings can be as well reviewed in the corresponding IMG node
documentation, as follows:
SPRO
Personnel Management
SAP S/4HANA for Human Resources
Synchronization of Business Partner for SAP HCM Employee Role
3. Which are the recommendations to trigger the INITIAL synchronization?
Please refer to KBA 2717481 - Setting up the INITIAL Employee to BP synchronization in S/4HANA
OnPremise
4. How to check SLG1 log for the synchronization between Employees and Business Partners in
S/4HANA OnPremise?
You can check the results of the report in the log via transaction SLG1 for object
SHCM_EE_INTEGRATION, Subobject BUPA_SYNC.
See KBA 2553518 for further details.
5. How to fill or change data for the Business Partner during the synchronization, which is outside
the scope of delivered standard?
You may need to implement BUPA_INBOUND BAdI to introduce the desired changes. When
implementing the BADI, some considerations need to be followed to avoid problems in the program
flow.
Please check further details in KBA 2568218 - BP integration: Considerations when implementing
BUPA_INBOUND BAdI
6. How to replace an incorrect user assignment to Employee/BP after the synchronization was
already executed?
There are some specific steps which need to be followed when replacing the user assignment of the
employee with the Employee to BP synchronization.
Please check attached KBA 2597146 where this is documented in detail.
7. How can the automatic generation of role FLVN00 be avoided in S/4HANA synchronization,
leaving only the creation of BUP003 role?
In S/4HANA synchronization from Employee to Business Partner, the generation of Vendor with role
© 2023 SAP SE or an SAP affiliate company. All rights reserved
3 of 11
2023-03-03
2578294
FLVN00 is expected and triggered automatically, and there is not any configurable option in the
standard to deactivate this separately from the Business Partner synchronization.
As an alternative, you could consider creating a custom implementation of BUPA_INBOUND BADI,
where you could remove the unwanted roles the moment they are being added. When implementing
that BADI, some considerations need to be followed to avoid problems in the program flow. For details
about this see in KBA 2568218.
8. Is there any synchronization triggered to BP Customer role?
This is not part of the functionality. As part of our standard S/4HANA Employee to Business Partner
synchronization we are not synchronizing any data regarding BP "Customer" role. As explained in the
S/4HANA Installation guide the synchronization is possible for the following roles:
○ Employee: BUP003, 1511- till SP1: FLVN01, 1511 SP2 & higher releases FLVN00.
In case of custom requirements on regard of Customer BP role, then customers would need to
evaluate and test the possibility of covering them with some own logic, for example with the help of
some existing badis such as BADI CVI_CUSTOM_MAPPER and its method
MAP_BP_TO_CUSTOMER, etc.
9. How can the employee BPs be maintained in BUP003 role without connection to HCM?
This role cannot be maintained from BP transaction. But since S/4HANA 1709 FP1 there is an app
named Maintain Employees which can be used to create Business Users in BusinessPartner Role
BUP003 (Employee) without HCM connection. Please refer to KBA 2646823 for more details.
10. How to handle performance issues during the synchronization?
Please check trouble shooting KBA 2647154 - Performance with Employee to BP synchronization in
S/4HANA OnPremise. General troubleshooting guide.
11. How to block or unblock the vendor role when the employee becomes inactive or active?
Please check KBA 3132597 - How to block or unblock the vendor role when the employee becomes
inactive or active
12. Vendor was not generated properly by the S/4HANA Employee to BP synchronization
Even if vendor role FLVN00 gets created, it could happen that the vendor cannot be created because
of some data missing or problem. Check KBA 2612009 for details. If the FLVN00 role was not
generated, please check this KBA 2832124 - How to generate a vendor role FLVN00 during
synchronization employee to BP .
13. CALL_FUNCTION_REMOTE_ERROR dump received from BP synchronization
A dump CALL_FUNCTION_REMOTE_ERROR could be generated with short text "The ASSERT
condition was violated." Check description of KBA 2556692 for the solution.
14. Messages "HCM001 identification Category Type is missing" and "HCM001 Address Type is
missing" appear in SLG1 log
Make sure you have followed all the customizing described in the IMG node:
1) Cross-Application Components -> SAP Business Partner -> Basic Settings -> Basic Settings ->
Identification Numbers -> Define Identifcation types
Check if the BP Identification type HCM001 is available.
2) Cross-Application Components -> SAP Business Partner -> Basic Settings -> Basic Settings ->
Address Determination
© 2023 SAP SE or an SAP affiliate company. All rights reserved
4 of 11
2023-03-03
2578294
Check if the BP Address Type HCM001 is available. If the value does not exist, add new BP Address
Type using the Customizing Define Address Types.
Address Type: HCM001
Name: Enter any name (for example, Employee Home Address)
15. Message R1000 "Error_Time Dependency_Addresses ADVW_VALIDITY_ERROR" appears in
SLG1 log
This message is usually triggered due to wrong customizing of the path "Cross-Application
Components=>SAP Business Partner=>Business Partner=>Basic Settings=>Address Determination".
Make sure the address type XXDEFAULT is set on "Assign Transaction to Address Type".
If the above customizing is right but the issue still appears, please check with transaction SU53 that
your user has all the necessary authorizations to run the report.
In addition, it is recommended to review SAP Notes 2517507 and 2598468 .
16. Message R1279 "Business partner category 1 is not allowed for BP role ******" appears in SLG1
log
This message may appear for your custom vendor role ******. The most probable reason is that
according to your customizing in the system, that custom role is only allowed for organizations, but not
for employees. If you want to add this role to persons, you would need to tick the checkbox for person
in section "Possible Business Partner categories". To access it please refer to the following IMG path:
Cross-Application components -> SAP Business Partner -> Business Partner -> Basic Settings >Business Partner Roles -> Define BP Roles. Here mark the corresponding custom role and open the
details for the BP role categories.
17. Message R11119 "Business partner GUID is blank" appears in SLG1 log
Please find the solution to this issue described in KBA 2580964
18. Message R11245 "Error for validity periods of address usages" appears in SLG1 log
If the changes from note 2517507 are not already available in the system, apply them. Then, as
explained in the description, ensure you maintain the address type XXDEFAULT in the customizing
Assign Transaction to Address Type (view V_TB008U). The IMG path is as follows: Cross-Application
Components > SAP Business Partner > Business Partner > Basic Settings > Address Determination >
Assign Transaction to Address Type.
19. Message /SHCM/EMPLOYEE_BL107 "Vendor-BP *** of Vendor *** is not in Person Category"
appears in SLG1 log
This error message appears when the synchronization logic tries to link an employee with its existing
Business Partner which has category type 2 - Organization instead of category 1 - Person. From the
S/4HANA Employee to BP synchronization, it is only possible to handle the CP-BP link with Person
category BPs. BPs in organization category will not be processed. Also it is important to consider
following information provided by CVI framework:
- Once the BP was created in a category, this cannot be changed, see KBA 2585965.
- The reason for this organization category to be assigned would be explained in "Cause" section of
KBA 1767277.
Additionally please check note 2539457 - CVI & employee vendors in wrong BP category.
20. Message /SHCM/EMPLOYEE_BL100 "Employee ***: Two different CP linked to the same
employee(P-CP,CP-BP)." appears in SLG1 log
If the relationship P-CP-BP (employee-central person-business partner) is not consistent, this error
message is going to be raised. The system checks if the BP of the BUT000 filtering by the "PERNO" is
the same which is linked to the CP for that P in the HRP1001 table. The root cause could be an
incorrect deletion of the relationship CP-BP. In this case, the solution for such an inconsistency could
© 2023 SAP SE or an SAP affiliate company. All rights reserved
5 of 11
2023-03-03
2578294
be trying to manually restore the CP-BP linkage or even consider deleting the BP and synchronizing
the P again. (Note: the deletion of the BP is not reversible and has to be tested before). For any issue
or doubt, the correct component is CA-HR-S4.
21. How to configure the system to maintain the same number between the Business partner and
the employee.
Please find explained the procedure in this KBA: 2792166 - Same number for BP and employee.
22. Message CVI_MAPPING043 "Vendor & already exists" appears in SLG1 log.
This error message appears when there is an inconsistency in the relationship between the Vendor
and the BP. Please check the KBA 2798051 - Error "Vendor & already exists" (CVI_MAPPING043).
23. SAPSQL_DATA_LOSS Runtime Error dump received from BP synchronization.
The dump "Runtime Errors SAPSQL_DATA_LOSS - ABAP Program
CL_FITV_HR_TO_BUPA============CP" could be occur if you try to synchronize an employee with
the Infotype 0105 maintained but no existing user linked in the subtype 0001. To avoid this dump,
please check that the user linked in that infotype must exists in the transaction SU01, hence, the
maximum length of the user will be 12 characters (2796772 - HR -> BP: dump SAPSQL_DATA_LOSS
possibly occurs).
24. Message /SHCM/EMPLOYEE_BL073 "Employee &1 : There is no valid CP-P relationship
maintained." appears in SLG1 log.
This error message is being raised if the start date of the employee's hiring action is a future date. The
creation of the BP will occur once the employee is active in the system. This error message is also
raised when the CP does not exist for the PERNR (there's no P-A209-CP in the HRP1001), in this
case, if the employee was created via ALE, it's recommended to check the configuration (further
questions belong to BC-BMT-OM-ALE).
Whether the employee was created via standard replication of employees from SuccessFactors
Employee Central, or by making a direct use of the HCM module in the S/4HANA system, either by
backend functionality (transactions like PA30/PA40/etc.) or from HR Renewal (Masterdata Webdynpro
Application, Roadmap forms), please refer to KBA 3077073.
25. Message AM653 "Postal code & must have the length &" appears in SLG1 log.
This error message is being raised if the length of the postal code in the Infotype 6 (field PSTLZ) does
not match with the expected length for that country. The postal code length for each country can be
checked in the table T005, where the LAND1 corresponds to the country and the ILANDK to the length.
In the Universal Postal Union web page, you can review the legal postal code's length for each country.
26. Message R11401 "Enter a value for field Last name of business partner (person)" appears in
SLG1 log.
This error message is being raised if the information maintained for the employee does not accomplish
with the required fields customized for the BP creation, this specific error belongs to the IT0002
(Personal data), further info in this KBA: 2616415 - Error Message No. R11401 - Enter a value for field
Last name of business partner (person).
27. Message R1286 "Business Partner XXXXXXXX already exists".
The view T77S0 contains the following customizing:
- HRALX PNUMB = 3
- HRALX PSUBG = XX (any two characters)
In addition, there must be an external BP number range with the same id XX created in transaction
BUC2.
With the above customizing, a new BP will be created with the same id as the employee number.
However, if there is already a BP with that number (e.g. the BP was created before), the sync report
will trigger the error "Business Partner XXXXXXXX already exists".
The existing BP has not been created by the sync report. Otherwise, the relationship CP-BP would
© 2023 SAP SE or an SAP affiliate company. All rights reserved
6 of 11
2023-03-03
2578294
exist in table HRP1001.
There are two possible solutions to this error:
1) (Recommended) Delete the existing BP and trigger the synchronization again. The sync report will
create a new BP with the same number.
2) Create manually the relationship CP-BP in table HRP1001 via transaction PP01. Before taking this
action, you must change the customizing in table T777E to be able to modify relationship 207 in
standard transactions.
Examples (taken from KBA 2792166):
- The flag HRALX-PNUMB is 3, HRALX-PSUBG is AB, in the BUC2 the grouping AB has the AB
Number Range and it is flagged as external, and in the BUCF there is: AB - From Nº EE00000001 - To
Nº EE00099999. The BP generated for the PERNR 1234 will be EE00001234. If the BP EE00001234
was created before, the sync report will generate the error message.
- The flag HRALX-PNUMB is 3, HRALX-PSUBG is AB, in the BUC2 the grouping AB has the AB
Number Range and it is flagged as external, and in the BUCF there is: AB - From Nº 0000000001 - To
Nº 0000099999. The BP generated for the PERNR 1234 will be 0000001234. If the BP
0000001234 was created before, the sync report will generate the error message.
28. Message /SHCM/EMPLOYEE_BL074 "Employee XXXXXXXX :Infotype 0001 is not available or
has incorrect data on YYYYMMDD".
This error message can appear for the Infotype 0002 as well. The minimum infotypes required for the
BP synchronization are 0000, 0001, 0002. If any of those infotypes are not existing or the start date is
in the future, this error message will appear. The solution will be maintain properly the HR master data
of the failing employees.
29. Message AM049 "Person could not be deleted as it is still used".
During the synchronization, if the employee has an user assigned on infotype 0105 subtype 01, the
report will convert the IDADTYPE of the user from 00 to 04. It is necessary to delete and create the
user again to do it. However, if the user has any entry in some tables, like ADRVP, the user cannot be
deleted and, therefore, the above error message is generated.
The solution for fixing this error is explained in the KBA 2264162 - Person could not be deleted as it is
still used - AM049. This SAP Note contains several steps to remove all the entries from the user in the
internal tables.
30. Message AM056 "Specify a valid address use (ADDRESS_REFERENCE)"
Please refer to KBA 3100539 - AM056 "Specify a valid address use (ADDRESS_REFERENCE)"
raised during Employee BP Synchronization
31. Message AM057 "Specify a valid person use (PERSON_REFERENCE)" or MESSAGE_TYPE_X
exception with CALL_FUNCTION_REMOTE_ERROR dump
Please refer to KBA 3190812 - AM057 error or MESSAGE_TYPE_X exception with
CALL_FUNCTION_REMOTE_ERROR dump happens during Employee BP Synchronization
32. Data from the business user associated to the employee has been removed from table view
USER_ADDR.
The business user management has changed in S/4HANA. A brief summary can be found in SAP Note
2570961. One of the changes is the table view USER_ADDR can not longer be used in S/4. This view
can only display classical users but not business users. It is not possible to enhance it.
For business users, it can be used the search help "USER_ADDR" or, in exceptional cases, the CDS
view "P_USER_ADDR" (with/without privileged access).
33. Issues with BP number related to employees sent via ALE HRMD_A iDocs from another system.
You are experiencing issues related to the assigned number for a BP. The employees are sent from a
SAP HR system via HRMD_A iDocs.
© 2023 SAP SE or an SAP affiliate company. All rights reserved
7 of 11
2023-03-03
2578294
In order to successfully import the employees, it is necessary to send the Central Person and
relationship CP-P in the iDoc. If this data is not sent, the CP will not be created in the S/4HANA
system.
If you want to have the same BP number in source and target systems, it is recommended to set the
same number for BP and HR employee. The steps for setting this customizing are explained in KBA
2792166.
34. Creating employees via LSMW does not trigger synchronization so the Business Partner will
not be created.
LSMW is a tool which can be used in HCM because this module is running in compatiblity package for
S/4HANA systems. However, it is being discontinued in other modules. You can find more information
in SAP Note 2287723.
Business Partner synchronization is automatically triggered on infotype save is triggered (either in
hiring or employee modification). This solution does not have integration with LSMW or other
replication, but data will be processed in case HR infotype save is triggered.
For this reason, it is necessary to set a job for report /SHCM/RH_SYNC_BUPA_FROM_EMPL. When
the job is executed, it will pick all the employees imported via LSMW and it will generated automatically
the BP if the data is right.
Another option is modifying employees via, for example, transaction PA30 or PA40. Manual trigger in
infotypes will trigger the logic, as it is part of the flow on Save action.
Only in case of errors (may be configuration, customizing, etc...) no objects like BP are created.
Automatic sync does not write any log. Hence we recommend to schedule report
/SHCM/RH_SYNC_BUPA_FROM_EMPL or manually run (as mentioned in the installation guide )
which writes in the logs in case of errors.
35. Message R1137 "'Valid-From' date may not be greater than 'Valid-To' date" appears in SLG1 log
This error message is raised if the first action (the Hiring action) has a different MASSN than "01" if the
STAT2 is different than '3' (the first record of the employment cannot be inactive). This condition is
inside the method MAP_EMPLOYEE of the Class /SHCM/CL_EMPLOYEE_INBOUND. To create a BP
with BUP003 (Employee) role, it's needed to have at least one active employment (with the STAT2=3
in the IT0000); If the STAT2 <> 3 in all the records for the IT0000, the system will determine the Hiring
Action with the MASSN = 01.
Update Note: The functionality has improved. The end date is determined by a new logic explained in
note 3074719 - The validity end date of Employee role was not determined corrrectly.
36. Message R1477 "Number XXXXXXXX is already assigned to partner XXXXXXXXXX for ID type
HCM001"
This error message is generated when a Business Partner exists with a identification type HCM001
equal to the personnel number but it is not connected to the person number via table HRP1001. Please
note that the personnel number (object type P) must be connected to the Central Person (object type
CP) and this object, at the same time, be connected to the Business Partner (object type BP).
The inconsistency can be created by different reasons:
- The CVI conversion from ERP to S/4HANA was not done correctly: the Business Partner was created
but not linked to the vendor (LFB1-PERNR=personnel number) or to the Central Person.
- The BP was previously linked to the personnel number: A process of blocking/archiving/deleting the
BP was iniated but not done correctly so the BP is not linked the Central Person but keeps the
identificator HCM001.
- The BP could have be created internally by other reports. Please, note that in S/4HANA systems, BP
with role employee BUP003 must only be created by the official synchronization reports.
There are two possible solutions to fix this inconsistency:
- Delete the Business Partner completly. The sync report will generate a new Business Partner.
- Manually create the link between Central Person and Business Partner in table HRP1001 via
transaction PP01. Before taking this action, you must change the customizing in table T777E to be able
to modify relationship 209 in standard transactions.
37. Message R1212 "Grouping XXX does not exist"
© 2023 SAP SE or an SAP affiliate company. All rights reserved
8 of 11
2023-03-03
2578294
This error message is thrown if BUPA SYNC is OFF in tcode OOV2 (Table: T77S0). The value has to
be set to ON.
38. Message R1225 "Bank details with ID HC01 already exists"
Please check KBA 3137000 - "Bank details with ID HC01 already exists" error is raised during
employee BP synchronization
39. Several PERNRs are connected to the same CP. One PERNR is inactive while other is still
active. However, the role BUP003 shows "Expired".
The behavior of the employee synchronization report is as following:
1. During first or initial synchronization,
• Which PERNR is hired with earlier hire date, and then the minimum active at the time will be
synchronized to the BP and this BP is linked to the CP in internal table HRP1001.
• This BP will also get role BUP003 in table BUT100.
• The initial synchronization indicator will be stored in internal table BUT0ID for the employee
number and BP, according to KBA 2984659
2. In case of additional PERNRs for the CP, additional BPs are created with only vendor role but they
are not linked to the CP in internal table HRP1001. Also these additional BPs will not get role BUP003.
3. Once the relationship CP-BP is created in internal table HRP1001, it will not be removed or adjusted
as standard scenario actions. For example, in case of termination of minimum active at first sync
PERNR (point 1), the BP relationship will not be deleted or adjusted. So the BP will still get data for the
first PERNR, who are stored in internal initial synchronization indicator table BUT0ID.
This standard behavior has been discussed several times with other customers and the conclusion is
that it is still used to avoid data overrides or loss and applications might still have reference or use case
for this data (from the old PERNR). These applications can only use data from BP, not from HR, and
they still need the data from old PERNR so it is not possible to change it.
40. Huge number of change pointers are generated in table CDPOS / CDHDR due to
synchronization.
This issue happened once in every synchronization, the values in tables CDPOS/CDHDR were
updated, even then there was no data change. It results in tables CDPOS/CDHDR growing very fast.
In order to correct it, please implement the following notes:
- 3022160 - CDPOS/CDHDR Table is growing very fast.
- 3078633 - Bank data do not getting Synchronized.
- 3138168 - CDPOS missing Parameter in PERSONAL DATA comparing
- 3076227 - Business partner sync dumps
- 3258366 - Enhance report /SHCM/RH_SYNC_BUPA_EMPL_SINGLE Parameter
- 2775396 - HR-> BP: no telephone number from infotype 6 into address depending communication
- 2845842 - HR -> BP: creation or update possibly fails due to address problem
- 3109007 - Error AM 266 when updating Business Partner
41. Message HRALX00_ORG301 "HR integration is not active".
Take the following steps:
© 2023 SAP SE or an SAP affiliate company. All rights reserved
9 of 11
2023-03-03
2578294
1. Go to tcode SM30.
2. Enter view T77S0 and click on Display.
3. Search for flags HRALX HRAC and HRALX PBPON.
4 a. From S/4HANA release 1709 SP1 or after applying notes 2535438 and 2549563, you need to set
HRALX HRAC = X and HRALX PBPON = ON.
4 b. In earlier versions (before 1709 SP1), set HRALX PBPON = OFF.
42. Message /SHCM/EMPLOYEE_BL072 "The USER to assign XXXXX does not exist. Please create
the USER in SU01".
Before an user is assigned to a Business Partner employee and converted to a business user, the user
must exist as a classical user. Please create the user you want to assign in transaction SU01.
43. Business Partner cannot be archived.
In some cases, the archiving of a Business Partner will fail if there are inconsistent entries(relations) in
table HRP1001. In this case, the RHCHECKRELATIONS report should be run. Often, the BP can then
be archived.
44. How to see logs of the synchronization that is triggered during changes in HR master data
records (for example, via tcodes PA30/PA40)?
The note 3080239 - HRALX PALOG Configuration Switch allows a log to be written even for
synchronizations triggered by changes in the HR master data. The swich HRALX PALOG in view
T77S0 can be activated to log these synchronizations. It is highly recommend to active this only if it is
urgent and only temporary because it creates a massive amount of mostly uninformative Application
Logs.
See Also
2570961 - Simplification item S4TWL - Business User Management
2340095 - S4TWL - Conversion of Employees to Business Partners
Keywords
SHCM_EE_INTEGRATION BUPA_SYNC /SHCM/RH_SYNC_BUPA_EMPL_SINGLE
/SHCM/RH_SYNC_BUPA_FROM_EMPL, USER_ADDR, iDoc, ALE, LSMW, CDPOS, CDHDR
This document refers to
SAP
Note/KBA
Title
3137000
"Bank details with ID HC01 already exists" error is raised during employee BP synchronization
3132597
How to block or unblock the vendor role when the employee becomes inactive or active
3100539
AM056 "Specify a valid address use (ADDRESS_REFERENCE)" raised during Employee BP
Synchronization
2832124
How to generate a vendor role FLVN00 during synchronization employee to BP
2798051
Error "Vendor & already exists" (CVI_MAPPING043)
2792166
Same number for BP and employee
© 2023 SAP SE or an SAP affiliate company. All rights reserved
10 of 11
2023-03-03
2578294
2616415
2264162
Person could not be deleted as it is still used - AM049
3022160
CDPOS/CDHDR Table is growing very fast
2796772
HR -> BP: dump SAPSQL_DATA_LOSS possibly occurs
2570961
Simplification item S4TWL - Business User Management
2340095
S4TWL - Conversion of Employees to Business Partners
2287723
LSMW in SAP S/4HANA on-premise (S4CORE)
Terms of use | Copyright | Trademark | Legal Disclosure | Privacy
© 2023 SAP SE or an SAP affiliate company. All rights reserved
11 of 11