Troubleshoot from result to cause

When a result looks wrong, start with expected data value and work backward through the Essbase model and the operations that produced it.

1. Confirm the requested intersection

   Make sure you are looking at the intended combination of members. A value in Essbase represents the intersection of dimensions, so verify the Product, Market, Time, Scenario, Measure, and any other dimensions that apply. Many apparent data problems are actually caused by retrieving a different intersection than expected.

2. Compare detailed values with the source

   If the result is aggregated or calculated, drill down to the lowest relevant level and compare those detailed values with the source data. This helps determine whether the discrepancy entered the cube during data preparation or loading, or appeared later during aggregation or calculation.

3. Check the hierarchy and member properties

   Verify that members are positioned under the correct parents and that their properties support the intended business relationship. For example, confirm that a state belongs to the expected region, that a product rolls up through the correct product family, and that consolidation properties produce the expected contribution to parent values.

4. Review formulas and calculation logic

   If detailed input values are correct but derived results are not, inspect the member formula or calculation process that produces the result. For example, if Margin is incorrect while Sales and COGS are correct, review the logic used to derive Margin. If only a particular area of the cube is affected, also confirm that the calculation processed the intended scope.

5. Review the operations that changed the cube

   Check job status, messages, and output for recent data loads, calculation runs, or outline updates. A successful job confirms that the operation completed, but you should still verify that it acted on the expected data and model. Failed or partially completed jobs can point directly to the source of the discrepancy.

6. Retest from detail to summary

   After correcting the issue, retrieve the detailed values again and then move upward through the hierarchy or calculated results. Confirm that the correction appears at the detailed level and flows through to the expected summaries and business measures.