Hello Jindrich,
should be this method. Will check/test this.

Service consumption model - oData API Deep Create with SubParent

Hi,
thank you for your blog. It is very inspiring and it is source of the latest SAP ABAP technologi tips. For the last year I work a lot with SAP Public Cloud and RAP and there is on thing which i was not able to solve and i don't konw if there is any solution.

How can we use Service Consumption Model of oData API to do Deep Create with more then 2 levels?

For example I would like to use API SalesOrder (A2X) https://api.sap.com/api/API_SALES_ORDER_SRV/overview
to create a sales order (level 1) with items (level 2) and with item billing plan(level 3) and item text (level 3).

I know that there is the "set_deep_business_data" method in the interface "/iwbep/if_cp_request_create" but as per my knowledge and as per all blogs there can be only one child level.

So is there any solution to create following structure?

1 Sales Order Header
2 -> Item
3 -> Item billing plan
3 -> Item Text

Thanks,
Jindrich

Hello Srinivas,
thank you for your feedback. We make a backlog entry for this topic, to write an article about the communication scenarios in ABAP environment on a more schematic way with some more explanations. Focus of the article was an update for the older article.

Greetings
Björn

Communication Infrastructure

Thank for your blog posts. Quite informative and definitely are aligned with the newest in the ABAP world.

Request: The communication arrangement, the scenario, the system is all too confusing for me -- may be a blog post on that with some pictorial representation in an hierarchy fashion would be better and easier to grasp the concept. More importantly, if we can align with its legacy counterpart (like how you mentioned here SM59) - then we would really be able to connect to the thought. Else, it so happens that we cannot recall what is inside what, and end up getting confused....

Please continue enlightening us...

Thanks & Regards
Srinivas Rao.