Set which value wins in a transaction with overlapping relationships
Related information
Related topics
If you have transactions with overlapping dimension relationships; that is, the base dimensions are different and the related dimension is the same, but with different values, you can set the priority for which related dimension value wins. For example, if you have two relationships where the two base dimensions are Customer and Department, and the related dimension is Class, you can configure the priority-order setting so that Class takes it value from the Customer/Class or the Department/Class relationship whenever the two relationships overlap in a transaction.
| Subscription |
Platform Services |
|---|---|
| Regional availability |
All regions |
| User type | Business user |
| Permissions | Business user with admin permissions |
| Restrictions | You can't export or import an application package that contains standard-to-standard dimension relationships. Import or export the package first, then manually create the relationships. |
| Previous step |
- Go to General Ledger > Setup > Configuration. The Configure General Ledger page appears.
- Scroll down to the Dimension relationships table.
- In the Priority order column for the appropriate related dimension, drag the handle of the dimension that should take precedence to the top of the list.
Next step: Filter and restrict overlapping values
