SAP PO OData adapter in $batch mode using POST operation(simple structure)
You might be very familiar with consuming OData service by using REST receiver adapter. However SAP has provided a native OData adapter to consume OData service as well.
In the content below, you will learn some knowledge on how to update information in backend by using OData adapter under the $batch mode.
There are some blogs post on using SAP PI OData adapter to make complex query to backend. Whereas in this blog post, I will describe how $batch has been used in OData adapter configuration under POST operation. here are the steps.
- Create a OData service as below from table SFLIGHT
remember to redefine these methods so that it can support $batch
In the above blogs, the author has described a way to get schema, resource path etc. by using Model Operation for query.
I will describe the detail steps on this.
Then create the ESR contents based on the xsd generated.
However, I found the Model Operation in NWDS has a defect dealing with an entity type having deep structure which prevents xsd from being generated.
I will write the way dealing with deep structure using $batch in another blog.
2. Configuration OData Receiver Channel
The entity set of the OData created in the backend by me is SflightSet
Note: this additional setting is to avoid an ‘utf-8’ string generated to the Accept in the request message, which cannot be accepted by SAP gateway service
3. Unit Test
Check entries in Table SFLIGHT
The values in field PRICE are 16 and 18.82 here
Make change to price field in the request message and send it.
Response message received by POSTMAN
Entries updated after the batch POST
goto tx code /IWFND/TRACES, select the communication user, we can find that when OData Adapter makes one call to backend by using POST, the odata service has been called 4 times in the backend.
The GET operation is to retrieve CSRF Token.
Therefore, one of the benefit to use OData Adapter to create/change data is that you do not need to switch off csrf token as for REST adapter.
Hopefully you will find the blog is useful.
Hi Stephen ,
I have the same requirement .I have gone thru the above description. I have some question on this.
1.How are you handling the CSRF token in the ODATA receiver adapter .
2. IF SAP PO want to connect the Odata service in the Backend via Apigee gateway then is there any possibility to add the static toke in the http header .
Thanks in advance !
for item 1:
OData adapter will handle the csrf token automamtically. pleae check the record above. the adater will trigger a GET operation at first to get the csrf token.
for item 2:
i have only tested the odata adapter connecting with ABAP backend. if you were trying to connect a 3rd party system, please raise a ticket to SAP service. lol. I assume at least REST receiver adapter will fulfill the requirement.
I am using the ContentTypeEncoding=none, as suggested, I'm still getting errors in the ODATA adapter and I am also trying the REST adapter, it's not working as well.
REST adapter is working when I am sending 1 item (not using the "Enable Batch Processing").
"this additional setting is to avoid an ‘utf-8’ string generated to the Accept in the request message"
Do you know what is the Encoding SAP Gateway is accepting ? And the header parameters expects to receive ?
Thanks in advance !
not sure what error you encountered.
check if this one helpfully it works for you.
2575582 - OData/SuccessFactors adapters: java.net.URISyntaxException: Illegal character in query
Hi Stephen ,
Thanks a lot for your response on the csrf token .
Could you please provide some feedback on the below 2 points.
Thanks for your help in advance !
you do not have to have a CPI account. whereas you need to install an eclipse with the HCI plugins to generate the OData Adapter's query string. hope it helps you. 🙂