SAP CPI - OData Receiver Adapter causes issue for auto generated key property

 


SAP Note: 3000179

Set the message Property SAP_ODataV2ExcludeAutoKey to boolean value true.



Popular posts from this blog

SAP CPI - Loop Process Call with SuccessFactor (oData V2)

Image
This example will show you how to fetch data from SuccessFactor (oData V2 Message Protocal) with a specific page size. For example, if your data has 10,000 total records and each record consists of 20 child nodes (the result size is around 10MB), you can fetch data by 500 records per request by using Loop Process Call. # My integration process consists of 1. Content Modifier " Initial Data " which I declare property "fetchData". 2. Loop Process Call " Loop Fetch Data " which calls Local Integration Process " Fetch Data From SF ". 3. Groovy Script which writes data from property "fetchData" in an attachment format. This example will focus on step 2 - Loop Process Call & Local Integration Process. # Local Integration Process "Fetch Data from SF".  How does it work? 1. Use Request Reply to call SuccessFactor to get data 500 records per request. 2. Use Groovy Script to get some fields and return in XML format. 3. Use XML to CS...
Read more

SAP Cloud Platform Integration - Splitter

Image
  This example will show you how to use General Splitter to divide a big XML message into several small messages. The main process we need to focus on is the local integration process, "Split XML", which has a General Splitter inside and ends with Gather to combine a result of each split message (after the process) together. # General Splitter 1.  Expression Type: I use XPath  because the results from the SuccessFactor are an XML. 2. XPath Expression: XPath of the node that marks each split the message (Including root node) 3. Grouping: The number of records in the 1 split message 4. Streaming: Enable this if you want to start splitting before the entire big message is loaded into memory. The system will first divide the message into chunks and starts splitting the chunks into split messages. This is only relevant if the splitter is the first step after the step that fetches data – otherwise, the content would have already loaded in memory. # Gather After you proces...
Read more

SAP CPI: Recover artifact in SAP CPI (Case Delete)

Image
Reference from:  Recover package in SAP CPI : Deleted by Mistake 1) Go to Manage Integration Content (Monitor -> Integrations and APIs -> Manage Integration Content)  2)Select the iflow that you have deleted or iflow you want to recover 3) On the right corner next to restart, you have drop down. select download 4) Jar file gets downloaded and you can upload the same Jar file in the Design       Design -> Intergrations and APIs -> Select your Package -> Add New API -> 
Read more