Best Practices for Allocation Rule Drivers
-
Avoid using dynamic members (upper-level members or members with a formula) in the driver definition.
-
Oracle Essbase ignores destinations with no driver data.
-
Dynamic members require a computation or aggregation before Essbase can determine if driver data is present.
-
A large destination range can result in many unnecessary computation steps for determining whether the driver data is absent.
-
An upper-level member returns an aggregated value – it does not define where to allocate.
-
-
Use data prep rules to compute driver data in ranges where allocation rules will need it – compute once, use many.
-
Keep in mind that if you are migrating from EBS, PSFT or other ledger-based allocations, the driver does not contribute to the destination definition.