SAP SFTP
File-based integration (often over SFTP) exchanges data as files, a simple, widely-supported, asynchronous style used for batch data transfer with many systems and partners.
SFTP and file integration moves CSV, XML, fixed-length or IDoc-XML files through a secure location, with PI/PO or CPI file adapters polling, transforming and routing them. It is the low-tech, reliable choice for batch exchange, partners that work in files and legacy systems where real time is unnecessary, provided scheduling, encryption, integrity checks and partial-file handling are planned.
- Formats: CSV, XML, fixed-length, IDoc-XML.
- Watch out: a file that arrived is not a file that was processed, and nothing tells the sender either way.
What SFTP / file integration does
File/SFTP integration writes or reads files (CSV, XML, IDoc-XML, etc.) to/from a secure file location, with middleware (PI/PO or CPI) picking them up, transforming and routing. It is a reliable, low-tech mechanism for batch and partner data exchange where real-time APIs are not available or needed.
Key aspects
- File adapters (SFTP/FTP/file) in the middleware.
- Formats: CSV, XML, fixed-length, IDoc-XML.
- Polling & scheduling for pickup.
- Security: SFTP/encryption, and integrity checks.
When to use it
Use file/SFTP integration for batch data exchange, partner integrations that use files, and legacy systems, especially where real-time is unnecessary. It is simple and robust, but plan for scheduling, security and error handling (partial/failed files).
Common pitfalls
- Wrong tool for the integration style.
- Ignoring monitoring/error handling.
- Point-to-point instead of governed integration.