Symptom
You are configuring an integration to hire employees and as part of this integration you are making use of the generateNextPersonID to get an available ID to complete the hire process.
In parallel you also have in your EC implementation a business rule implemented to define the sequence of your employees which is configured under Hire/Rehire Configuration with a business rule consuming a sequence object.
During your tests you have noticed that when hiring an employee via API it will not update the sequence number object, which means that you may fall into a scenario where hiring an employee through UI may use an ID that is already in use by another employee that was hired during INT execution.
Read more...
Environment
- In your SFSF instance you must be defining the employee IDs using business rule + sequence number in Hire/Rehire Configuration
- In your integration you are calling generateNextPersonID when hiring an employee
Product
Keywords
KBA , LOD-SF-INT-ODATA , OData API Framework , LOD-SF-EC-HIR , Hire & Rehire Wizards , Product Enhancement
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.