Oracle Business Intelligence Applications

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

Achieving Highly Customized Layout For Financial Reports in OBIEE/OBIA

Received Response
41
Views
6
Comments

Dear Team ,

 

 

We have requirements to design P&L Report on top of OBIA with customized layout by business team. I am attaching the layout for your reference.

PL report layout.PNG

We are using P&L group accounts dimension and GL Balance/Budget Facts for the same. As per the layout we need to have some custom calculations on top of group accounts to satisfy the layout, For example we need to calculate Product Margin which is Sales + COGS.

Further Group Account names are sorted by a custom key column in repository.

We have tried using selection stesps (creating calculated fields/Groups) in pivot table layout which return correct data as per the expectations. However we are not able to sort calculated fields in selection steps to form desired layout. Further ordering in selection steps seems to be a limitation in OBIEE as per MOS note Doc ID 2040416.1

Please suggest how we can achieve this layout. We are okay to made changes in repository or warehouse for the same.

Regards

Ali Mostafa

Answers

  • Thomas Dodds
    Thomas Dodds Rank 8 - Analytics Strategist

    Having had to do this at multiple clients ... I would suggest you build a custom physical structure to hold the data in that format - then just present it via OBIEE.  You will spin your wheels a lot more trying to rig the presentation/logical layers to do it ...

  • Ali M Mostafa
    Ali M Mostafa Rank 2 - Community Beginner

    Dear Thomas,

    Thanks for quick response.

    I have tried building custom dimension where I tried to include calculated members as a row but couldn't get the success. My group account table is joined with fact table and not sure how I can join calculated dimensions rows in the group account dimension with Fact.

    Can you please explain little more how to achieve this?

    Regards

    Ali Mostafa

  • Thomas Dodds
    Thomas Dodds Rank 8 - Analytics Strategist

    Custom FACT table (it's really a snapshot) ... and/or custom dimension (if your GL Account dim isn't cutting it) to achieve this

  • Ali M Mostafa
    Ali M Mostafa Rank 2 - Community Beginner

    Dear Tomas,

    I have too many fact tables , it's difficult to make replicate theses fact tables . do you any suggestion to make only custom dimension  without change in fact tables?

    Regards,

    Ali

  • Thomas Dodds
    Thomas Dodds Rank 8 - Analytics Strategist

    Too many fact tables?  I doubt it ... a fact star (singe fact table with dimensions) answers a specific question or set of related questions about the business.  Given that foundation - what I hear is "the business asks too many questions" when I hear "too many fact tables".

    Having solved this exact issue more than once for many different sized businesses - the way to go is a custom fact table AND POSSIBLY an additional dimension to solve it.  

  • Naeem Akhtar
    Naeem Akhtar Rank 3 - Community Apprentice

    Below steps may help.

    1. Duplicate group account dimension in warehouse.
    2. Add a new column named Custom Group Account Name.
    3. Add calculated row name in custom group account. in you case product margin & commercial margin etc rows will be inserted.
    4. Calculated rows WIDs will be inserted repeatedly at row level for as many times as number of group accounts in calculated row. For example Sales ROW_WID is 1000 and COGS ROW_WID is 1010 then Product Margin will have two additional rows with ROW_WID as 1000 and 1010.
    5. Copy description of all PL accounts to new column created in step 2
    6. Join this dimension with facts in physical layer, import this as logical dimension and set hierarchy and levels on it.
    7. Add group account content levels in Facts LTS so that aggregation work for newly created group account dimension.
    8. Expose this to presentation layer.
    9. Use custom group account name filed in your report.
    10. Build ETL for new dimention population.

    It should work as "many to many" relation with your facts.

    cheers

    Naeem