Financial Reporting (FR) Users Can Not Access ASO Reports Based For BSO_ASO Coupled Application With Essbase As Connection Type
(Doc ID 2679422.1)
Last updated on MARCH 18, 2022
Applies to:
Hyperion Planning - Version 11.1.2.4.005 and laterHyperion Essbase - Version 11.1.2.4.000 and later
Hyperion BI+ - Version 11.1.2.4.000 and later
Information in this document applies to any platform.
Symptoms
This issue is limited to when FR (Financial Reporting) report points to an ASO cube BSO_ASO coupled application with Essbase Connection type while users lack the Essbase administrator privilege. Also while using a planning type connection for BSO-ASO coupled application, the FR report is not able to display ASO members aliases correctly for shared members on report. Issue is seen only when suppress missing blocks is enabled on FR report. If only basic suppress options are enabled (If Zero, If Error, If Missing), behavior works fine.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |