Circular Reference - any elegant solutions out there?

[#1]

I've run into a circular reference issue and would really appreciate some ideas for a clean, intuitive solution. Attached is my data model.

Each person belongs to a single Cost Center and Country. Each Cost Center belongs to a node in the Cost Center hierarchy. Each Country has a High/Medium/Low Cost Location classification.

I'd like to set up a rate table at the Cost Center Hierarchy and H/M/L location intersection. Each person would then inherit the rate of the Cost Center Hierarchy and H/M/L location they belong to.

A simplified data model is attached - any thoughts on how to break this circular reference, and still get the required business logic above?

[srchilukoori · Accepted solution]

Create a compound key using the Country & Cost Center.

[#3]

Thanks - this makes sense. Will give it a shot. Appreciate the quick feedback.