The SFTP Endpoint Your SAP Landscape Connects To

Yes. File exchange is a first-class SAP integration pattern. SAP Cloud Integration (CPI) ships an SFTP adapter for sender and receiver flows, PI/PO file adapters poll SFTP, FTPS, and FTP endpoints, and IDoc interfaces exchange flat files with trading partners. Files.com is the managed endpoint on the other side of all of them.

SAP CPI authenticates to Files.com with two pieces. The Files.com host key goes into the CPI tenant’s known_hosts file, deployed once because the host key is permanent. Authentication itself runs on the SSH key pair CPI generates in its tenant keystore, with the public key installed on a scoped Files.com service user. CPI’s connectivity test verifies both before the first iFlow runs.

Yes. Files.com handles IDoc and EDI exchange at the file layer. TransformScript converts partner XML, CSV, and EDI into the flat-file shapes your IDoc interfaces import, and each inbound file routes to the right interface by its content. The partner’s format problem never becomes an ABAP change.

Yes. The Files.com Agent runs inside the plant network and makes only outbound connections, so SAP Datasphere output lands on on-premises systems without an SFTP server built or an inbound firewall port opened. The OT/IT boundary stays sealed.

SAP Cloud Integration refuses to connect to an SFTP server unless that server’s host key is deployed in the tenant’s known_hosts file, under Manage Security Material. Files.com’s host key is permanent, so the known_hosts entry is deployed once and never chased again. No iFlow breaks because an endpoint rotated its key.

Yes. PI/PO file adapters poll SFTP, FTPS, and FTP endpoints with exact expectations about modes, ports, and cipher suites, and Files.com meets them. Protocol mandates like a TLS version change become configuration on the adapter, not a migration.

Yes. SuccessFactors integrations deliver and collect HR and payroll files over SFTP like the rest of the SAP estate, commonly PGP-encrypted. Files.com runs the encryption inside the flow and manages the keys in its GPG Key Manager, per recipient.

Each counterparty gets its own Files.com credential and folder, connecting over SFTP, FTPS, FTP, or AS2 on its own terms. No partner sees another’s files, and dedicated IPs give every firewall team on both sides a fixed address to allowlist.

Yes. Files.com delivery monitoring knows when each feed into or out of SAP is due and raises an alert when a window closes without the expected files. A silent supplier-feed failure is a same-day alert instead of a missing IDoc discovered at month-end.

Nothing changes on the SAP side. The hostname, host key, and dedicated IPs your SAP landscape points at are permanent Files.com properties, so storage moves, cloud migrations, and vendor changes happen behind the endpoint without touching a single iFlow, communication channel, or firewall rule.