Column Relationships Rules
These rules apply when you define column relationships for a column set:
A table can have only one column set for a specific effective date.
You can define column relationships for column sets with future effective dates.
The sequence numbers within a column set must be unique.
A basis column can have multiple different destination columns. A destination column cannot be defined for multiple basis columns.
A column pair in a column set does not have to have a relationship with the other column pairs. You can have unrelated relationships within the pairs in a column set.
After you define a basis column for a column pair, you cannot use the basis column as a destination column for another pair with a higher sequence number. Stated another way, after you define a destination column for a column pair, you cannot use the destination column as the basis column with a lower sequence number. The end result in both of these scenarios is the same; the system will issue an error message.
Following these rules, sequence number 40 would result in an error:
Sequence Number
Basis Column
Destination Column
10
Category Code 01
Category Code 02
20
Category Code 02
Category Code 03
30
Category Code 03
Category Code 04
40
Category Code 04
Category Code 02