Core Financialspublic

General Ledger & Intercompany

Get Involved. Join the Conversation.

This is a public Forum  public

Topic

    Tausif Mulla
    List of Impact on having a (single COA with multiple COA...
    Topic posted January 16, 2019 by Tausif MullaBronze Medal: 1,250+ Points, last edited February 6, 2019, tagged Accounting Hub Cloud Service, Allocations, Assets, Budgetary control, Cash Management, Collections, Compliance, Configuration, Discussion Forums, Expenses, Financials, Fusion, General Ledger, Help Center, Intercompany, OTBI, Payables, Period Close / Reconciliation, Receivables, Reports, Revenue Management, Sample Reports, Search, Security, Setup, Setup / Administration, Subledger Accounting 
    106 Views, 6 Comments
    Title:
    List of Impact on having a (single COA with multiple COA Instance) versus (Multiple COA structure with limited or no COA instance)
    Summary:
    List of Impact on having a (single COA with multiple COA Instance) versus (Multiple COA structure with limited or no COA instance)
    Content:

    Hi,

    We are performing a design workshop and would like to know what all gets impacted within Oracle Cloud financials if we have the below two situation:

    1. Single COA Structure with multiple COA Instance.

    2,. Multiple COA structure with limited or no COA instance.

    One example i can think of is the CVR. Multiple COA structure will require multiple CVR to be defined for each structure. Similarly what are the other impacts based on the above two scenarios ?

    You inputs will help us take design decision. Hence need to know the repercussions for each scenario.

    Thanks !

    Tausif Mulla

    Comment

     

    • Tausif Mulla

      Hi,

      Will appreciate if any thoughts on this post.

      Thanks !

    • Ba Kwon

      For the COA to be used, it is the structure instance that matters. The COA configuration isn't complete until you have done the structure instance.  There is no advantage in having multiple structure instances for one COA structure because each structure instance is a separate COA. I know it is confusing. You can look at both as one complete configuration for COA. I don't see a need to analyze further. I would suggest one structure instance for each COA structure. Please keep in mind each structure instance is a completely separate COA.

      • Neelam Thakur

        Hi Ba,

         

        I have always found this confusing. Thanks for providing some clarity. If you have some further articles or white papers on this subject, I would greatly appreciate it.

        Thanks,

        Neelam

      • Tausif Mulla

        Thank you Ba for your inputs ! It helps !

    • Ba Kwon

      There is no white paper or articles on this subject that I'm aware of. The definitions are stated in Cloud Documentation here. However, they are more or less technical definitions rather than explanation. The bottom line is that each structure instance in combination with an accounting calendar would result in a cube in Essbase. Let's say you really need 3 distinct COA structures, each with the same number of segments and the order of each segment but you need different value sets (for some segments) due to various requirements. Let's say you only need 1 accounting calendar. Whether you create 1 structure and 3 structure instances, or you create 3 structures each with its own structure instance, the end result is the same. You end up with 3 Essbase cubes. All your accounting, SLA, etc. are based on the COA structure instance. Hence, I would rather suggest that defining the structure and the structure instance together completes the COA configuration (1:1 structure and structure instance) and leave it at that.

     

    community forum