3790663 - How to Isolate Whether a Data Write Issue Is Caused by the OData API or Import Engine

When data is written through the OData API in SuccessFactors, two components are involved:

• The OData API layer — receives the request
• The Import Engine — validates and saves the data (the same layer used when importing data manually through the SuccessFactors UI)

The OData API and the UI Import tools (Import Employee Data, Import and Export Data) share the same underlying Import Engine to validate and persist data. This means that if a data write failure can be reproduced through a manual UI import using the same payload, the root cause is in the Import Engine or the business logic of the owning module — not in the OData API layer itself.

A failure can come from either component. Identifying which one is responsible ensures the issue is routed to the correct team from the start.

Note: Applies to integrations that write data in SuccessFactors. Not applicable to read data from SuccessFactors scenarios.

SAP SuccessFactors HCM Suite

SAP SuccessFactors Employee Central

To determine whether the failure is at the API layer or the Import Engine layer, reproduce the scenario using a manual file import:

1. Navigate to Import Employee Data (for EC entities) OR Import and Export Data (for MDF entities).
   
   
2. Download the CSV template for the relevant entity.
   • Note: Set Include Dependencies = No.
     
     
3. Using the API request payload (body) that generated the error, populate the CSV with the exact same values.
   
   
4. Import the CSV file and click Validate.
   
   
5. If no validation errors are returned, proceed by clicking Import.
   
   
6. Share the following with the support team:
   • The import result, including any validation or import messages
   • The CSV file used for the test

Conclusion

If the issue is reproducible via UI Import, it should be analyzed by the Employee Central (for EC entities) or Platform team (for MDF entities). If it is not reproducible, it falls within the Integrations team scope. 

Note: If you have already reproduced the issue via UI Import before opening an incident (for example, during your own initial troubleshooting), you do not need to repeat the test. The fact that the issue is reproducible through the UI Import tools already confirms that the failure originates in the Import Engine layer, not in the OData API layer. Please include the import result and the CSV file used in your incident, and route it to the appropriate module team as described below.

Test Result	Responsible Team	Component	Action
Issue IS reproducible via UI Import (EC entity)	Employee Central team	LOD-SF-EC	Route the incident to the EC module team. This is not an integration issue.
Issue IS reproducible via UI Import (MDF entity)	Platform team	LOD-SF-PLT	Route the incident to the Platform module team. This is not an integration issue.
Issue is NOT reproducible via UI Import	Integrations team	LOD-SF-INT	Keep the incident under LOD-SF-INT for investigation of the OData API layer.

Guide: Employee Data Imports

KBA: 3359262 - How to provide more details about OData upsert with error - OData API - SAP for Me

OData API, Import Engine, Import and Export Data, Import Employee Data, Employee Central, Metadata Framework, MDF, Generic Objects, CSV import, insert error, update error, upsert, API error, file import, validate, troubleshoot, isolate, integration, HR entities, SuccessFactors API, data not saving, data not inserting, data not updating, API call failing, API call fails, API not working, API vs UI, same error in UI and API, OData error, OData request failing, HTTP 400, bad request, PROCESSING_ERROR, payload error, request body error, employee not created, employee not updating, position not created, job information error, foundation object error, EC API, Employee Central API, HRIS sync, inbound integration, integration failing, Boomi error, CPI error, SAP Integration Suite, picklist error, business rule error, effective dating error, mandatory field error, validation error, import validation fails, import job fails, import not working, CSV template, foundation data, org structure, generic object, MDF object, compound employee, personal information, employment information, pay component, EC entity, which team to contact, wrong team, case routing , KBA , LOD-SF-INT-EC , Employee Central SFAPI & OData Entities , LOD-SF-EC-EDP , Import Employee Data (EC Core only) , LOD-SF-MDF , Metadata Framework , LOD-SF-EC-INT , Manage Pending Hires (Integration RCM/ ONB/ OBX + UI) , LOD-SF-INT , Integrations , LOD-SF-INT-ODATA , OData API Framework , How To

SAP SuccessFactors Employee Central all versions ; SAP SuccessFactors HCM Suite all versions