SAP SFTP integration with SFTPPlus MFT

SFTPPlus MFT is managed file transfer software that connects SAP ERP to partners that exchange files over SFTP or FTPS. SFTP stands for SSH File Transfer Protocol and protects files while they travel between systems. SFTPPlus runs on your own Windows or Linux system, receives or collects partner files, and delivers them to a folder your SAP application can access. A configured XML SOAP hook can then notify a compatible SAP endpoint that the file is ready to process.

For SAP systems with an existing file import or export interface, this keeps SFTP connections, authentication, retries, and transfer logs outside SAP. Your administrators configure the file transfers through the SFTPPlus Web Manager or INI files, without commissioning custom SAP SFTP code. Your SAP team retains control of the business rules for importing and producing documents.

For SAP Concur imports and extracts, see SAP Concur SFTP and PGP transfers, including SSH key authentication, UTF-8 preparation, and file encryption.

Receive partner files into SAP ​

For incoming orders, invoices, or other business files:

1. A partner connects to the SFTPPlus SFTP server using its existing SFTP client and an account restricted to that partner's folder.
2. SFTPPlus receives the complete file and makes it available in an agreed import folder, either directly or through a configured file transfer or dispatch action.
3. Once the file is ready in the folder SAP can read, an HTTP event handler sends an XML SOAP notification to your SAP endpoint.
4. The SAP workflow reads the file, validates its contents, and performs the business import.

If your partner already operates an SFTP server, SFTPPlus can instead connect to it and download files on a schedule. There is no need to host an incoming SFTP service for that workflow. Partner accounts and SSH keys are managed in the file transfer layer, without creating SAP users for external partners.

Send SAP files to an SFTP server ​

SAP writes its reports or export files to an agreed folder. SFTPPlus monitors that folder and uploads completed files to the partner's SFTP server, with configured retries and email notifications for delivery failures or success. SAP does not need to implement the SFTP connection.

Alternatively, publish the exports in a partner's SFTPPlus folder and let that partner connect to download them. Use separate incoming and outgoing folders, and agree how a producing application marks a file as complete before a transfer starts. This avoids sending a file while SAP is still writing it.

Trigger SAP processing with XML SOAP hooks ​

The HTTP webhook handler can send transfer events as JSON, XML, or SOAP XML. Set http_content_type = soap to send the standard SFTPPlus event envelope. The hook carries event metadata, such as a file path and transfer details; the file contents travel through the separate file transfer workflow.

An SAP administrator must provide a reachable endpoint, the accepted message format, authentication requirements, and a way for SAP to read the delivered file. The standard SFTPPlus SOAP envelope is an event notification, not an automatically generated call to any SAP business function. If your service expects a different message, configure a custom body template and the required headers, or adapt the receiving integration. Use HTTPS and certificate validation for the endpoint connection.

Trigger the hook from the success event for the step that places the complete file in SAP's import folder. When a separate transfer moves an uploaded file there, an upload notification alone is too early. Filter the handler to the relevant transfer or service, and configure response checks, retries, and failure alerts. The receiving workflow should recognise a repeated notification so a retry does not import the same order twice.

See the HTTP handler settings and payload and response reference for configuration details. File delivery, successful notification, and successful SAP import are separate results to check during evaluation.

Licence options ​

SFTPPlus MFT offers perpetual licences and annual or multi-year subscriptions. Choose the licence roles by which system initiates the connection, rather than by whether the business file is incoming or outgoing.

See licensing options and request a quote that covers your installation, support needs, and any non-production environments. Include hosting and any implementation services when you discuss the full project scope. Ask us to confirm the roles for your complete workflow, including staging transfers and high availability.

Compare with an SAP SFTP adapter project ​

If SAP already reads and writes files, SFTPPlus can handle the partner connections without adding an SAP integration platform solely for SFTP. Reusing an existing import workflow or compatible SOAP endpoint can also avoid commissioning SAP-specific file transfer development or additional consultancy for that part of the project.

Compare the complete project scope: software, hosting, support, configuration, and any work still needed on the SAP business interface. If you already use SAP Integration Suite, its SFTP sender adapter can read files from an SFTP server and may suit your existing integration flows. SFTPPlus can provide that SFTP server as well. The right approach depends on the SAP services you already license and the integration work you need.

SAP FTP and FTPS integration ​

For partners using FTP, the same folder and notification workflows apply. Use FTPS to encrypt FTP connections with TLS, or SFTP for transfers over SSH. Plain FTP does not encrypt credentials or file contents. FTPS and SFTP are different protocols, so agree which one the partner supports before configuring the connection.

SFTPPlus can accept FTPS uploads, collect files from a partner's FTPS server, or make SAP exports available for partners to download. For FTPS, configure certificate trust and the passive data port range as well as the control connection. If the server is behind a firewall or load balancer, check the advertised passive address and data ports using the FTPS network guide. These network settings are managed in SFTPPlus, separately from the SAP import workflow.

EDI files and SAP business processing ​

SFTPPlus MFT can transfer Electronic Data Interchange (EDI) orders, invoices, and shipping notices between partners and an SAP-connected import folder. SAP or your EDI application remains responsible for interpreting, validating, and mapping those documents. Moving an EDI file does not by itself convert it to an SAP business document or confirm that SAP accepted the order.

For partners that require signed messages and delivery receipts, SFTPPlus also supports AS2 for EDI file transfers. Use the transport required by each partner while keeping the document processing in your existing business application.

Check your SAP environment ​

This integration uses file access and HTTP interfaces rather than an add-on installed inside SAP. For SAP ECC or S/4HANA, first confirm the import/export interface and endpoint available in your particular deployment. A cloud SAP application may require a supported API or integration service instead of access to a shared filesystem. SFTPPlus is software you operate on your infrastructure, including cloud virtual machines; it is not a hosted SAP integration service.

Where the file interface and compatible notification endpoint already exist, administrators can configure the transfer workflow without writing SAP code. If they do not exist, your SAP team still needs to provide the application integration. You can also use an existing scheduled SAP import when no notification endpoint is required.

Try one complete SAP transfer ​

Use the supported trial to test one partner and one transfer direction with non-sensitive sample data.

1. Agree the source, destination, file format, completion signal, and SAP import or export workflow with your SAP administrator.
2. Install SFTPPlus MFT on a supported platform and configure the required SFTP service or automated transfer.
3. Send a sample file. Check its contents at the destination and the successful delivery event in the SFTPPlus log.
4. If using SOAP, enable the notification for the correct completion event and verify that SAP processes the file. Check the SAP import result as well as the HTTP response.
5. Test an interrupted connection, an unavailable endpoint, and a repeated filename or notification. Confirm alerts, retries, duplicate handling, and source retention before using production data.

Request your supported trial using the form below. When our team follows up, tell us your SAP deployment, transfer direction, partner protocol, and whether an import folder or SOAP endpoint already exists. Our team can help you review the workflow and request a quote.