Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Want to see what's currently in public preview? We've pulled it all together in one place. Check it out here
cancel
Showing results for 
Search instead for 
Did you mean: 
vintac
Partner - Contributor III
Partner - Contributor III

Error with tSAPTableInput using RFC server

Hello,

i'm trying to read a table from SAP S4/HANA using the tSAPTableInput with the RFC server, but i keep getting this error:

[ERROR] 09:12:02 org.talend.sap.impl.service.client.SAPStreamServiceClient- Request failed with status code 404: {"timestamp":"2025-10-06T09:12:02.739+00:00","status":404,"error":"Not Found","message":"No static resource api/stream/default/table.","path":"/api/stream/default/table"}
[FATAL] 09:12:02 test.sap_test_0_1.SAP_test- tSAPTableInput_4 Request failed with status code 404: {"timestamp":"2025-10-06T09:12:02.739+00:00","status":404,"error":"Not Found","message":"No static resource api/stream/default/table.","path":"/api/stream/default/table"}

I already connected the RFC Server with SAP following the documentation and the connection is working, below the component configuration

vintac_0-1759742923073.png


Anyone can help me to solve this? Thanks in advance.

Vincenzo.

Labels (2)
1 Reply
gouravdubey5
Partner - Creator
Partner - Creator

Hello,

tSAPTableInput is not supported when using an RFC Server connection.
This component is designed to read SAP tables using a direct RFC client connection, where Talend initiates the call to SAP.

When configured with an RFC Server, Talend expects inbound (push-based) scenarios and internally attempts to access the SAP Stream Service, which results in the error:
No static resource api/stream/default/table.

Recommended action:

Reconfigure tSAPTableInput to use a standard RFC client connection (Application Server or Message Server).

Ensure the SAP user has the required table and RFC authorizations.

Best practice:
For S/4HANA systems, consider using tSAPODPInput for ODP-based extraction, which is the supported and future-proof approach.

 

Thanks,

Gourav

Talend Solution Architect | Data Integration