CLOUD PLATFORM INTEGRATION

IDOC TO SFTP SCENARIO

SAP Cloud Platform Integration provides the following technical
connectivity options in the form of Adapters:

SFTP
IDOC
LDAP
SOAP
HTTPS
Mail.

SAP CPI provides ADDON adapters:

Ariba
Odata
ODC
Success Factors
Facebook
Twitter adapter.
SAP CPI
WEB UI
Configuring IDoc in ECC system.

Tcodes
BD54
Define Logical System Name
You can provide any logical system name you deem fit.
In our case we have called the Logical System Name “CPI“
Download HCI SSL Certificate.
Go to your HCI URL, View Certificate ( from padlock ) –> Details –> Copy to File –> Select
Default Options
Save the certificate to your local desktop.
STRUST
Go to view – SSL Client SSL Client ( Anonymous )
Import your HCI SSL Certificate here.
Click on Import Certificate
Select your certificate from previous step
Click on Add to Certificate List.
(This is required to establish a SSL connection between your SAP ERP and SAP CPI
ALE settings.
SM59
we need to check the connection under HTTP Connections to External System(type G) in SM59 transaction.
create a TRFC Destination,
in the case of CPI as the communication happens using SOAP over HTTP you create a Connection Type G
Connection Type: G ( HTTP Connections to External Server)
Target Host: <HostName from the Endpoint URL copied from HCI>
Service No: 443
Path Prefix : /cxf/<Path in Address Field of IDoc Adapter>
( In our case the Idoc adapter had Orders05 and hence, /cxf/Orders05
Proxy Settings is any
LogOn & Security
Basic Authentication – Provide your HCI User & Password
Security Options,
SSL – Active
SSL Certificate – Anonym SSL Client ( Anonymous ) –
The view where the HCI SSL Certificate was loaded in previous steps in STRUST.
Perform a Test Connection.
If everything is Good,
You should get a HTTP 500 Response
WE21
Create a port in transaction WE21 which shows the target system’s RFC destination.
Create a TRFC Port. In HCI, you create a XML HTTP Port as the connection happens
using SOAP Over HTTP
Port Type : XML HTTP
RFC Destination : HTTP Destination Type G from Previous Step
Content Type – Default Setting – Text/XML
SOAP Protocol – Selected.

As HCI is expecting the IDoc as a SOAP over HTTP, do ensure that SOAP Protocol is
selected here.
This will make sure that the message that goes out from ERP is a SOAP message.
WE20
In transaction WE20, create a partner profile and mention the message type details
outbound parameters,
maintain port and IDOC details, because port describes to which system the IDOC has to
flow.
Add an outbound entry for your Logical System as per the IDoc being used.
In our case we are using ORDERS.ORDERS05 IDoc and hence the outbound entry will
contain the ORDERS.ORDERS05 details
CPI Integration Flow Configuration.

Integration Flow with No Mapping.

Sender IDoc Adapter and a Receiver SFTP Adapter
Role Based Authentication is selected.
Sender IDoc Adapter and a Receiver SFTP Adapter
sftp configuration.
The sftp server can act either as a sender or a receiver of messages.
The setup and the detailed configuration procedure differ according to the
communication direction that is being set up:
whether the sftp server is supposed to provide messages to the integration platform
or the other way round.

SSH based communication.

the cloud integration tenant needs the host key of the sftp server,
which has to be added to the known hosts file and deployed on the cloud
integration tenant in the next step.
The host key can either be downloaded from sftp server or has to be provided by the
administrator of the sftp server.
Public key authentication.
public key authentication with the sftp server, a private key has to be maintained
in the cloud integration tenant keystore. Also User/Password can be used instead,
in this case user credentials have to be deployed in the cloud integration tenant.
Recommended configuration option for secure communication is public key
authentication.
Test Your Flow

Trigger the IDoc using either your standard transaction or using We19.
The IDoc should now be sent to CPI and processed by CPI.