Differentiate reject links in lookup with multiple ref links

[jerome_rajan]

Hi All,

I have a job that looks like this:

Code: Select all

                       ORA
                         |
                         |
                        TXN
                       |  |  |
                       |  |  |
           ORA---------->LKP------>
                          |
                          |
                      COLGEN
                          |
                          |
                          DS

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_rajan]

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

[zulfi123786]

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

[jerome_rajan]

Now was it not as simple as that! Thanks a million! Really appreciate it.

[ray.wurlod]

Server or parallel job? The answer will be different.

You posted in the Server forum but marked your job type as parallel.

[jerome_rajan]

Sorry Ray. It's a parallel job. Can this be moved to the Parallel forum?

[jerome_rajan]

Just one more scenario that I am posed with.

None of my keys are nullable. Basically all the reference links carry an ID for a corresponding key in the stream link.

Sample Record in stream: A,B,C,D,E

There would be an ID in the reference link corresponding to each column s that my target would be

A,1,B,2,C,3,D,4,E,5

How should I be filtering this in the transformer on the reject link? Or is there an alternative?

[jerome_rajan]

Never mind. Solved this by setting reject failure to 'Continue' and filtering the resulting nulls.

[chulett]

Sorry Ray. It's a parallel job. Can this be moved to the Parallel forum?

Yes, of course... done.

Also, please make use of the Reply to topic button, there's no need to quote everything every time you reply. See how much nicer things look now?

Lastly, the forum software removes all "extra" whitespace which is what destroyed your ASCII art. The

Code: Select all

[/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.

[jerome_rajan]

I am relatively new to this forum and am still getting used to the 'Best Practices'. Your information helped that cause. Thank you