SAP Integration Suite
SAP Integration Suite's Cloud Integration capability can exchange files with Files.com through its SFTP adapters. An integration flow can collect partner submissions from Files.com, map their contents for an SAP application, and publish response files for delivery. Files.com provides the partner-facing accounts, folders, and transfer methods; the SAP integration flow owns the application processing.
Cloud Integration is also known as SAP CPI. This connection uses its standard SFTP adapters and a Files.com user account. It does not require a Files.com API connector.
Sender and Receiver Direction
SAP names its adapters from the integration flow's perspective. In both cases, the Cloud Integration tenant initiates the connection to Files.com.
| SAP adapter | File movement | Files.com access |
|---|---|---|
| SFTP sender | Reads a file from Files.com into the integration flow. | Listing and download, plus the operations selected for file handling after processing. |
| SFTP receiver | Writes the integration flow's output to Files.com. | Upload, plus any required folder creation, replacement, or rename operations. |
For example, a supplier submits an order to Files.com. The sender adapter collects it for SAP processing. A receiver adapter publishes the resulting acknowledgment in a different Files.com folder, where that supplier can retrieve it. Separate folders make the input and response easy to distinguish and allow each account to receive only the access it needs.
Tenant Credentials and Server Identity
Create a dedicated Files.com machine account with SFTP enabled and the required folder permissions. Configure the adapter's address with your site's hostname or custom domain and port 22. Follow the SFTP connection settings for network access and account authentication.
SAP's SFTP connection setup separates server trust from user authentication:
- The tenant's
known_hostsmaterial identifies the Files.com server by hostname, algorithm, and public host key. Use the host key appropriate to your Files.com hostname. - For public-key authentication, keep the private key in the tenant keystore and register its matching public key on the Files.com user. Select the corresponding private-key alias in the adapter.
- For password authentication, deploy a User Credentials artifact and reference that credential in the adapter.
Use directory paths visible to the integration's account. A configured SFTP client root can present an integration folder as /; the adapter then uses paths within that root.
File Readiness and Repeat Processing
Configure the sender's file selection and read-lock strategy for the way producers publish completed files. Keep files awaiting decryption or other preparation outside the pickup folder. A done-file strategy requires the producer to publish the corresponding completion file; selecting it in SAP does not create that signal.
Review the sender's post-processing choice before its first run. The default deletes successfully processed files, which requires deletion permission and removes the file from its storage location. The option to keep a file and mark it as processed tracks filenames; reusing a name for a later delivery can therefore prevent that delivery from being collected. Choose names and handling that fit the business exchange, rather than treating every scheduled run as a new file.
For receiver output, decide what happens when the destination name already exists. Its temporary-file option can separate an upload in progress from the final filename. Make the downstream collector select the completed output, and grant the account the rename access this arrangement needs.
Use SAP's message processing records alongside Files.com SFTP Logs. Verify the application's result as well as the file operation: collecting an order into an integration flow does not establish that the SAP application accepted it.