Core Financialspublic

General Ledger & Intercompany

Get Involved. Join the Conversation.

This is a public Forum  public

Topic

    Jan Groenen
    Performance creating account GroupAnswered
    Topic posted April 29, 2014 by Jan GroenenGreen Ribbon: 100+ Points, last edited January 30, 2019, tagged Financials, General Ledger 
    318 Views, 8 Comments
    Title:
    Performance creating account Group
    Summary:
    When creating a new account group added one line with the detail account information takes forever..
    Content:

    Hi all,

    When clicking on the Plus sign on the accounts region Fusion seems to load all possible values of all segments into its cache. This is taking forever and some of the time does not finish at all.

    Any other users having this problem or solved it? We are having a P1 open now for 3 weeks to solve this issue but no luck until now! It is a strange issue because essbase should be very fast!

    See below the screenshot…

    Best Comment

    David Haimes

    Mathieu,

    I believe you are are on R7, so the patch number with the fix is 17960794.

    It is included in the Financials Release 7, patch bundle 11.

    In order to see the improvement for table validated value sets, you will need to rebuild the cube.

    Let me know if you have any more questions.

    Thanks

    David

    Comment

     

    • Jan Groenen

      Hereby the screen shot

      Account group.docx (80KB)
    • Jan Groenen

      Hi we resolved the issue with the performance of the essbase functionality. 

       

      We used some table based validation sets in our accounting flexfield per example Employee code. So whenever a new employee was entered in HCM the code which was used was also available in our accounting flex field segment. This caused Essbase to completely breakdown. We now created a trigger which adds a value in the accounting flex field value set whenever a new employee is entered in HCM and it orks fine now.

    • David Haimes

      We did have a performance issue with table validated value sets in R5, which has since been fixed.

      The patch is available via http://aru.us.oracle.com:8080/ARU/ViewPatchRequest/process_form?aru=17091554

      • Mathieu Kamp

        Hi David,

        The patch which you are referring to cannot be found by us with a 'normal'  Oracle support login. Also the URL you are referring to seems to be an 'internal' Oracle URL.

        Could you help us out to get this patch?

        Thanks and regards,

        Mathieu Kamp

        • David Haimes

          Mathieu,

          I believe you are are on R7, so the patch number with the fix is 17960794.

          It is included in the Financials Release 7, patch bundle 11.

          In order to see the improvement for table validated value sets, you will need to rebuild the cube.

          Let me know if you have any more questions.

          Thanks

          David

    • Mathieu Kamp

      This was indeed the issue. So be aware when using table validated value sets ;-)

      • David Haimes

        No need to be aware when using a table validated value set because we have fixed the issue now.  A table validated value set will perform just the same as any other value set.

    • Jairo Rojas Mendez

      This was indeed the issue. So be aware when using table validated value sets

     

    community forum