In Financial Reporting (FR) Reports, Conditional Suppression Doesn't Work Correctly On Essbase Shared Members Which Are At Different Levels In The Hierarchy
Last updated on AUGUST 07, 2017
Applies to:Hyperion BI+ - Version 18.104.22.168.704 to 22.214.171.124.705 [Release 11.1]
Information in this document applies to any platform.
You have an Essbase cube containing some shared members. For at least one of these members, the original member is level-1 (i.e., it has at least one child member). The shared member, which appears after the original member in the hierarchy, is level-0 (no child members).
You've created an FR report with conditional suppression applied to prevent level-0 members from displaying at runtime. When the report is run, the member (described above) is not suppressed. For shared members that are level-0 at both locations in the outline, the problem doesn't occur -- these members are suppressed correctly in the report.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms