tELTSAPMap and left outer join

[kurzkano]

Dear community,

does anyone made it to run tELTSAPMap with a left outer join? While joining two (or more) tables with an inner join works seamlessly, an outer join of two (or more) tables immediately runs into

org.talend.sap.impl.SAPConnectionFactory- BAPI failed to start the background job

.

And no: it doesn't matter if you check the "Explicit join" checkboxes or not.

We're running Talend Cloud API Services Platform (R2021-07-7.3.1). Any idea is very welcome.

Best regards

Norbert

[Anonymous]

Hello,

The error information "org.talend.sap.impl.SAPConnectionFactory- BAPI failed to start the background job" is not a specific error message and it seems to be a generic message and coming from misconfiguration.

From your use case, it is coming from mismatch in join keys in the query. It is recommended to create a support case on talend support portal so that our colleagues from support team will give you a remote assistance on your issue to see if there is any workaround for you.

Best regards

Sabrina

[kurzkano]

Hi @all,

we updated to R2021-09-7.3.1 and made sure we're using the most actual SAP module TEDK910156.

I did some more investigation: a LEFT OUTER JOIN works perfectly as long as no WHERE clause is on the joined table:

With a WHERE clause the mentioned error is thrown.

As a workaround one could filter the result afterwards instead of using a WHERE clause. But this would result in millions of records instead of a few thousand - doesn't make sense.

[kurzkano · Accepted solution]

Ok, I finally figured out how to use the component correctly. Of course you can specify a WHERE clause on a column, but you ALWAYS have to check the "Explicit join" checkbox!

The resulting query is processed with ABAP and as far as I understood ABAP always needs an explicit join. This checkbox is obsolete as it must be checked always!

See also Talend Bug Tracker: [TDI-44914] tELTSAPMap initial table join configuration - Talend Open Integration Solution (talendfo...