Each of the 3 reference links contain one ID each. Now, whenever a certain ID is rejected because it was not present in the reference, I need to add the appropriate reason in the column generator and store it in the dataset. The problem here is that I am not able to differentiate between the rejects and hence the reason added in the Column generator is generic to all 3 ids. the requirement is to have a specific reason.
I do not want to use 3 different Lookup because at this point that would mean dismantling a lot of other jobs which use a similar approach.
Any suggestions gurus?
Jerome
Data Integration Consultant at AWS
Connect With Me On LinkedIn
Life is really simple, but we insist on making it complicated.
Looks like I do not know how to align the diagram. The top oracle connector goes to a transformer that splits data into 3 links which go to the lookup as reference links.
the stream link is from the other oracle connector. The reject link is from the lookup that goes to a column generator. The output of the generator goes to a dataset
Jerome
Data Integration Consultant at AWS
Connect With Me On LinkedIn
Life is really simple, but we insist on making it complicated.
Why not use a transformer instead of column generator and check which particular ref link has caused the reject (by checking the nullability of key columns from reference) and then assign appropriate reasons.
I understand transformer is bulky when compared to column gen but column generator isn't intelligent enough to satisfy your requirement
[/b] tags, however, preserve whitespace which is the secret to making diagrams that line up. Next time use them and make liberal use of the Preview option to make sure things look correct before you post.
-craig
"You can never have too many knives" -- Logan Nine Fingers