Supplier collaboration mobile app fails to upload large attachments over 5MB

SCM Oracle Fusion Cloud SCM
, , , , , , , ,
1

We’re having issues with our supplier collaboration mobile app in Fusion Cloud SCM 24A. Suppliers are unable to upload compliance documents larger than 5MB through the mobile interface. The upload starts but fails midway with a generic timeout error.

Smaller files (under 2MB) upload fine, so I suspect we’re hitting some API gateway file size limits. I’ve checked the server-side error logs and found this:


ERROR: Request entity too large
URI: /fscmRestApi/resources/supplierPortal/attachments
Content-Length: 8388608
Status: 413 Payload Too Large

Desktop uploads work for files up to 25MB, so this appears to be specific to how the mobile app handles multipart upload requests. This is causing significant compliance delays as suppliers need to submit detailed technical specifications and quality certificates. Has anyone configured the mobile API gateway to handle larger file uploads?

2

Don’t forget about the timeout settings. Even if you increase the file size limit, large uploads might still fail due to gateway timeouts. The default timeout for mobile API calls is usually 60 seconds, which isn’t enough for 5MB+ files on slower mobile connections. You need to increase both the read timeout and write timeout values in your API gateway configuration. We set ours to 300 seconds for document uploads.

3

The 413 error confirms you’re hitting the API gateway’s default file size limit for mobile endpoints. Oracle sets different limits for mobile vs desktop for performance reasons. Check your API Gateway configuration under Integration Cloud > API Platform > Policies. There should be a ‘Request Size Limit’ policy that’s likely set to 5MB for mobile endpoints. You’ll need to increase this, but be careful not to impact performance for users on slower mobile networks.

4

Check if your mobile app is using the correct Content-Type header for multipart uploads. It should be ‘multipart/form-data’ with a boundary parameter. Also verify that the mobile SDK you’re using supports large file uploads - some older SDKs have hardcoded limits. The server-side logs you shared show the full content length is being sent, which suggests the mobile app isn’t chunking the upload at all.

5

Here’s a comprehensive solution addressing all three critical areas:

API Gateway File Size Limits: The 413 error indicates you’ve hit the default 5MB limit for mobile API endpoints. Increase this limit in your API Gateway configuration:

  1. Navigate to: Tools > Integration Cloud > API Platform Gateway
  2. Select your supplier portal API policy
  3. Modify the Request Size Limit policy:

Max Request Size: 26214400 (25MB in bytes)
Apply to: Mobile endpoints
Path Pattern: /supplierPortal/attachments/*

Also update the reverse proxy configuration if you’re using Oracle Web Gateway:


ProxyIOBufferSize 65536
LimitRequestBody 26214400

Multipart Upload Handling: Your mobile app needs to implement chunked uploads for files over 2MB. The current implementation is trying to send the entire file in one request, which causes both size limit and timeout issues. Implement this approach:

  1. Split files into 2MB chunks
  2. Upload each chunk with Content-Range headers
  3. Use the resumable upload API endpoint

Pseudocode for mobile app implementation:


// Pseudocode - Chunked upload implementation:
1. Calculate total chunks: fileSize / chunkSize (2MB)
2. For each chunk:
   a. Read chunk bytes from file
   b. Set header: Content-Range: bytes start-end/total
   c. POST to /fscmRestApi/resources/supplierPortal/attachments/chunked
   d. Store upload session ID from response
3. Send final commit request with session ID
4. Handle resume logic if network fails mid-upload
// Reference: Oracle Fusion REST API Guide Section 8.4

Server-Side Error Logs Analysis: Enable detailed logging to track upload progress and identify failure points:

  1. Set logging level for attachment uploads:

Logger: oracle.apps.scm.supplierPortal.attachments
Level: FINE
Include: request headers, content length, upload duration

  1. Monitor these specific error patterns in logs:

    • 413 Payload Too Large: API gateway limit hit
    • 504 Gateway Timeout: Timeout before upload completes
    • 500 Internal Server Error: Backend storage issue

  2. Check backend storage quotas - ensure your file repository has sufficient space

Additional Configuration: Increase timeout values to accommodate large file uploads over mobile networks:


API Gateway > Timeout Configuration
Read Timeout: 300 seconds
Write Timeout: 300 seconds
Keep-Alive Timeout: 120 seconds

For optimal performance, implement these mobile app enhancements:

  1. Show upload progress bar with chunk-level granularity
  2. Implement automatic retry for failed chunks
  3. Cache partially uploaded chunks locally for resume capability
  4. Compress files before upload if they’re not already compressed

After these changes, suppliers should be able to upload files up to 25MB from the mobile app. The chunked upload approach also provides better reliability on unstable mobile connections. Monitor your server-side logs for the first few days to ensure the new configuration handles the increased load without performance degradation.

One final recommendation: implement a file size warning in the mobile app that suggests switching to desktop for files over 10MB, as upload time and battery consumption can be significant for very large files on mobile devices.