This blog post will explain how you can model your iFlow to insert and update data in your Custom Business Object. As a prerequisite you should read blog post https://blogs.sap.com/2017/05/12/usage-of-odata-service-of-custom-business-object/.
Overall iFlow
The iFlow consists of 8 steps for mass data coming in through a SOAP service and mapping to the OData service of a custom business object (CBO). Each step is explained in detail.
The HTTP session handling is set to “On Integration Flow” to ensure that the same session is used for all calls to SAP Hybris Marketing instead of creating multiple sessions. This increases performance:
In this example the payload of an incoming SOAP Service looks like this: 6 EXTERNAL Max Mustermann 7 EXTERNAL Ellen Musterfrau 8 EXTERNAL John Doe
Step 1: Iterating Splitter to package mass data into chunks of 1000
In order to not overload the CBO backend system the data is handled in chunks of 1000. An iterating splitter is used for that purpose. The incoming payload is split at the token :
After the split the payload looks like this: 6 EXTERNAL Max Mustermann 7 EXTERNAL Ellen Musterfrau 8 EXTERNAL John Doe
Step 2: Process Call to Local Integration Process “Enrich SAP_UUID”
To update or delete an entry, the SAP_UUID as technical key is needed. Therefore for each entry the SAP_UUID is enriched in a local integration process, if the entry already exists in the CBO.
Step 3: Iterating Splitter to handle each entry in a seperate call
Currently CPI does not support batch processing for OData GET calls. Therefore each entry must be handled seperatly. But they can be processed in parallel. The splitting is again done at the Token but this time without grouping:
Step 4: Content Modifier to save the semantic key in properties
The semantic keys of the OData service of the CBO are ContactId and IdOrigin. In the Content Modifier the values are saved in properties for usage in step 5:
Step 5: Content Enricher to read the technical key SAP_UUID
A Get request is made to the SAP Hybris Marketing system to get the technical key SAP_UUID. The properties ContactId and IdOrigin are given over in the filter expression. As the content enricher needs a matching field from the existing payload and from the receiving payload, also the ContactID is requested:
In the Content Enricher properties the result is then mapped to the current payload:
If a SAP_UUID is returned by SAP Hybris Marketing, the payload looks as follows after the content enrichment: 7 00163e35-616b-1ed7-b5b9-662f3d264ba0 7 EXTERNAL Ellen Musterfrau
If no SAP_UUID is returned, the payload looks like this: 8 EXTERNAL John Doe
Step 6: Mapping After Enrichment
As the payload looks different after the content enrichment for new and changed objects, a mapping is introduced that maps both cases to the same structure. As result structure already the OData structure of the CBO is used. The fields ContactID, IDOrigin, Field1 and Field 2 can directly be assigned:
For the field SAP_UUID a complex expression is build. It is checked if the tag SAP_UUID exists in the incoming payload. In this case the SAP_UUID is taken over. In case the tag does not exist, an empty constant is written to the target SAP_UUID tag:
Step 7: Gathering of SAP_UUID Enrichment Calls
In the last step of the local integration process all calls are gathered and enhanced by an overall tag . The overall tag is needed by CPI for further XML processing.
After the gathering the payload looks like this: 00163e0c-0f31-1ee7-8eae-19ed448a1944 6 EXTERNAL Max Mustermann 00163e35-616b-1ed7-b5b9-662f3d264ba0 7 EXTERNAL Ellen Musterfrau 8 EXTERNAL John Doe
Step 8: Map request chunk to OData Batch Processing
The last step of the whole integration flow maps a chunk of 1000 to batch processing of the CBO OData service. The tag is mapped to the tag . The target tag gets an empty constant assigned. The tag is mapped to the tag . The target tags and have a complex expression based if the entry needs to be created or updated. The target tag is not needed and therefore disabled. The target tags and get an empty constant. The target tag has a complex expression. The fields ContactID, IDOrigin, Field1 and Field2 are mapped directly from source to target.
The target tag can either be POST for a new entry or PUT for a changed entry. If the source tag is empty (SAP_UUID equals string ”) then the constant POST is assigned to tag . Else the constant PUT is assigned:
The target tag is only needed for changed entries. Therefore the complex expression is as follows: If the source tag is empty (SAP_UUID equals string ”), revise the result (Not). Only if the revised result is true, create the tag . The creation of the tag is created by concatenation of constant value YY1_HCI_ID_ID_ORIGIN(guid’ with source SAP_UUID and next concatenation to constant value ‘):
The complex expression for the target tag is similar to the target tag . Only if the source SAP_UUID is filled the target tag is created:
The payload now looks as follows: PUT YY1_HCI_ID_ID_ORIGIN(guid’00163e0c-0f31-1ee7-8eae-19ed448a1944’) 00163e0c-0f31-1ee7-8eae-19ed448a1944 6 EXTERNAL Max Mustermann PUT YY1_HCI_ID_ID_ORIGIN(guid’00163e35-616b-1ed7-b5b9-662f3d264ba0’) 00163e35-616b-1ed7-b5b9-662f3d264ba0 7 EXTERNAL Ellen Musterfrau POST 8 EXTERNAL John Doe
Batch requests to an OData service are always send as a POST request. Therefore the Receiver Channel needs to be setup like that:
The timeout is configured with 5 minutes as this is the normal runtime in SAP Hybris Marketing system.
http://bit.ly/2Cpbpm1 #SAP #SAPCloud #AI
