Two common problems can occur with exceptions by location. One, when you drill down one way, the exception is enforced. When you drill down another way, it is not enforced. Two, although your exceptions have been created properly, you can still see the excepted measure.
If you do not create your exceptions for all submeasures below your initial exception, users may be able to bypass it and see measures that you intended to hide.
This issue occurs when you create an exception in the location structure. Locations below this measure are not excepted. Unless you create exceptions consistently for all submeasures in the structure, users can bypass the exception to access a measure. Users can drill down by measure, then access the measure by drilling down by location at lower levels in the view.
Problem two occurs when your exception has been validated somewhere else and is being overridden by Metrics Management. Explaining this problem requires describing hierarchy calculations.
Hierarchy synchronization is the operation that enforces the exceptions by location. Synchronization suppresses or hides the measures in the view that should not be seen. Metrics Management synchronizes hierarchies in three passes. The first pass analyzes each view individually and tracks all valid measure and location pairs. The second pass flags all measure and location pairs that are invalid due to exceptions. The final pass checks if measure and location pairs are invalid in one view but valid in another view. If a measure and location pair is invalid in one view and valid in another, Metrics Management validates the measure across all views. Metrics Management assumes that if someone is using the measure and location pair then it should not be excepted.
After synchronizing hierarchies, in Setup—Measure—Properties, invalid locations for a measure appear in Locations, as shown in the example in Figure 5‑4.
Figure 5‑4 Locations at which a measure is excepted
Although less likely, an additional problem occurs where certain measure and location pairs are validated and invalidated in the same view. Use Parent Measures to see measures in a view.
If a measure and location pair is validated, and you believe that it should not appear, verify that the exception was created properly. Also, check whether someone validated that the measure and location pair appears in another view or structure.
If you do not create your exceptions for all submeasures below your initial exception, users may be able to bypass it and see measures that you intended to hide.