SAP Knowledge Base Article - Public

2643090 - Behavior of API upsert request for EmpPayCompNonRecurring entity

Symptom

 Behavior of API Upsert request for empPayCompNonRecurring entity

Environment

Successfactors API (SFAPI/OData API)

Reproducing the Issue

NA

Cause

NA

Resolution

Behavior of upsert request for API entity empPayCompNonRecurring:

  • 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.
  • This would result in new value for "createdOn", "createdBy" , "lastModifiedOn" and "lastModifiedBy" fields too.
  • 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":

datamodel

NOTE: This screenshot has been taken from internal system.

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

See Also

 empPayCompNonRecurring

Keywords

KBA , LOD-SF-INT-API , SF API & Adhoc API Framework , LOD-SF-INT-ODATA , OData API Framework , How To

Product

SAP SuccessFactors HCM Core all versions