Sending data from SAP Gateway to Middleware using ODATA

[former_member500090]

Hi ,

We have a Central Hub Deployment of Gateway .

We need to use REST based services for transferring data .

Our architecture looks like below.

SAP ECC-> SAP Gateway - > Middleware hosted on Microsoft Azure - > Magento (hosted on Microsoft Azure)

For eg, when a customer gets created in Magento, corresponding odata service is called, and the details are saved in SAP.

This happens normally like any OData service.

We have a requirement where in if we make any changes in SAP, the same has to be passed to Magento. A batch job runs every 1 hour or so to check what all customer data have been changed and the data needs to be pushed to SAP Gateway which inturn needs to push data to Middleware.

How can we achieve this scenario?

Thanks,

Archana.

[architectSAP · Accepted solution]

Hello Archana,

I am not sure why you would want to push your changed ECC data through Gateway to your middleware. I would think that your flow could look like this where your batch job in ECC passes any customer changes on to your middleware that in turn calls a respective API in your Magento system: SAP ECC-> Middleware hosted on Microsoft Azure - > Magento (hosted on Microsoft Azure).

Best regards

Frank

[weberpat · Accepted solution]

Agree with Frank. NWGW is supposed to expose data sources on your SAP backend as ODATA services, not push data from your backend to satellite systems. For your outbound scenario, you will want to deliver the data straight to your middleware system, e.g. as an IDoc.

[former_member500090 · Accepted solution]

Hi Patrick ,

Our GW system is connected to multiple ERP systems. Hence any communication that happens with non-sap system will happen through gateway.

From the below link,

https://feedback.azure.com/forums/287593-logic-apps/suggestions/8004945-receiving-idocs-from-sap

I understand that the Logic Apps will not be able to receive IDOCS from SAP.

Are there any possibility to send asynchronous data from SAP ECC to Middleware via Gateway?

Thanks,

Archana.

[weberpat · Accepted solution]

Hi Archana,

Again, Gateway is a platform that is meant to expose services, not send messages. When I was talking IDocs, I was thinking of them as a container and did not mean to imply that you would need to use the classic RFC transport layer that is often automatically associated with IDocs. You could just as well send them in XML format to an HTTP endpoint, with or without SOAP envelope. I'm not very familiar with Azure but i'm fairly certain that this is a type of integration they would be able to support.

Regards,
Patrick

[former_member500090 · Accepted solution]

Hi Patrick,

Thanks for replying!

Can you please share the links to understand how this works?

Thanks,

Archana.

[weberpat · Accepted solution]

Hi Archana,

If you know how IDocs work in general, there is very little to learn to make this happen. Instead of using a TRFC port and a Type 3 RFC Destination, you use an XML HTTP port and a type G RFC connection (HTTP to external server). The settings should be quite obvious if you have ever worked with HTTP.

Regards,
Patrick