7

Intercepting SAP Ariba Cloud Integration Gateway messages to ECC and routing to...

 2 years ago
source link: https://blogs.sap.com/2022/05/04/intercepting-sap-ariba-cloud-integration-gateway-messages-to-ecc-and-routing-to-sap-logistics-business-network/
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
neoserver,ios ssh client
May 4, 2022 2 minute read

Intercepting SAP Ariba Cloud Integration Gateway messages to ECC and routing to SAP Logistics Business Network

Many customers have worked extensively to on-board their suppliers to the SAP Ariba Business Network to leverage the full flexibility of the Network to manage their supply chain.

With the roll out of SAP Logistics Business Network, those customers who have already performed this on-boarding may be reluctant to have to repeat the exercise to then on-board the same customers to the LBN.

For that reason, the use case arises where customers may want to intercept inbound SAP Ariba Cloud Integration Gateway messages (Specifically ASN, Component Consumption and Component Acknowledge messages) and route them to LBN on behalf of their suppliers.

I utilized SAP Cloud Integration on the Integration Suite to achieve this as part of a Proof of Concept

The first challenge was to pass through all messages from SAP Ariba Cloud Integration Gateway to the Back End SAP S/4HANA via Cloud Integration.

Since SAP Ariba Cloud Integration Gateway only configures the target host once and dynamically builds the path to the specific service, it meant that we had to pass through all messages and could not filter individual message types for pass though.

Thankfully I could leverage some of the Standard Integration Content to achieve this.

My starting point was to copy the SOAP Inbound Pass through flow:

Standard%20Flow

Standard Flow

This also required configuration of the associated Value Map to identify the Cloud Connector Virtual Host and Location.

I then added a Parallel Multicast to branch from the pass-through:

Full_flow

Full flow

For each of the three message types, a separate Consumer flow was created to handle the mapping.

To determine the correct flow, I added a Router with the following conditions:

Router%20Conditions

Router Conditions

This router relies on the docType Header value which is added as part of the xslt mapping included in the standard flow used as the foundation.

Finally, in each of the Consumer iFlows we mapped the three message types to the three LBN event as follows:

ASN maps to DeliverEvent

Component Consumption maps to ProduceEvent

Component Acknowledge maps to ReceiveEvent

In conclusion, by leveraging the standard integration content for SOAP Inbound Pass-through, we were able to simultaneously route these messages to the SAP Logistics Business Network, thereby avoiding the need to onboard these suppliers.

If this blog post was helpful, or if you have any questions related to it, please comment below and don’t forget to like the post.


report

Recommend

About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK