Oracle Analytics Publisher

How to build custom analysis using BIP Data Model SQL

Received Response
37
Views
3
Comments

Hi Everyone,

I have a customize BI Publisher Report for Procurement Data from PR until AP Payment with some customize parameter to use a grouping Business unit that i mapped with a Standard Lookup. The BIP Report is successfully created and user can use the report.

But they have another requirement to build the same report in the OTBI (Analysis). Because this report is used by many department and each department have their own data that need to show in the report then i am thinking that we can use the Custom Analysis.

Predefined Analysis is not have the detail information that we need, i try using "Procurement - Procure To Pay Real Time" and "Receiving - Purchase Receipts Real Time" but both of the Analysis cannot show the customize BU Grouping from standard lookup.

I try to insert the SQL that i use in my data model but it throw an error said INVALID SQL.

How to use the custom SQL for the analysis?

Regards,

Hendra

Answers

  • Hi @Hendra_innopia

    I try to insert the SQL that i use in my data model but it throw an error said INVALID SQL. —> Are you creating an DM using sql query and facing invalid sql error?

    are you trying to create an report based on analytics report/subject area's?

    Regards,

    Arjun

  • Hi Mallikarjuna,

    I try to create a Custom Analysis by using Create Analysis from Simple Logical SQL.

    Regards,

    Hendra

  • Hi @Hendra_innopia ,

    Just to be sure you are reaching the right audience with your question: you are not creating a Publisher report but an analysis based on a Logical SQL query, right?

    If it's the case, I would move your question to the right category (currently in the Publisher category), because "SQL" is a different language than LSQL (Logical SQL).

    And if when you enter the LSQL you have in there you get the message that your LSQL is invalid, then you should post your LSQL here, otherwise it's quite difficult to say much more than "write a correct LSQL and it will be good".