Mapping will not load tables in correct order

Question

I am running OWB 10.2.
I have a set of tables with parent/child relationships enforced by FK constraints as follows: A -> B -> C and D
I created a mapping to load tables A, B and C and this works perfectly. I then copied to mapping and modified to load tables A, B and D, keeping basically the same flow particularly at the load end (i.e. just a few different attributes).
My problem is that when I generate the mapping it wants to load the tables in the order B then A then D. The original job generates the order A then B then C as expected.
I have tried setting the Target Load Order property such that A = 1, B = 2 and D = 3 but this makes no difference to the generated PL/SQL.
Has anyone else had a similar problem?

Answer 1

ok, figured it out.
I was putting in the load order in each table operator not the mapping properties.
I think this is a UI issue because:
1. There are 2 places you can modify table load order but one seems to have no effect.
2. I knew table order was listed somewhere but had trouble finding it.
3. You have to click on the mapping somewhere on the canvas to get to the mapping properties. This is however, completely different to the mapping properties you get by clicking on Mapping -> Properties from the menu
4. At no stage had I manually modified the table order before the problem occurred yet it was overriding the order that should have been determined by the FK constraints.