SAP Knowledge Base Article - Preview

3370396 - SAP Cloud Integration for data services - OData adapter nested or deep inserts - not supported

Symptom

You are trying to build integrations with the IBP OData API endpoint PLANNING_DATA_API_SRV and inside your body payload, you have nested entities (also called as navigation or deep insert records) according to this fictional sample:

POST

https://myXXXX-api.scmibp1.ondemand.com/sap/opu/odata/IBP/PLANNING_DATA_API_SRV/ABCTrans

body payload in JSON format:

{
"Transactionid": "11111",
"AggregationLevelFieldsString": "LOCID,PRDID,PERIODID0_TSTAMP,INDEPENDENTDEMAND",
"VersionID": "",
"DoCommit": true,
"ScenarioID": "",
"NavJD4UD": [
   {
       "LOCID": "AB01",
        "PRDID": "XX2121",
        "PERIODID0_TSTAMP": "2023-01-01T00:00:00",
        "INDEPENDENTDEMAND": "99"
    }
]
}


Read more...

Environment

  • SAP Cloud integrations for data services - OData adapter
  • SAP Data Services - OData adapter

Product

SAP Cloud Integration for data services all versions

Keywords

CI-DS, CIDS, CPI-DS, OData, deep insert, missing feature, navigations, POST, upsert, update, create, API , KBA , LOD-HCI-DS-AGNT , On-Premise Agent, Connectivity, Task Run errors , LOD-HCI-DS , HANA Cloud Integration for Data Services , EIM-DS-EXE , Job Execution , 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.