SCD fails to recognise key for update

[clarcombe]

We are trying to use SCD in a very simple job to generate type 2 lines for currencies if the description changes.

The first pass works and we get all the data into the target dimension table, the second pass aborts with the 'Input not sorted at record 18' error across all partitions.

What we have tried.
On input we have hash partitioned and sorted the reference and the source table.

We have done the same operation using a lookup and the data matches.

I feel I am so close but it might be a lot less effort to try and use a lookup with a change capture and copy routine. But I have to do 40 tables like this so I have to ensure the best method is used

Thanks

[soumya5891]

I think in the SCD stage there are two types of functioning.
1. In build look up stage
2. Transformer stage.
First performs look up then performs transformation in the transformer.
So for the SCD stage always make the partition as auto.

Let me know if any other issue is there

[clarcombe]

We tried auto initially but it doesnt fix the problem. This is why I then tried hash partitioning

[soumya5891]

Are you selecting your business keys and type 2 column properly?
Can you please provide your business keys column and type 2 column?

[rameshv]

Give same order of columns both the scd stage. check surrogate key given properly