Level 2 Funcitionally Dependent and Not Consistent

Question

I'm trying to create a dimension table but get the following error when i try to add a child dimension:
BUSINESS MODEL CCCi PS Fin Analyitcs:
[nQSError: 15001] Could not load navigation space for subject area CCCi PS Fin Analyitcs.
[nQSError: 15019] Table PeopleSoft FIN Tree Node Hierarchy is functionally dependent upon level Node Level 1 Hierarchy, but a more detailed child level has associated columns from that same table or a more detailed table.
Here is the situation. I have a single physical table (Table A) that contains data that makes up a hierarchy. Here are the key fields: (1) Node Name, (2) Node Level (1 high - 9 low), and (3) Parent Node Name. I want to create a dimension that allows me to drill down from level 1 to level 9 for node details. Initially I've tried to set this up to just drill down from level 1 to level 2.
What I've done:
(1) Created two aliases for Table A: 1A and 1B in the Physical Layer
(2) Created a complex join between Tables 1A and 1B where Parent Node Name of 1B = Node Name of 1A and 1B Node Level = 2.
(3) Created a Logical table and moved the three fields (from above) from table 1A to the logical table.
(4) In the logical table source I added the 1B table as a new table and joined it to 1A using a Left Outer join
(5) Added 3 columns from 1B to logical table
(6) Selected create dimension from the logical table
This created a dimension with the 3 fields (total of 6) from 1A and 1B on the first level. I do a Check Consistency at it passes. However, i really want the 3 fields from 1B to be on a child dimension.
(7) I create a child dimension and drag the 3 fields on level 1 from 1B to level 2 (the child level).
(8) Check consistency and i get the message from above.
I'm not sure why i cannot do this. If you can help solve this or provide an alternative solution it would be helpful.
Thanks...

Answer 1

I think the key's are a potential error but am not sure that a clearly understand how to do this. Here is what i have:
1) When I copied the columns from the first physical table (Table 1A) over to the logical table it created the keys Node Name and Node Level no the Logical table in the Business Model.
2) When I copied the columns from the second physical table (Table 1B) over to the logical table it did not create these as keys on the logical table in the Business Model. It just created them as columns.
3) When I created the first level of the dimension table I created a key for only the Table Name since that is what i want to be able to drill down on. This pass consistency verification.
4) When I created the second level of the dimension table I created a key from the second node name field (from the second physical table) on the logical table. This is part of the key on the physical table but is not part of the key on the logical table. This is when it fails consistency.
I'm not sure how to arrange these keys to meet what you suggested.
Thanks...