Hi,We are struggling to integrate a standard OData API (Condition Record for Pricing in Sales - API_SLSPRICINGCONDITIONRECORD_SRV) residing on an S/4HANA private cloud system. Both an OData and REST adapter are being used, but both throw an error.I l...
All,I have an additional requirement in a SAP PO REST receiver adapter. 2 parameters must be provided in the headerContent-LengthHostFor the host, I can provide a fixed value. But what about the Content-Length. That one is calculated within Postman.A...
In previous blogs, I talked about the context, use cases and how the Edge Integration Cell, EIC in short, looks and feels. This blog will bring insights in the setup. It is not a manual, obviously. But it provides tips and tricks to give you a better...
In my previous blog, I introduced the Edge Integration Cell, EIC in short, explaining what it is about and what the typical use cases are. It was written from a deploy & monitor perspective. This blog is to give you an idea how it looks like and what...
For a long time, SAP talked about the Neuron Edge or the Hybrid Integration Runtime. But when you read this, SAP officially launched the brand new Edge Integration Cell, EIC in short. Just today!
Let me introduce you to SAP’s next-generation, lightw...
SOLUTION found: the problem was in my mapping. I pushed all in 1 block. Different messages were put in A_SlsPrcgConditionRecordType.Now, I changed the mapping and individual messages are put in batchChangeSetPart. That was the key to success.
I assume JSON is the only way forward. The adapter should translate from XML.And batch processing is the only way to go, to my opinion. We need to be able to process multiple messages, in 1 big source message, in 1 shot.If not, we face issues with th...
I assume, yes.
Unmodified standard content means a standard integration package in the Integration Suite.
Now, you are talking about flat files. That is something different.
