ODATA - FML_UPLMATINVPR_SRV usage

[ritushree]

Hi Team ,

We would like to integrate this functionality directly from the SAP backend (ABAP) using the odata service - FML_UPLMATINVPR_SRV without using the Fiori UI. Specifically, our requirement is:

Read an existing Excel file stored within SAP (e.g., MIME repository / application server)
Pass the file content programmatically to the OData service
Trigger the same processing flow (upload → validation → batch → post)
Is it supported to use the OData service FileContentForUploadSet in a backend-driven scenario where:
The Excel file is not uploaded via Fiori UI
Instead, the file content (XSTRING) is read directly from SAP repository
And sent programmatically via HTTP client (CL_HTTP_CLIENT) or similar framework?

Thanks & Regards

Ritushree 

[junwu]

doesn't sound like a good idea.

[mark_pe · Accepted solution]

I did some research and here is a checklist you may try.

The idea here is to leverage some logs to see and pinpoint where the issue is.  So the checklist below may help your team check the valid/needed logs to pre-determine what may be causing the issue.

1. Payload & Header Verification
[ ] CSRF Token: Ensure the code first performs a GET request to retrieve the x-csrf-token and passes it back in the POST header.

[ ] Slug Header: Verify if the service requires a Slug header (common in SAP upload services to define the filename).

[ ] Content-Type: Ensure the header is set precisely to multipart/form-data with the correct boundary string if required by the service definition.

2. Environment & Authority Check
[ ] Service Authentication: Does the user context executing the ABAP code have authorization for both the OData service and the underlying business logic (e.g., M_MATE_WRK)?

[ ] MIME/App Server Access: Confirm that the technical user executing the code has read access to the specific path on the Application Server (transaction AL11) where the Excel file resides.

3. Execution Simulation
[ ] Trace Comparison: Try to run a Fiori upload while the trace is active in /IWFND/TRACES. Compare the HTTP request headers generated by the Fiori framework with the headers their ABAP code is sending.

Note (Additional Idea):  Instead of CL_HTTP_CLIENT (which is legacy), try to use the CL_WEB_HTTP_CLIENT or the CL_HTTP_DESTINATION_PROVIDER frameworks if you are on an S/4HANA 2023 environment. These offer better integration with the current SAP connectivity.

These are just some idea to hopefully expose the issue.  Then the experts from the team can act on it.