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

Announcements
Save $650 on Qlik Connect, Dec 1 - 7, our lowest price of the year. Register with code CYBERWEEK: Register
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

[resolved] Some Problems with added lookup in Oracle-SF integration

Talend Version:
Version: 6.1.0.2 
Build id: 
Hello Community, 
I have some problems with my Talend Integration Salesforce Component. 
We add some more connections and fields continously to ur Oracle-SF Process in talend.
The next step was an additional query oracle lookup on an Field from an other existing query.
Actually the Oracle-SF Integration looks like this:

The query to Oracle Database from Component "Umsatz Lookup":

"SELECT DISTINCT 
(RELFIRMA.FIRMANR),
DATENFELDER_1,
RELES.VORVORJAHR,
  RELES.AktJahr,
  RELES.VorJahr,
  RELES.SATZART
FROM INFOR.RELFIRMA RELFIRMA
LEFT OUTER JOIN INFOR.RELES RELES
ON RELES.DATENFELDER_1 = RELFIRMA.FIRMANR
WHERE SATZART = 'UK'"
Here is the Query from the component "Oracle-Query-account-ktxt":
"SELECT 
  DISTINCT
 (RELFIRMA.FIRMANR),
 RELFIRMA.FIRMANR,
  RELANSCH.STRASSE,
  RELANSCH.ORT,
  RELANSCH.LAND,
  RELANSCH.STAAT,
  RELANSCH.PLZORT,
  RELANSCH.POSTFACH,
  RELACP.VERTRETER1,
  RELANSCH.LANDKNG,
  RELADRESSE.ANSCHRIFTNR,
  RELFIRMA.ABCKLAS,
  RELFIRMA.USTIDNR,
  RELFIRMA.KTXT,
  RELFIRMA.BEMERKUNG,
  RELFIRMA.VERWENDUNG1,
  RELFIRMA.CREATEDATE,
  RELFIRMA.MODIFYDATE,
  RELFIRMA.ABCKLAS,
 RELFIRMA.NAME,
  RELACP.TEXT0,
 RELACP.TEXT1,
  RELACP.TEXT2,
  RELACP.TEXT3,
  RELACP.TEXT4,
  RELACP.ZBED,
  RELZTLB.KTXT Lieferbedingungen,
  RELZTSPE.KTXT \"Spedition/Versand\", 
  RELZTZB.KTXT Zahlungsbedingungen 
 FROM (INFOR.RELFIRMA RELFIRMA
INNER JOIN INFOR.RELADRESSE RELADRESSE
ON (RELFIRMA.FIRMANR = RELADRESSE.FIRMANR)
inner JOIN INFOR.RELACP RELACP
ON (RELFIRMA.FIRMANR = RELACP.MNR)
inner  join  INFOR.RELANSCH RELANSCH
ON (RELADRESSE.ANSCHRIFTNR = RELANSCH.ANSCHRIFTNR))
right outer JOIN INFOR.RELZTLB RELZTLB
ON (RELACP.TEXT0 = RELZTLB.ZTKEY) 
right outer JOIN INFOR.RELZTSPE RELZTSPE
ON (RELACP.TEXT1 = RELZTSPE.ZTKEY)
right outer JOIN INFOR.RELZTZB RELZTZB
ON (RELACP.ZBED = RELZTZB.ZTKEY)
WHERE RELFIRMA.VERWENDUNG1 = '1'
AND RELFIRMA.FIRMANR = '32275'
AND RELANSCH.VERWENDUNG1 = '1' 
AND RELFIRMA.FIRMANR NOT LIKE 'I%'
AND RELZTSPE.Sprache = 'de'
AND RELZTZB.Sprache = 'de'
AND RELZTLB.Sprache = 'de'"
And here is the Lookup  with  Mapping :

The problem is, that the mapping still take action in other way as it should be.
The Field  DATENFELDER_1, which has an lookup to FIRMANR  will be mapped to Umsatz_VorVorjahr__c but it's just declared as an key 
an not as an mapping one.
For Testing i've made an query with an doubled Firmanr Field it's called  FIRMANR1
Here is the ouput after mapping with the 2 related Fields:

As you can see the 2 Fields has the same Values but this does not reflect the mapping in the prevoius step.
I don't know where these strange behaviour comes in.
Does anyone  has an idea 
thanks in advance 
regards john 
Labels (4)
14 Replies
Anonymous
Not applicable
Author

So some notes or suggestions for me.
Or do you need some more infos or explainations.... is sth. unclear
best regards fireskyer  
Anonymous
Not applicable
Author

Bumping ..... 
regards fireskyer 
Anonymous
Not applicable
Author

No one again ? 
regards 
Anonymous
Not applicable
Author

Update:
Whats is crucial 
If i change the Order from the Fields in the Mapping the output is null for the affected fields.
regards john 
Anonymous
Not applicable
Author

Update :
I had an other job and i could solve the problem with an very idiotical trick which gives no sense.
I rearaange the Fiels from the tmap schema  a little bit ( put the field down in the schema  ) ... but with other job it doesnt work.
But back to this actual job:
I haven't achieved to make this job working.
What iv'e done is to rebuild the job from scratch in a completely different way.
@xdishi:
Do you have researched the java code from the job ? Or only the job conception 
I don't know why this job doesn't work properly. 
But I asssume that Talend cannot process some Jobs with Lookups within an  join statement together not really properly.
But depsite of that guess ... i just change everything with other components.
so in any way the issue is "solved " .. but I'M really interested in the fact  what was  wrong with the job
regards john