Symptom
With the 2H 2023 release a new header has been added to the response payload of batch API calls in OData API:
"successfactors-internal-apiresource"
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
Environment
- SAP SuccessFactors HCM Suite
- OData API
Reproducing the Issue
- Perform a batch call in OData API.
- Response will look as below (new header in bold):
--batch_151f0fa4-563f-4220-8345-e4aea3b404df
Content-Type: multipart/mixed; boundary=changeset_24c3694a-3747-486f-9660-c42634b9f1c0--changeset_24c3694a-3747-486f-9660-c42634b9f1c0
Content-Type: application/http
Content-Transfer-Encoding: binaryHTTP/1.1 200 OK
Content-Type: application/json;charset=utf-8
DataServiceVersion: 1.0
successfactors-internal-apiresource: User
successfactors-message: X-SF-Correlation-Id, successfactors-sourcetype are missing in request headers
Content-Length: 157
Resolution
This header will show what entity is receiving the data.
This new value will not impact your current API calls and no actions need to be made on your side, unless you have custom codes in your company that consumes the headers from such calls. If so, please evaluate your code and adapt it if needed.
See Also
Keywords
successfactors-internal-apiresource, header, value, batch, upsert, 2h 2023, b2311, API-29394, API-27897, API Insights, RFC standards , KBA , LOD-SF-INT-ODATA , OData API Framework , Product Enhancement