• • The Start Timer schedules the IFlow execution and can be configured.

• • The IFlow should be scheduled during off-business hours

• • The IFlow should not run more frequently than every minute.

Data Store Select

Select Contacts

• • Data Store Name: Define the data store name from where the failed messages are stored.

• • When the message is processed successfully, the data store entry is deleted.

• • Messages are processed one-by-one

Splitter

Split single message

• • The Data Store Select is configured to only collect one entry from the data store with each run.

• • The splitter is added to ensure that only one message is processed at a time.

• • Processing each data store entry individually makes it easier to define what message failed and succeeded.

• • In case of multiple errors, the select operation can be changed to collect multiple messages. Adjustments in the error process might be required if multiple entries are selected.

• • The select operation adds additional elements to the called message. The filter step filters the selected message to match the original message
    Filter condition: //n0:BusinessPartnerSUITEBulkReplicateRequest

• • Header: message_reprocessing is sent with value “true” (fix value).

• • This is used in the Business Partner replication to avoid storing the message again in the data store, creating duplicate entries

• • Exchange Property: inboundMessage sets the new inbound message for the second reprocessing IFlow in case the message fails again.

Exception process

Reset message body

• • This step defines the new message body for the second reprocessing IFlow

Data Store Write

Write to Data Review Data Store

• • Data Store Name
    Define the data store name for the second reprocessing IFlow

Sender: S4OnPrem

Type: SOAP

• • SOAP Sender is configured

• • Address: /SalesOrderBulkReplication_Out_OnPrem

• • Processing Settings: Robust

• • Authorization: User Role

• • User Role: ESBMessaging.send
    The role needs to be assigned in SAP BTP Cockpit to the communication user that is used for authentication.

Content Modifier

define properties and headers

• • Message headers and properties are defined.

• • Exchange Properties:

• • filename: Mandatory. Defines the filename of the imported sales data

• • adminEmail; The CPI Admin Email is required when Mail notifications are enabled.

• • MailNotification: Email notifications can be enabled but require configuring an CPI Admin Email and A Broadcast event with Email template in Emarsys.

Groovy Script

Log Inbound Payload

• • Logs the inbound message body.

• • Message logs need to be enabled by setting the exchange property “Enable Logging” to value “true”.

• • Only enable the message log if needed. The message body is stored as an attachment in the Message Processing Log (MPL) and the storage size for attachments is limited on SAP Cloud Integration.

• • For testing the integration, it is recommended to log level “trace”. The trace log level can be enabled for 10 minutes and traces the complete message processing, including message headers and properties.

General Splitter

XML Splitter

• • The XML Splitter splits the inbound message payload into single messages, so the message mapping can validate each Sales Order Business Document.

• • It is not required to process the sales order individually. Sales Orders can be processed in batches.

• • In this example, the Sales Order are processed individually. The Mapping for business documents requires the Sales Order BD to be processed individually, otherwise the complex BD structure can lead incorrect message transformations.

Message Mapping

Emarsys Contact Mapping

XSLT Mapping

Remove ítems

• • The XSLT Mapping removes Sales Order items that are not to be imported into Emarsys.

• • The conditions for importing the Sales Order are defined in the IFlow description above and implemented in an XSLT script

• • All Sales Order items with Item Status “INPROCESSING” are removed.

• • All Sales Order items with Overall Status “COMPLETED” and Item Status “CANCELLED” are removed.

• • All Sales Order items with Overall Status “CANCELLED” and Item Status “COMPLETED” are removed.

• • Other options are possible to solve this.

• • The gather step collects the Split items and combines them into one message.

Router

Check empty

• • Branch 1: empty
    Default Branch, Ends message processing

• • Branch 2: not empty
    Expression Type: XML
    Condition: boolean(//salesorder)
    When at least one sales order exist after mapping the message for further processed.

• • The Gather step filters for only the relevant items.

• • The Gather step removed the partent nodes added from the previous steps

• • XPath Expression: //salesorder

• • Value Type: Nodelist

Content Modifier

Add root

• • The Content Modifier add a root element to the XML.

• • The root element is required in the XML to further processing and transformation.

• • Converts the XML body to CSV

• • Path to Source Element in XSD: /salesorders/salesorder

• • Include Field Name as Headers: enabled

• • Include Parent Element: disabled

• • Include Attribute Values: disabled

Groovy Script

Log Outbound Payload

• • See groovy Script “Log Inbound Payload”

Content Modifier

Emarsys Sales API

• • Defines the mandatory headers and properties.

• • Headers are predefined and should not be changed.

• • merchantId: Mandatory. The Merchant ID can be retrieved from Emarsys in the Predict data sources.

• • bearerToken: The bearer token it stores in a secure parameter on CPI to not have the plain text exposed in the frontend. The property refers to the name of the created security parameter on SAP CPI.

Groovy Script

Set Authorization

• • The custom function gets the bearer token stored in the security parameter and generates the authorization header.

HTTP Receiver

Submit Sales Data

• • The HTTP Receiver connects to the Emarsys Sales API.

• • All values except the Merchant ID and Timeout are preconfigured.

• • The Merchant ID and Timeout values are maintained as an externalized property.

• • Branch 1: HTTPCodeOK

• • Expression Type: non-XML

• • Condition: ${property.responseStatus} = ‘OK’

• • Branch 2: HTTPCodeNotOK
    Default branch, ends processing.

Groovy Script

logHTTPError

• • Logs and writes message body as Message Processing Log attachment

• • Called custom function: logHTTPError

Local Sub-process

Error Handling

• • Default error handling: log the error and decide if an Email is sent as a notification.

• • The error handing is same for Business Partner and Sales Order replication

Groovy Script

Log Error

• • Saves the message payload as attachment to the Message Processing Log.

• • Branch 1: no reprocessing (default)

• • Branch 2: Reprocessing
    ${property.enableReprocessing} = ‘true’ and ${header.message_reprocessing} != ‘true’

• • The message body is reset to the inbound and stored in the SAP Cloud Integration data store.

• • The data store write operation is defined to store the failed message.
    Entry visibility is to be set to “Global”

• • Branch 1: Email, Send Email Notification

• • Branch 2: No Email, No Email Notification

• • Condition expression: ${property.MailNotification} = ‘true’

Groovy Script

Define tmn host

• • The error notification includes a link to the CPI tenant’s Monitoring overview.

• • The tenant management node is defined in this step.

• • Called function: defineTmnUrl

Content Modifier

Define external event

• • The broadcast event request body is defined.

• • Available personalization attributes:

• • {{event.adminEmail}}
    Email of the defined CPI Admin in the IFlow configuration

• • {{event.timestamp}}
    Error Timestamp

• • {{event.CPIHost}}

• • SAP CPI Tenant Management Host

• • {{event.CPIPath}}
    SAP CPI Enpoint path

• • {{event.caughtException}}

• • Caught exception message

• • {{event.expectionMessage}}

• • Exception message

• • {{event.messageProcessingLogID }}
    SAP CPI MPL ID, this is used to search the error message in the Message Processing Log

• • The parameters required for the email notification should be defined depending on the relevant use cases.

Content Modifier

delete uri header

• • Deletes CamelHttpUri header to prevent overwriting the target host url

• • Delete: $name=CamelHttpUri

• • Creates Authentication header

• • Call function: XWSSEHeader

Request-Reply

Send error notification

• • • • Configure Broadcast Event API request
    • • Address: https://api.emarsys.net/api/v2/email/
    • • Authentication: none (Authentication is set by the “Create WSSE Header” Script)
    • • Request Headers: X-WSSE (allowed header)
    • • Response Headers: * (allow all response headers)

Complete the Email settings and select “Broadcast Event” in the Trigger Settings

Note the Broadcast Event ID