Our procurement document import process via FTP has become increasingly unreliable over the past month. We’re experiencing frequent ‘connection reset by peer’ errors when attempting to upload purchase order acknowledgments and invoice files from our supplier portal.
The errors occur inconsistently - sometimes files upload successfully, other times the same file size fails. We’re using passive FTP mode and the files range from 2MB to 15MB. Our FTP timeout is currently set to 60 seconds, and we’re seeing failures mostly with files over 8MB.
The supplier portal generates these files automatically, and we need a stable solution. We’ve considered increasing timeout values, but we’re also hearing that SFTP might be more reliable. Has anyone migrated from FTP to SFTP for procurement document imports in Oracle Fusion Cloud SCM 23C? What are the considerations around file size limits and timeout settings for large batch imports?
Connection reset errors during FTP transfers are typically network-related rather than Oracle Fusion configuration issues. However, I’d recommend checking your firewall settings first. Passive FTP requires a range of ports to be open, and if those ports are being blocked intermittently, you’ll see exactly the behavior you’re describing. Have your network team verify that the passive port range is consistently available and not being throttled by bandwidth management policies.
The SFTP configuration in Oracle Fusion Cloud SCM is managed through the File Import/Export settings in Setup and Maintenance. You’ll need to update the connection parameters, exchange SSH keys with your supplier portal, and test the connectivity. The actual document import process remains unchanged - only the transport protocol changes. Make sure your supplier portal supports SFTP before proceeding. Most modern systems do, but it’s worth confirming their capabilities and any additional security requirements they might have.
I strongly recommend migrating to SFTP for several reasons. First, SFTP uses a single port (22) which simplifies firewall configuration and reduces connection issues. Second, it provides better error handling and resume capabilities for large files. We made this switch last year and our document import reliability improved dramatically. Oracle Fusion Cloud SCM supports SFTP natively, and the configuration is straightforward through the integration settings. The migration effort is minimal compared to the ongoing troubleshooting you’re facing with FTP.
One thing to consider with larger files - Oracle Fusion Cloud has file size limits for imports that vary by module. For procurement documents, the standard limit is 20MB per file, but performance degrades significantly above 15MB. You might want to work with your supplier to implement daily batches instead of weekly if files are consistently large.
We’ve increased the timeout to 180 seconds as suggested, which helped with some of the smaller files, but we’re still seeing failures on files over 10MB. The supplier portal doesn’t support file compression or chunking. Starting to think SFTP migration is the better long-term solution. What’s involved in the configuration change on the Oracle Fusion side?
Let me provide a comprehensive solution that addresses your FTP timeout issues, file size challenges, and migration path to SFTP.
FTP Timeout Settings:
Your current 60-second timeout is insufficient for files over 8MB, especially if network latency is involved. Based on your file sizes (2-15MB), I recommend these timeout configurations:
Connection timeout: 120 seconds (allows for initial handshake delays)
Data transfer timeout: 300 seconds (provides buffer for 15MB files even on slower connections)
Keep-alive interval: 30 seconds (prevents idle connection drops during large transfers)
However, these are temporary measures. FTP’s inherent limitations make it unsuitable for your use case, particularly the connection reset issues you’re experiencing with passive mode.
File Size Limits:
Oracle Fusion Cloud SCM’s procurement module supports files up to 20MB, but optimal performance occurs with files under 10MB. Your 15MB files are pushing the practical limit. Consider these strategies:
Request your supplier portal to generate files more frequently with smaller batches
Implement file splitting logic if you control the export process
Use compression (though you mentioned this isn’t supported by your supplier portal)
The inconsistent failures you’re seeing with 8MB+ files suggest network congestion or bandwidth throttling during peak hours. This is a strong indicator that your current FTP setup lacks the robustness needed for production document imports.
SFTP Migration:
Migrating to SFTP will resolve most of your current issues. Here’s the implementation approach:
Oracle Fusion Configuration:
Navigate to Setup and Maintenance > File Import and Export
Create new SFTP connection profile with your supplier portal details
Configure authentication using SSH key pairs (more secure than password)
Set connection parameters: port 22, transfer mode binary
Supplier Portal Coordination:
Verify SFTP support with your supplier’s IT team
Exchange SSH public keys for secure authentication
Test connectivity from both sides before production cutover
Establish file naming conventions and directory structures
Benefits of SFTP:
Single port (22) simplifies firewall rules and eliminates passive mode port range issues
Better error handling with automatic retry capabilities
Resume support for interrupted transfers (critical for large files)
More reliable connection management reduces timeout errors
Migration Timeline:
Week 1: Configure SFTP on Oracle Fusion side and test connectivity
Week 2: Parallel run with both FTP and SFTP to validate document processing
Week 3: Monitor SFTP performance and error rates
Week 4: Decommission FTP connection after successful validation
File Size Optimization:
Even with SFTP, I recommend working with your supplier to implement more frequent, smaller batches. Daily 5MB files are more reliable than weekly 15MB files. This also improves processing time within Oracle Fusion and provides faster visibility to procurement teams.
Immediate Actions:
While planning your SFTP migration, implement these temporary fixes:
Increase FTP timeout to 300 seconds
Schedule file transfers during off-peak hours (nights/weekends) to avoid network congestion
Implement monitoring and alerting for failed transfers
Create a manual retry process for failed files
The SFTP migration is the right long-term solution. The configuration effort is minimal (typically 2-3 hours), and the reliability improvement is substantial. In our environment, we saw a 95% reduction in transfer failures after migrating from FTP to SFTP for similar procurement document imports.