When customers move from on-premise SAP system to SAP Cloud they are hesitant to either continue their integrations from on-premise or move all of them to cloud. One of the biggest reason for this is that they have already invested a lot in their integrations from on-premise systems via on-premise SAP middleware i.e. SAP PI.
Few customers decide to go with SAP PI as their first choice for all integrations from ECP. Few decide to go with SAP Cloud Platform Integration (CPI) and few decide to use both.
Scenario 1 – Customer doesn’t want to use SAP CPI :
All inbound integrations via SAP PI will send data to ECP as well as write the file on customer internal network drive which is in customer’s landscape.
SAP PI can send data in idoc to ECP system.
In the above scenario you need to create a function module in ECP and attach it to your idoc type.
Scenario 2 –
All inbound integrations via SAP PI will send data to ECP as well as write the file on customer SFTP or their internal network drive which is in customer’s landscape.
SAP PI can send data via SOAP to ECP system
Scenario 3 – Customer wants to use SAP CPI for all vendor interactions but wants to have the data as a file in their internal network drive.
SAP CPI interacts with all vendors and sends data to ECP via SOAP. SAP CPI sends data to SAP PI via SOAP and SAP PI will write the data in file format in customer internal network drive because SAP CPI can’t reach there because there’s no standard adaptor given by SAP for that.
Scenario 4 – Customer wants to use one middleware i.e. SAP CPI.
SAP CPI will interact with all vendors and archives the file in Customer SFTP via SFTP adaptor.
Note: If the file needs to be archived on the Customer’s on-premise SFTP server then SAP CPI can also do that. There’s a solution which SAP has given in Nov 2018 release. Refer this blog for more information.
Here’s the link of my blog on Outbound Integration approach from ECP