The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →There is no single SAP FTP configuration procedure. The correct setup depends on whether you are connecting from SAP AS ABAP, SAP Integration Suite, SAP Process Integration/Process Orchestration, or an SFTP endpoint. For the common ABAP case, the sequence is: confirm the protocol and endpoint, test connectivity from the machine that will run the transfer, maintain the SAPFTP_SERVERS allow-list, generate or check SAPFTP and SAPFTPA, test with RSFTP002, and then run a real upload or download.
known_hosts file normally indicate SFTP, not classic FTP. Do not try to configure an SFTP server as an ordinary SAPFTP endpoint.Choose the correct SAP connection path first
Use the decision guide below before changing SAP configuration. Following the wrong branch is one of the most common reasons an apparently valid connection fails.
| What you are using | Correct SAP-side configuration |
|---|---|
SAP GUI, SM30, SA38, RSFTP002, or custom ABAP |
AS ABAP classic FTP using SAPFTP, SAPFTPA, SAPFTP_SERVERS, and ABAP FTP function modules |
| An Integration Suite integration flow that reads files | FTP sender adapter for FTP or FTPS; use the SFTP sender adapter for SFTP |
| An Integration Suite integration flow that writes files | FTP receiver adapter for FTP or FTPS; use the SFTP receiver adapter for SFTP |
| PI or PO Integration Directory and communication channels | File/FTP adapter for FTP or FTPS, or the separate SFTP adapter for SFTP |
| The partner supplied port 22, an SSH key, or a known-hosts file | SFTP-specific configuration based on SSH authentication and host-key verification |
SAP documents these as separate connection technologies. Its secure-protocol guidance distinguishes FTP and FTPS from SSH-based SFTP.
FTP, FTPS, and SFTP are not interchangeable
| Protocol | How it works | Common port | Important implication |
|---|---|---|---|
| FTP | Traditional File Transfer Protocol without transport encryption | 21 | Usernames, passwords, and file contents can be exposed on an untrusted network |
| Explicit FTPS | FTP upgraded to TLS on the FTP control connection | Usually 21 | The server and client negotiate TLS after connecting to the FTP service |
| Implicit FTPS | FTP over TLS from the beginning of the connection | Usually 990 | The adapter must be configured for implicit TLS rather than ordinary FTP |
| SFTP | SSH File Transfer Protocol, a separate SSH-based protocol | Usually 22 | Use SSH keys or password authentication and known-host verification; FTP function modules do not turn into an SFTP client |
The port is a clue, not absolute proof. Confirm the actual protocol with the FTP administrator. A service on port 21 may require explicit FTPS, and a nonstandard port may be used for any of these protocols.
Information to collect before configuring SAP
Ask the external-system owner for a complete endpoint specification. Do not infer details from an email that merely calls the service an FTP server.
- Protocol: plain FTP, explicit FTPS, implicit FTPS, or SFTP.
- Hostname or IP address and port.
- Username and password, or an SSH private key and passphrase.
- Remote inbound and outbound directories.
- Whether the server requires passive mode.
- The source IP addresses that the partner firewall will allow.
- Filename pattern, extension, and case-sensitivity rules.
- Whether uploads must use a temporary filename and be renamed after completion.
- Whether the exchange is text or binary, and the expected character encoding.
- Retention, duplicate-file, retry, and acknowledgment rules.
- For FTPS, the required CA certificate or trust configuration.
- For SFTP, the server fingerprint or
known_hostsrequirement. - A harmless test file and a test directory where uploading is permitted.
Also identify where the SAP program will run. A dialog transaction may connect from a user workstation, while a scheduled background job normally connects from the SAP application server. That difference affects DNS, firewall rules, routes, credentials, file paths, and operating-system permissions.
Primary walkthrough: configure classic FTP for SAP AS ABAP
This procedure applies when ABAP code or standard reports such as RSFTP002 initiate the transfer through the classic SAPFTP component. It does not apply to an SFTP endpoint and should not be mixed with the Integration Suite adapter procedure.
Prerequisites and authorizations
- SAP GUI access to the relevant SAP client.
- Permission to maintain the FTP server allow-list, or a Basis administrator who can do it.
- Access to the SAP application-server operating system or help from the network and Basis teams.
- The partner’s host, port, protocol, credentials, directories, and firewall requirements.
- A controlled test file and a safe upload location.
SAP protects the standard RSFTP* reports with authorization object S_ADMI_FCD and value SFTP. If RSFTP002 or RSFTP005 is unavailable, ask the Basis or security team to provide the required authorization rather than bypassing the control.
1. Confirm the endpoint and protocol
Record the details in a change or interface document. For example:
Host: ftp.example.com
Port: 21
Protocol: FTP or explicit FTPS
Username: supplied FTP user
Remote path: /inboundIf the specification instead says Port: 22, SSH public key, or known_hosts, stop this procedure and select an SFTP-capable adapter or approved SFTP client. Adding port 22 to the classic FTP allow-list does not add SSH support.
2. Test TCP reachability from the actual execution host
Test the control port from the machine that will run the transfer:
telnet ftp.example.com 21Where available, use:
nc -vz ftp.example.com 21For a background ABAP job using SAPFTPA, run the test from the SAP application server, not just from an administrator’s laptop. For an interactive test using SAPFTP, the connection may originate from the frontend workstation.
A successful TCP test proves only that a connection to the control port was possible. It does not prove that the username and password work, the SAP allow-list is correct, passive data ports are open, the user can access the required directory, or a file can be transferred.
3. Maintain the SAPFTP server allow-list
In SAP GUI, open:
- Transaction
SM30. - Enter maintenance view
SAPFTP_SERVERS_V. - Choose Maintain.
- Add the approved FTP hostname or IP address and port, with a useful description.
- Save the entry in the appropriate transport or configuration process used by your organization.
SAPFTP_SERVERS_V is the maintenance view. The underlying allow-list table is SAPFTP_SERVERS. SAP’s AS ABAP security documentation explains that classic SAPFTP access to arbitrary FTP servers is restricted by default.
Maintain the entry in every relevant SAP client if the configuration is client-dependent in your release and landscape. Confirm the behavior in your system rather than assuming that an entry in one client automatically covers all clients.
* weakens the control and can permit connections to untrusted servers. SAP recommends restricting the allow-list to only the servers required by the application. If a wildcard is used temporarily for controlled diagnosis under local policy, remove it immediately after testing.4. Check or generate the standard RFC destinations
Run RSFTP005 from SA38 or SE38. This standard report checks the SAPFTP setup and can create or regenerate the standard RFC destinations:
Free tools Windows power users keep installed
One-click scans. No signup required.
SAPFTP— intended for frontend or local execution.SAPFTPA— intended for application-server execution and background processing.
Use SM59 to inspect an existing destination if the report identifies a problem. Do not replace a standard destination with an arbitrary TCP/IP destination unless the Basis team understands where the sapftp executable must run and how the destination is configured.
SAP’s background FTP guidance documents the different execution locations and the role of RSFTP005.
5. Test login, directories, and a real transfer with RSFTP002
Execute RSFTP002, the standard FTP command test. Supply the FTP username, password, host, and the appropriate RFC destination.
For an interactive test, select SAPFTP. For a test that represents a background job, select SAPFTPA. Try commands such as:
pwd
ls
cd /inbound
get test-file.txt
lcd /usr/sap/tmp
put test-file.txtFTP command syntax can vary by server implementation, and the user may be restricted to a chrooted home directory. The important result is an end-to-end test: successful login, directory access, and a controlled download or upload. Do not regard a successful pwd as proof that production file processing will work.
SAP identifies RSFTP002 as the standard Execute FTP Command report and documents the command-based workflow through FTP_COMMAND in its ABAP FTP function-module documentation.
6. Implement the ABAP transfer
The classic sequence is:
- Scramble the password for the legacy API call with
HTTP_SCRAMBLE. - Open the FTP session with
FTP_CONNECT. - Run commands with
FTP_COMMAND, or transfer text data withFTP_SERVER_TO_R3andFTP_R3_TO_SERVER. - Close the FTP session with
FTP_DISCONNECT. - Close the RFC connection with
RFC_CONNECTION_CLOSE.
A simplified skeleton is shown below. The variables are placeholders and should be declared, validated, and populated by your program.
CALL FUNCTION 'HTTP_SCRAMBLE'
EXPORTING
source = lv_password
sourcelen = lv_password_length
key = 26101957
IMPORTING
destination = lv_scrambled_password.
CALL FUNCTION 'FTP_CONNECT'
EXPORTING
user = lv_user
password = lv_scrambled_password
host = lv_host
rfc_destination = lv_rfc_destination
IMPORTING
handle = lv_handle.
IF sy-subrc <> 0.
" Log the error and stop before attempting FTP commands
ENDIF.
CALL FUNCTION 'FTP_COMMAND'
EXPORTING
handle = lv_handle
command = lv_command
TABLES
data = lt_response.
CALL FUNCTION 'FTP_SERVER_TO_R3'
EXPORTING
handle = lv_handle
fname = lv_remote_file
character_mode = 'X'
TABLES
text = lt_text.
CALL FUNCTION 'FTP_R3_TO_SERVER'
EXPORTING
handle = lv_handle
fname = lv_remote_file
character_mode = 'X'
TABLES
text = lt_text.
CALL FUNCTION 'FTP_DISCONNECT'
EXPORTING
handle = lv_handle.
CALL FUNCTION 'RFC_CONNECTION_CLOSE'
EXPORTING
destination = lv_rfc_destination.The example shows both direct text transfers; a real program normally uses the applicable operation rather than calling both. Check sy-subrc and returned messages after every function module, and guarantee cleanup on every error path. SAP documents the handle-based session and the need to close both the FTP session and the RFC connection.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
About HTTP_SCRAMBLE and password security
HTTP_SCRAMBLE with key 26101957 is part of SAP’s documented classic API example. In this context, scrambling or obfuscation is more accurate than calling it modern encryption. It does not encrypt ordinary FTP traffic and does not protect files moving over the network.
- Do not hard-code a production password in an ABAP report.
- Do not store the password in an unprotected custom table.
- Use the credential-storage and secret-management approach approved for your SAP release and organization.
- Use FTPS, SFTP, HTTPS, or managed file transfer when the data or credentials must be protected in transit.
7. Handle foreground and background file paths correctly
There are three different machines to keep separate:
- Presentation server: the user’s workstation running SAP GUI.
- Application server: the SAP server where background jobs execute.
- FTP server: the external remote system.
Use SAPFTP when an interactive transfer should originate from the frontend. Use SAPFTPA when the program runs on the application server, particularly in a background job. For background processing, files should be written to an approved application-server directory rather than a presentation-server path. /usr/sap/tmp/ is only an example; the directory must exist and be writable by the relevant SAP operating-system account.
Frontend APIs such as GUI_UPLOAD depend on a user session and are unsuitable for a background job. SAP’s background-transfer documentation explains why the application-server route must be tested separately.
Recommended Free Tools
SAP Integration Suite / Cloud Integration
Use this branch when the transfer belongs in an Integration Suite integration flow rather than in a direct ABAP report.
When SAP reads files from the partner
Add an FTP sender adapter when the tenant polls an external FTP server. Configure the source directory, filename or pattern, server host, port, proxy type, encryption mode, and credentials artifact. Depending on the runtime and adapter version, you may also configure timeout, reconnect attempts, reconnect delay, file deletion or retention behavior, and idempotency-related processing.
Typical filename patterns include file*.txt and file?.txt. Confirm the exact behavior in the adapter documentation for your tenant. SAP’s FTP sender documentation also describes passive-mode operation and binary transfer behavior.
When SAP writes files to the partner
Add an FTP receiver adapter when the integration flow sends a message to the external server. Configure:
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →- Target directory.
- Static or dynamic target filename.
- Host and optional port.
- Proxy type.
- Location ID when the On-Premise proxy is used.
- Plain FTP, explicit FTPS, or implicit FTPS encryption mode.
- The User Credentials artifact.
- Timeout, reconnect attempts, and reconnect delay.
- Directory-creation and path-handling options.
- Whether to disconnect after each message.
See SAP’s FTP receiver adapter documentation for the current field names and runtime behavior.
Cloud Integration settings that need verification
The following values are documented for the current Cloud Integration FTP adapter scope, but should not be generalized to classic ABAP or every PI/PO release:
Rank #4
- Wireless File Transfer
- Full functional SSH Server
- SFTP File Transfer
- Protect USB charging port
- Multiple users with multiple paths
| Setting | Documented Cloud Integration behavior |
|---|---|
| Plain FTP default port | 21 unless another port is entered |
| Explicit FTPS default port | 21 |
| Implicit FTPS default port | 990 |
| Transfer mode | Binary |
| Passive mode | Supported; active mode is not supported by the Cloud Integration FTP adapter |
| TLS session reuse | Not supported by the FTP adapter |
| Default connection timeout | 10,000 milliseconds |
| Default reconnect attempts | 3 |
| Default reconnect delay | 1,000 milliseconds |
| SFTP | Not supported by the FTP adapter; use the separate SFTP adapter |
For the Cloud Integration connectivity test, enter the hostname without https://, a path, or a URL scheme. Provide the port, proxy type, Location ID when applicable, and encryption mode. SAP describes these requirements in its FTP connectivity-test documentation.
Using SAP Cloud Connector for an on-premise endpoint
Use the On-Premise proxy when the FTP server is inside a private network and the Integration Suite tenant must reach it through SAP Cloud Connector:
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitches- Install Cloud Connector in the on-premise network.
- Establish the required subaccount connection and authentication.
- Configure access control for the target FTP host and port.
- Ensure the backend system is exposed through the required virtual host and port.
- Select the On-Premise proxy in the adapter.
- Enter the matching Location ID if your landscape uses one.
- Deploy the credentials artifact.
- Run the FTP connectivity test.
- Deploy the integration flow and monitor a controlled test message.
Cloud Connector does not remove the need for firewall rules, partner allow-listing, directory permissions, or passive data-port planning. SAP’s Cloud Connector guidance for Cloud Integration adapters covers the on-premise setup.
SAP PI/PO File/FTP adapter
For SAP Process Integration or Process Orchestration, configure the connection in the Integration Directory rather than using the AS ABAP SAPFTP_SERVERS view.
- Create or open the communication channel.
- Select adapter type
FILE. - Select sender or receiver direction.
- Select FTP as the transport protocol.
- Enter the host, port, credentials, directory, filename, and processing behavior.
- Configure content conversion if the file must be converted to or from XML.
- For FTPS, import the issuing CA certificate into the appropriate trusted keystore.
- For SFTP, use the separate SFTP adapter and configure SSH keys or partner fingerprints.
- Activate the channel and test through message monitoring.
PI/PO labels and available options depend on the NetWeaver release and installed support packages. Some older SAP documentation is marked as no longer updated, so consult the documentation for your precise release and the applicable SAP Notes before treating a field as universal. Relevant references include SAP’s PI/PO File/FTP adapter documentation and its NetWeaver 7.5 receiver documentation.
Network and firewall requirements
FTP uses a control connection and a separate data connection. Opening only port 21 may allow login while still preventing directory listings or file transfers.
In passive mode, the server advertises a data port and the client connects to that port. Ask the network team to confirm:
- Control port.
- Passive data-port range on the FTP server.
- Source IP address of the SAP application server, frontend workstation, or Cloud Connector.
- NAT behavior and the address advertised by the FTP server.
- Firewall rules in both directions where required.
- TLS inspection or certificate interception that could break FTPS validation.
Passive-mode restrictions differ by product. Cloud Integration’s FTP adapter supports passive mode but not active mode; do not automatically apply that statement to every ABAP or third-party FTP client. PI/PO documentation also discusses the separate FTP data-port requirement.
Text, binary files, and encoding
Do not assume that a successful transfer means the file is usable. A CSV or XML file has character-encoding and line-ending requirements, while a PDF, ZIP, spreadsheet, image, or other binary file must not be treated as text.
- Confirm whether the partner expects UTF-8, UTF-16, ISO-8859-1, or another code page.
- Check whether line endings must be preserved or converted.
- Use binary transfer for PDFs, ZIP files, images, Excel files, and other binary payloads.
- Use character mode only when the ABAP API and receiving application both expect text.
- Cloud Integration’s FTP adapter uses binary transfer mode by default; configure charset handling explicitly where applicable.
The classic FTP_SERVER_TO_R3 and FTP_R3_TO_SERVER examples above use a text table with character_mode = 'X'. Do not copy that choice for binary payloads without selecting and testing the appropriate binary-capable implementation.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchBest Value
- Wireless File Transfer
- Full functional SSH Server
- SFTP File Transfer
- Protect USB charging port
- Multiple users with multiple paths
Production file-handling design
Connection setup is only part of a reliable interface. Define the behavior around the files before scheduling the job or deploying the flow.
- Incomplete uploads: have the sender write a temporary name and rename it only after the upload completes, or use a completion marker.
- Polling: avoid reading a file while another system is still writing it.
- Duplicates: use idempotency, a processed-file repository, a unique business identifier, or another controlled duplicate strategy.
- Retries: ensure a retry cannot create a second business posting after a successful transfer with a lost acknowledgment.
- Retention: define whether successful files are deleted, moved to an archive directory, or retained by the partner.
- Permissions: verify that the FTP user can list, download, upload, rename, and delete only what the interface requires.
- Monitoring: alert on authentication failures, connection timeouts, missing expected files, rejected filenames, and repeated retries.
- Paths: distinguish remote FTP paths from SAP application-server paths and do not rely on a user’s workstation directory for a background job.
Troubleshooting matrix
| Symptom | Likely cause | What to check | Corrective action |
|---|---|---|---|
| User has no access authorization for computer | Missing or mismatched SAPFTP allow-list entry | SAPFTP_SERVERS_V, hostname, port, SAP client, and RFC destination |
Add only the approved server and port in the correct client; do not solve it with an unrestricted wildcard |
| Attempt to set up connection failed | Wrong host or port, DNS, firewall, protocol, or RFC setup | Test from the actual execution host; inspect RSFTP005, SM59, application-server traces, and FTP-server logs |
Correct the endpoint, route, destination, or firewall rule, then repeat an SAP-side test |
| Dialog works but background fails | The dialog used the frontend while the job uses the application server | RFC destination, application-server DNS and route, source IP allow-list, OS path permissions | Use SAPFTPA, test from the application server, and use an application-server file path |
| Login fails | Wrong credentials, expired account, wrong protocol, or FTPS/SFTP mismatch | Partner account status, TLS mode, SSH key, host, port, and server logs | Use the protocol-specific adapter and approved credential material |
| Login succeeds but listing or transfer fails | Directory permission, chrooted path, filename, quota, or data connection issue | Run pwd, ls, cd, and a harmless transfer; inspect passive ports |
Correct the remote path or permissions and open the required passive range |
| Passive-mode timeout | Only the control port is open or the server advertises an unreachable address | Passive data-port range, NAT, firewall, and source IP | Align the server’s passive range and firewall rules; do not test only port 21 |
| FTPS certificate failure | Untrusted CA, hostname mismatch, expired certificate, or TLS inspection | Certificate chain, endpoint hostname, trust store, and inspection devices | Import the approved CA chain or correct the endpoint; do not disable validation casually |
| WinSCP works but SAP does not | WinSCP may be using SFTP, a key, a different route, or a different directory | Actual protocol, port, source IP, authentication method, and remote path in WinSCP | Match the SAP product and adapter to the protocol actually used |
Port 22 fails in RSFTP002 |
The endpoint is probably SFTP | Partner specification, SSH key requirement, and host fingerprint | Use an SAP SFTP adapter, Integration Suite SFTP adapter, or approved SFTP integration layer |
| File contents are corrupted | Text/binary mismatch, wrong charset, or line-ending conversion | File type, transfer mode, encoding, hashes, and receiving-system expectations | Use binary mode for binary files and explicitly configure the required text encoding |
| The same file is processed twice | Retry or polling behavior has no idempotency control | Message logs, processed-file records, rename/delete behavior, and acknowledgment timing | Use a completion strategy and an idempotent processing design |
SAP’s SAPFTP troubleshooting guidance specifically points administrators toward the allow-list, RSFTP005, RFC destinations, and traces when classic SAPFTP errors occur.
Choosing a safer or more suitable alternative
| Requirement | Reasonable choice |
|---|---|
| A legacy partner supports only unencrypted FTP | Classic FTP may be technically necessary, but isolate it, risk-assess it, restrict the allow-list, and avoid sending sensitive data without compensating controls |
| FTP semantics are needed with TLS encryption | FTPS |
| The partner requires SSH keys or port 22 | SFTP |
| Cloud orchestration, transformation, retries, and monitoring are required | SAP Integration Suite |
| An existing on-premise middleware system owns the interface | PI/PO File/FTP or SFTP adapter |
| A simple ABAP batch job must reach a legacy FTP endpoint | SAPFTPA and the classic ABAP FTP APIs, subject to security review |
| A new integration carries sensitive data | FTPS, SFTP, HTTPS/API, object storage, or managed file transfer instead of plain FTP |
For a new interface, compare security, observability, retry behavior, file-volume limits, transformation needs, supportability, and clean-core policy—not merely whether a classic function module can connect. Depending on the business process, an IDoc, OData, SOAP, REST API, event, object-storage exchange, or document-management service may be a better integration than FTP.
Final SAP FTP configuration checklist
- Correct protocol confirmed: FTP, explicit FTPS, implicit FTPS, or SFTP.
- Host, port, directories, credentials, and filename rules documented.
- Source IP identified for dialog, background, or Cloud Integration execution.
- TCP reachability tested from the actual execution host.
- Passive data-port range confirmed where FTP or FTPS is used.
SAPFTP_SERVERS_Vmaintained with only the required server and port for ABAP.RSFTP005completed and the correctSAPFTPorSAPFTPAdestination selected.- Credentials protected and not hard-coded in custom ABAP.
- FTPS certificates or SFTP host keys validated.
- Real login, directory, download, and controlled upload completed.
- Text encoding and binary-transfer behavior verified.
- Temporary filenames, completion markers, duplicate handling, retries, and retention defined.
- Background job tested independently from dialog execution.
- Monitoring, alerting, and partner-side logging enabled.
Frequently Asked Questions
Can SAPFTP connect to an SFTP server on port 22?
No. Classic SAPFTP is an FTP client and adding port 22 to the SAPFTP_SERVERS allow-list does not add SSH/SFTP support. Use the SFTP adapter in Integration Suite or PI/PO, or another approved SFTP integration layer configured with the required SSH keys and host verification.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsWhat is the difference between SAPFTP and SAPFTPA?
SAPFTP is intended for frontend or local execution, while SAPFTPA runs the FTP client from the SAP application server and is the appropriate destination for background processing. A successful dialog test with SAPFTP does not prove that a scheduled job using SAPFTPA will work.
Does a successful telnet test prove that SAP FTP is configured?
No. Telnet or nc confirms only that the TCP control port is reachable from the machine that ran the test. You must still verify the SAP allow-list, RFC destination, credentials, directory permissions, passive data ports, encryption mode, and an actual upload or download.
Where is the SAP FTP server allow-list maintained?
Use SM30 with maintenance view SAPFTP_SERVERS_V. The view maintains entries in the underlying SAPFTP_SERVERS table. Restrict the entries to the required hosts and ports.
Is plain FTP safe for production files?
Plain FTP provides no transport encryption. If the partner supports it, prefer FTPS, SFTP, HTTPS, or managed file transfer for sensitive business data. If plain FTP is unavoidable, use network isolation, strict allow-listing, limited credentials, and a documented risk assessment.
The Bottom Line
For direct ABAP transfers, maintain the restricted SAPFTP_SERVERS allow-list, generate or verify SAPFTP and SAPFTPA with RSFTP005, and test the complete exchange with RSFTP002 from the same host that will execute the job. If the endpoint uses TLS or SSH, configure FTPS or SFTP through the SAP product that supports it instead of treating every file-transfer service as classic FTP.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
