Form Formula in Planning 11.1.2.4 displays as #No ACCESS in Smartview for a non-admin user

On a recent Planning 11.1.2.4 implementation we encountered an issue where a formula in a Planning form displayed #No Access in Smartview when accessed by non-admin users. When we logged in as an admin, the formula worked fine. The same formula displayed correctly when accessed through the Planning web.

Planning Smartview #No Access

Planning Patch Set Update (PSU): 11.1.2.4.002 did not resolve this issue either.

We raised an SR with Oracle and after a few development iterations; Oracle confirmed this to be a bug and logged Bug 21280663 – FORMULA IN PLANNING FORM DISPLAYS AS #NO ACCESS IN SMARTVIEW FOR NON-ADMIN USER

4 thoughts on “Form Formula in Planning 11.1.2.4 displays as #No ACCESS in Smartview for a non-admin user

  1. Hello!

    I faced this problem.

    Technical support of an oracle speaks that apply patch system is necessary. After application of a patch – the mistake remained. Those support ignores inquiries.

    Tell, it managed to you to solve this problem or to find some workaround?

    Thanks.

    • Hi Alexandr,

      Applying Plannning patch PSU 11.1.2.4.002 did not fix the issue. Oracle has identified this issue as a bug and their development team is working on it. I have not been given a date on when they will issue a patch. As soon as I get more information, I will post it.

      As far as workaround goes, you can use the Smartview Planning Admin Extension to upload formulas. There is a post on this site on using the Smartview Planning Admin Extension. Test updating formulas using the Smartview Planning Admin Extension on a dev environment before using it on Prod.

      Thanks,
      Neha

  2. Thanks for the answer, the answer from those got supports today:

    Bug 21476478 – HYPERION PLANNING FORMULA ROWS SHOW #NO ACCESS IN SMARTVIEW

    Even after applying the suggested patch 11.1.2.4.002 — Planning and calc manager the issue remains the same.

    The status of the bug seems its in testing phase with a patch (Could be 11.1.2.4.003 or 11.1.2.4.004)

    This bug is tentatively triaged to future Planning 11.1.2.4.004.

Leave a Comment