Which Dimension is able to be used to set up translation if Legal Entity is unrepresented in the Entity Dimension?

Which Dimension is able to be used to set up translation if Legal Entity is unrepresented in the Entity Dimension?

• A. Account
• B. Flow
• C. UD1
• D. UD8

Answer: (B)

When translating data across dimensions, you can use a routing or alias layer so that if a member isn’t present in the primary dimension (the Entity dimension for Legal Entities), the data can still be mapped correctly. The Flow dimension serves this role by carrying the data’s flow context and can be configured with translation rules to map an unrepresented legal entity to the appropriate target. This keeps consolidations and reports accurate even when some entities are missing from the Entity dimension. The Account dimension is about accounts, not translation mapping. User-defined dimensions (UD1, UD8) could hold custom mappings, but Flow is the intended mechanism for handling translation when the Legal Entity isn’t represented.

When translating data across dimensions, you can use a routing or alias layer so that if a member isn’t present in the primary dimension (the Entity dimension for Legal Entities), the data can still be mapped correctly. The Flow dimension serves this role by carrying the data’s flow context and can be configured with translation rules to map an unrepresented legal entity to the appropriate target. This keeps consolidations and reports accurate even when some entities are missing from the Entity dimension.

The Account dimension is about accounts, not translation mapping. User-defined dimensions (UD1, UD8) could hold custom mappings, but Flow is the intended mechanism for handling translation when the Legal Entity isn’t represented.