Our travel expense integration is failing when uploading receipt attachments via SFTP in Oracle Fusion Cloud 23B. Employees submit expense reports through our mobile app, and receipts should automatically sync to Fusion, but we’re getting ‘file not found’ errors that are blocking expense report processing.
We’ve configured the SFTP connector following Oracle documentation, and the directory structure appears correct. The SFTP server is accessible, and we can manually place files in the designated folder. However, when the integration job runs, it fails to locate the attachment files even though they’re present.
SFTP Path: /incoming/expenses/receipts/
Error: File not found: receipt_EXP12345_001.pdf
Status: Integration job completed with errors
The mobile app generates standard PDF and JPG files. We’re concerned about SFTP directory permissions and how file mapping works between the mobile upload and Fusion attachment process.
Let me provide a comprehensive solution addressing all three focus areas:
SFTP Directory Permissions:
Your SFTP integration user needs specific permissions:
Directory: /incoming/expenses/receipts/
Permissions: Read (r), Execute (x) on parent directories
Subdirectories: Read, Execute on all date-based folders
Files: Read permission on all PDF/JPG files
Verify permissions using: `ls -la /incoming/expenses/receipts/
The integration service account must have execute permission on the parent /incoming/ and /incoming/expenses/ directories to traverse to the receipts folder. Many implementations grant read-only without execute, causing intermittent access failures.
Attachment File Mapping:
The critical mapping occurs in your expense import process. Configure your SFTP connector with:
Enable recursive directory scanning: Set scanSubdirectories=true in connector properties
File pattern matching: Use wildcard patterns like receipt_*.{pdf,jpg,jpeg} to accommodate mobile app naming
Implement file staging: Add a preprocessing step that:
Copies files from date-based subdirectories to a flat staging directory
Renames files to match expense report reference format
Validates file exists before expense import runs
In your expense import CSV/XML, reference attachments using:
Grant proper SFTP permissions including execute on parent directories
Enable recursive scanning in SFTP connector configuration
Implement file staging process to flatten directory structure and standardize naming
Add upload completion markers from mobile app
Configure integration job to validate marker files before processing
Implement 5-minute retry window for missing attachments
Add monitoring to track upload-to-processing time lag
This approach eliminates the timing race condition between mobile upload and integration processing while ensuring proper file mapping and permissions throughout the workflow.
This draft is based on general Oracle Fusion Cloud knowledge. It has not been verified against your specific version and environment. Practitioners: verify the steps and share your experience below.
The ‘file not found’ error usually indicates a mismatch between the filename pattern your integration is expecting and what’s actually being uploaded. Check your SFTP connector configuration for the file naming convention. Does your mobile app include the expense report number in the filename? Also verify that the SFTP user has read permissions on the /incoming/expenses/receipts/ directory - sometimes the upload succeeds but the integration service can’t read due to permission restrictions.
We had a similar issue with expense attachments last year. The problem was timing - our mobile app was uploading files to SFTP, but the integration job was running before the upload completed. We implemented a 5-minute delay between mobile upload completion and integration job execution. Also check if your SFTP connector is configured to process files in subdirectories. If files are being placed in date-based subfolders by the mobile app but your connector is only scanning the root receipts directory, they won’t be found.
Confirmed this resolves the SFTP attachment upload failure — adding execute permission on the parent /incoming/expenses/ directory was the missing piece for our Oracle Fusion integration service account.
Good point about subdirectories. I checked and the mobile app does create date-based folders like /receipts/2025-05-22/. Our SFTP connector configuration might not be scanning subdirectories recursively. I’m going to modify the connector settings to enable recursive directory scanning.
Beyond directory scanning, you need to ensure proper file mapping in your integration. The attachment file name must match exactly what’s referenced in your expense report import file. If your expense import CSV references ‘receipt_EXP12345_001.pdf’ but the mobile app uploads ‘EXP12345_receipt_001.pdf’, the integration will fail. Review your mobile app’s file naming logic and ensure it aligns with what your expense import process expects. Also consider implementing a file staging process where files are renamed to match integration requirements before being picked up by the SFTP connector.
From the mobile app perspective, we’re using the standard Oracle Mobile Expense API for file uploads. The API should handle file naming automatically. Have you verified that the mobile app is actually uploading to the correct SFTP path? Check the mobile app configuration settings - there’s a separate SFTP endpoint configuration that might be pointing to a different directory than your integration connector is monitoring. Also, some mobile devices have issues with large image files - if receipts exceed certain size limits, the upload might fail silently.
I’ve been working with our mobile development team and confirmed the app is uploading to the correct path with date-based subdirectories. We modified the SFTP connector to scan recursively, but we’re still seeing occasional failures. I think the timing issue mentioned earlier might be a factor - some files seem to be processed before upload completes.