2643090 - Behavior of API upsert request for EmpPayCompNonRecurring entity - SuccessFactors API (SFAPI/OData)

Behavior of API Upsert request for empPayCompNonRecurring entity

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental." 

SuccessFactors API (SFAPI/OData API)

Behavior of upsert request for API entity empPayCompNonRecurring:

1. If no sequenceNumber field value is being sent with API upsert request for existing record, data from DB will be deleted completely and new record will get created with the field values sent in upsert request.
2. This would result in new value for "createdOn", "createdBy" , "lastModifiedOn" and "lastModifiedBy" fields too.
3. If upsert request is being sent for existing record and you do not want existing data to be deleted, make sure you have configured succession data model for field "sequenceNumber" as shown below i.e allow-import="true":

• Another option would be: Under Admin Center->Manage Business configuration->payComponentNonRecurring->Sequence-Number->Detail and set "Allow Import" field value as "Yes". 

empPayCompNonRecurring

sequenceNumber, Sequence-Number, empPayCompNonRecurring, Behavior of API upsert request for EmpPayCompNonRecurring entity - SuccessFactors API (SFAPI/OData) , KBA , LOD-SF-INT-ODATA , OData API Framework , LOD-SF-INT , Integrations , LOD-SF-INT-API , API & Adhoc API Framework , How To