How can you retrieve data from a SAP Business Content Extractor in Talend Studio without SAP modules CMT/TLND_ODP?

[Alastor]

Hi,

I have the following situation: I want to retrieve data from a SAP Business Content Extractor in Talend Studio. I have a successful SAP Connection and the Extractor is located and added under Metadata. For testing purposes, I created a standard job with the tSAPODPInput component "Main" Row output connected to a tLogRow component.

I tried using Built-In or Repository as the Property Type and Schema in my tSAPODPInput component. The problem is, that Talend Studio keeps trying to force the use of a Talend specific SAP module:

Exception in component tSAPODPInput_1 (SAP_Extractor_Test)

SAPException@7bb6ab3a [

errorCode=20

,errorGroup=123

,errorKey=JCO_ERROR_FUNCTION_NOT_FOUND

,errorMessage=Function module '/CMT/TLND_ODP' not found!

,bapiName=/CMT/TLND_ODP

]

When I add a property under "Advanced Settings" for "use_native_api" with value "true", I can prevent it from using that but then I only get 1 row, which does not appear in the log. I assume its some sort of metadata I get, but not the actual data.

Theres a warning on my component that a schema is not defined. Whenever I try to add a Schema under "Edit Schema" in Basic Settings, it automatically forced the use of the Talend Module which is not installed in my SAP system. 

Does Talend Studio not allow for retrieval of data from a SAP BW Extractor without the Talend specific SAP module?

[gouravdubey5]

Hello 

You can retrieve data from a SAP Business Content Extractor in Talend using the tSAPODPInput component, but there are a few prerequisites to be aware of.

First, retrieve the Business Content Extractor into the Repository by right-clicking your SAP connection and selecting Retrieve Business Content Extractor. Once retrieved, the extractor metadata and schema will be available under the SAP connection and can be reused in the job.

Then, use tSAPODPInput and select the retrieved extractor. Talend reads SAP Business Content Extractors through ODP (Operational Data Provisioning), not directly like tables or queries.

Regarding the error
JCO_ERROR_FUNCTION_NOT_FOUND (/CMT/TLND_ODP)
this usually indicates that the required SAP ODP function/module is not available or not activated in the SAP system. In this case, please check with the SAP Basis team that:

The extractor is released for ODP

The required ODP infrastructure is available in the SAP backend

The extractor is supported for external access (not BW-internal only)

Also ensure the extractor schema is correctly retrieved in the Repository; missing or incorrect schema can cause execution issues.

Architect tip:
For stable SAP integrations, always confirm the extractor supports ODP and test it directly in SAP before consuming it in Talend, especially for large-volume or delta scenarios.

Thanks,

Gourav