Additional columns in physical query

hi,
OBIEE 11.1.1.6
This is continuation from my old post for strange behavior of logical to physical query transformation.
Floor applied during
I got additional column during the transformation from logical SQL to physical SQL
select Distinct 0 as c1, case when .... as c2 from ....where 0 as c1 is additional column which I am getting.
Did anyone experienced with the same issue? any solution for to overcome this issue?
Thanks,
Hesh

Based on default OOB query settings this get generate, generally with WITH clause. No point to trace it for the reasons untill this is not affecting to your results.
I would suggest just ignore ;)
Pls mark as correct/helpful if helps

Similar Messages

  • How to show additional column in the Query searchby field selection window?

    Hi Experts,
    I have a simple query as below:
    select * from ocrd where cardcode between '[%0]' and '[%1]'
    Now, it is evident that the searchby field is the cardcode, so when I click on the browse button, all cardcodes will be displayed for me to choose on a separate selection window. Now, on this separate selection window, can I also show an additional column "customer name"?? This is because I cannot really identify every customer code, and need to depend on customer name instead.
    Thanks!
    Warmest Regards,
    Chinho
    note: please dont ask me to use the below query instead, that is not what I want to achieve.
    select * from ocrd where cardname between '[%0]' and '[%1]'

    Hi!
    It's not possible i belive. You can use Filter Option instead on Selection Parameter.

  • Adding columns to content query

    I have created a Content Query that retrieves all of my tasks from my site collection that meets my filter criteria.  However, The Item Views are incredibly limited
    (basically just the title).  I want to add ~5-7 additional columns to the query, such as due date.  I understand I may have to do this through SharePoint designer.  Please advise and if coding is required, please let me know what code to use.

    Hi,
    I understand that you want to add columns to content query web part.
    To include additional columns in the Web Part's query, we need to perform some minor customization in the .webpart file. We should programmatically instruct the Web Part to rename columns to names the default XSLT transformation expects, and then render
    the columns by using the default XSLT transformation styles. For more information:
    http://msdn.microsoft.com/en-us/library/ms497457(v=office.14).aspx
    But the default XSLT transformations can render the following four fields:
    Title, Description, LinkUrl, and ImageUrl, we can  add a column and display it as the
    Description field in the Web Part. If we want the other columns to appear in addition to the KB title and product, modify the XSLT transformation and add the rendering for the additional columns.
    More information:
    How to: Customize the SharePoint Content By Query Web Part by Using Custom Properties (ECM):
    http://msdn.microsoft.com/en-us/library/aa981241(v=office.14).aspx
    How to: Customize XSL for the SharePoint Content By Query Web Part (ECM):
    http://msdn.microsoft.com/en-us/library/bb447557(v=office.14).aspx
    How to: Customize the Rendering of a Field on a List View:
    http://msdn.microsoft.com/en-us/library/ff606773(v=office.14).aspx
    Customizing List Views with XSLT Transformations:
    http://msdn.microsoft.com/en-us/library/cc300164(v=office.12).aspx
    Best Regards,
    Linda Li

  • How can i join additional column without using a query

    Hi,
    I created a report using a base query; Now i want to add an additional coloumn to it without using another table i.e. from no new query; That additional column is complex computed value from different tables created for each record; How can i attach it to each record;
    thanks in advance
    prasanth

    Add a formula column in your existing query.

  • Query Report - To display additional column in list selection box.

    Hi,
    There is query report where i want to display the additional column in list selection.
    Below is the system query report, where parameter passed is card code.
    When the cardcode - list selection is clicked system displays 2 columns i.e. Customer Code & No. of Records.
    Now in the same list selection; is it possible to display the customer name along with cardcode only for reference.
    SELECT T0.DocDate, T1.SlpName, T2.Name, T0.DocDueDate, T0.DocNum,    (CASE WHEN T0.DocStatus = 'O' THEN 'Open' ELSE 'Closed' END) AS Status,    T0.DocTotal FROM OQUT T0 LEFT JOIN OSLP T1    ON T0.SlpCode = T1.SlpCode LEFT JOIN OCPR T2 ON T0.CntctCode = T2.CntctCode WHERE T0.CardCode = N'[%0]'    ORDER BY T0.DocNum DESC
    Kindly let me know the details.
    Thanks & Regards,
    Yogesh Jadav

    Hi Yogesh Jadav,
    The answer is NO.  You may only display either code or name but not both.
    Thanks,
    Gordon

  • Physical query not accessing Fact Table/Column

    Hi,
    I'm facing a weired issue. I have a report with 32 columns. 22 columns are from 8 dimensions and 10 columns from 3 Facts.
    But while observing the Physical query. Its not touching 1 particular Column coming from 1 Fact Table.
    So, in the query only 2 Fact columns are there and in the report its always Null value.
    When I'm adding a filter on that Fact Column to force Analytics to go and join with that Fact Table, Its not including that Fact Table/Column and producing a very funny query like the following:
    SELECT
    COLUMNS....
    FROM
    TABLES (8 DIMENSION AND 2 FACTS)
    GROUP BY COLUMNS....
    HAVING cast(NULL as DOUBLE PRECISION )>1234
    ================================
    "cast(NULL as DOUBLE PRECISION )>1234" - this is the filter, I have added on that Fact Column.
    Note- It may be because of RPD configurations/joins. But the system (Siebel Analytics 7.8) is in production for 2 years and 500 users using it and nobody reported any issue like this before.
    Can anyone please give me some helpful hint, idea, what is happening?
    Thanks in Advance
    Regards
    Sudipta

    Hi Kishore,
    Thanks for your reply.
    However, I did the analysis and found following, please let me know if your perspective is falling in the same line or not.
    Scenario:
    Suppose all the columns i'm trying to fetch, are coming from 5 dimensions [d1,d2,d3,d4,d5] (some of them are aliased table) and 3 fact tables [f1,f2,f3]
    Now, the report is not fetching data for c1 column which is coming from f3 fact table. Even f3 table is not included in the physical query.
    Now what i found that, there is a dimension suppose d3 which is not having any direct join with f3, but other facts like f1,f2 have joins with d3 table.
    If i remove the columns coming from d3 dimension from report, then f3 fact columns are getting populated in report.
    Problem:
    I need to provide a single physical query for that report, while those report columns are defined by the business.
    Questions:
    1. So is it really possible to create a query for that kind of report without changing the RPD design?
    2. If no, then is the only solution to split that report (i'm thinking) into 2-3 sub reports?
    Thanks all of you for replying and providing your thoughts.
    Regards
    Sudipta

  • Addition of Filters on Answers changing the physical query

    Hello,
    I have three Dimensions D1, D2 and D3 joining (as left outer join in BM layer, i have a requirement where i have to show all the records from Dimension) to a common Fact 'F'
    I am trying to build a report based on columns from 3 dimensions.
    The report gives a correct output, and returns a single physical query.
    If i add a filter condition from say D1 on the report like D1.Col = <something> on the answers report, the physical
    query splits in two and then join the two query to give the result.
    Any thoughts what could have gone wrong here?
    Thank You

    hi..
    First tell me all dimensions are left outer with fact?
    Then, check your fact table LTS levels..
    If you have created hierarchies for dimensions, and all dimensions are directly connected to the facts... then, mention the levels for particular fact LTS to detail level for all dimensions. .
    Check this...

  • Physical query generation: unneeded dimension tables get joined to the fact

    Hi there!
    The setup is the following:
    There is a logical fact table which is joined to 7 logical dimensions, it has 4 table sources which correspond to different time dimension levels (all other dimensions are mapped to Detail level).
    Time dimension logical table also has 4 different table sources (for days, months, quarters, and years).
    The data source is an Oracle Database 11gR2.
    The problem is:
    No matter what the logical query is, in the physical query all 7 joins are performed, even if the resulting data is then simply discarded. This results in very bad query performance.
    I feel that it is somehow related to the level-based fragmentation (since, for instance, inclusion of time dimension columns in SELECT list (not in WHERE) seems to affect physical queries), but lack sufficient knowledge to solve this problem or put up with it.
    My questions are the following:
    1) Have you ever encountered such a situation?
    2) Can unneeded joins be eliminated?
    2.1) If yes, how?
    2.2) If not, then why are they needed?
    Thanks in advance!

    Physical level:
    D01-D06 - ordinary physical tables.
    D_DATES - all time levels from dates to years, D_MONTHS - time levels from months to years, also D_QUARTERS and D_YEARS.
    F_DAILY - fact table joined to all of the D01-D06 and to D_DATES, F_MONTHLY - joined to D01-D06 and D_MONTHS, also F_QUARTERLY and F_YEARLY. All measure columns are the same.
    Logical level:
    D01-D06 correspond to ordinary logical tables with a single table source. Logical dimensions are created.
    D_TIME is a logical time dimension with four levels (dates, months, quarters, and years) and four table sources ( D_DATES, D_MONTHS, D_QUARTERS, and D_YEARS ).
    F is a fact table with four logical table sources ( F_DAILY, F_MONTHLY, F_QUARTERLY, and F_YEARLY ) with aggregation content levels set correspondingly.
    OBIEE correctly picks physical table sources for different time levels, but generates extremely inefficient SQL (joining all dimension sources in a WITH-subquery, doing ROW_NUMBER over a result set, and then discarding half the columns, which were not needed to start with).

  • Additional columns in Cross tab

    If I have Project name as the column and project count as the summary in a cross tab
    for eg
    ProjectA,ProjectB, ProjectC
    3,             4,           5
    CaN i add additional columns next to project C having  some condition related to these projects and project counts and then get the grand total??
    Thanks

    Let's see...  This is about the tenth time I've answered this question in the past few weeks, but, hay, let's do it again! 
    The only way I am aware of adding columns to a crosstab is by including new data in your database query.  So, if you currently are returning the data
    Project    Count
    ProjectA   2
    ProjectB   4
    ProjectC   5
    Than, probably using a database command for the data source, change it to return
    Project    Count
    ProjectA   2
    ProjectB   4
    ProjectC   5
    Totals     11
    How this is accomplished very much depends on your database tables and what additional columns you want to add to the crosstab.
    HTH,
    Carl

  • Syntax error in OBIEE generated Physical query - Advance filter concept

    I encountered a syntax error when running a report with the help of advanced filter concept.
    I am getting syntax error at the physical query generated by the OBIEE for main report.
    I used a sub report with the help of advanced filter concept in main report.
    I am posting the physical query for the convenience.
    select D1.c2 as c1,
    D1.c1 as c2
    from
    (select sum(T600347.sales_usd) as c1,
    T601002.currency as c2
    from
    (Select distinct currency from pfact) T601002,
    pfact T600347
    where ( T600347.currency = T601002.currency and T600347.pdate between ( select distinct min(D1.c1) as c1* from
    (select D1.c1 as c1
    from
    (select D1.c1 as c1
    from
    *(select max(T600425.pdate) as c1*
    from
    *(select distinct pdate from pdates where pdate is not null) T600425*
    where  ( T600425.pdate < 11/22/2010 )
    *) D1*
    ) D1
    ) D1 ) and '11/25/2010')
    group by T601002.currency
    ) D1
    I executed the query against my database(sybase) in query tool. It showed error.
    I took out the column alias generated by the OBIEE ("as c1" as underlined). Then the query is working fine.
    How to disable OBIEE from generating the alias.
    Is there any way to do it.
    If obiee is generating the physical query, i am suprised to see a syntax error.
    The bold part is the query from Intermediate report
    I underlined the problematic part.
    Please help me. This is an urgent reuirement,
    Thanks in advance for the help.

    HI,
    When I execute the query on query tool ( my database is sybase)
    I am geting error at "as c1" part, as underlined in the query.
    when I remove that and execute the query, It is generating the output.
    here is the better view of query and error:
    http://img255.imageshack.us/img255/4719/25187227.jpg

  • RPD - Cannot obtain number of columns for the query result :Working with MS SQL 2012 schema

    Hi All,
    I have created my warehouse in MS SQL 2012.
    For management purpose, I have created different schemas in SQL database
    In RPD, Physical layer, when i view data > I get error as
    [nQSError:16002] Cannot obtain number of columns for the query result.
    [nQSError:16001] ODBC error state : S0002 code : 208 message: [Microsoft][ODBC SQL Server Driver][SQL Server] Invalid object name 'tbl'..
    [nQSError:16001] ODBC error state : S0002 code : 208 message: [Microsoft][ODBC SQL Server Driver][SQL Server] Statements could not be prepared..
    I have already browsed : OBIEE 11g Strange ODBC Driver Error with SQL Server : Total Business Intelligence ... did not help me
    please help!!!

    Hi All,
    After all R&D it is been found that Oracle business administrator( RPD) needs default dbo schema. It doesn't accept custom schema for pulling data.
    If anybody have other views please share.!!
    Thank you

  • Filters not applied in Physical Query?

    Hi all..I have two tables (facts) and a dimension table..
    Fact A, Fact B, DIm C
    fact A, Dim C belong to one database in one Physical Server (CUrrent Data Server)
    Fact B belong to another database in another Server (History Server)
    I have a report combining all these three tables.
    But, When I apply filters in the report and check the physical query...
    3 queries are being fired to to two Servers...
    but I could see the filters on only one Query (for Fact A)
    It is scanning whiole table of Fact B and Dim C and looks like filtering in BMM layer...hence my report is taking long time to run, as it is scanning the whole table without criteria..
    Is there any thing I can do, such that The report filters are sent via all the queries?

    Both fact donot have same structure..
    my report consists of:
    Dealer Number ||||||||||||||customer number |||||||||| customer name|||||||||purchase date||||||| settle date|||||| Price
    Customer number, Purchase date, settle date comes from FACT A
    Customer name Comes from Dim C
    Dealer Number,Purchase Date, Settle date, prine are in Fact B
    FACT A and Dim C are in same server but different databases..(sorry I just realized I mentioned same databases in my previous posts)
    Dealer Number, Purchase Date, Settle date are input to FACT B which is in different Server. Price is pulled with these columns as inputs..
    The thing is, Server should send a single query for Fact A, Dim C as they are in same server ...But it is sending two....(scanning Customer dimension fully...)
    The real problem is..:::::
    I have Dealer Number as report filter..
    I wish this filter applies to FACT B....
    but It isn;t....

  • Adding Additional Columns to the Results

    Hi,
    I wanted to additional column in iRecruitment Vacancy Results Table.I have added the column using personlaization but it's not displaying.
    Here are the Steps that I have done.
    iRrecruitment Administrator --> Vacancies --> Search for the Approved Vacancies.
    Click on the Abpout Page and found the VO Object: IrcVacancyVO
    Found the Attribute that I need to add : VACAttribute8
    I have created a New Item with Style : Message Styled Text
    and provided the View Attribute (VACAttribute8) and View Instance(IrcVacancyVO) accordingly.
    The Item that I am adding is attribute8 of the Additional Vacancy Details DFF.I have enabled this attrbiute in the Flexifield.
    The attribute is part of the IrcVacancyVO Query.
    I am not sure what's I am missing but its not displaying the column that I have added.
    Any Input is highly appreciated.
    Regards,
    A
    Edited by: 791680 on Jun 17, 2011 11:22 AM

    Hi Wasey,
    Try as Diwakar told. I am not able to see that tripline in display mode. A long back i copied the same program and i added extra fields in it.I copy program SAPLMCB3 inside which routine AUSGABE_LISTE_KZ.
    Regards,
    Madhu.

  • Logging level to get the physical query

    Hi All,
    Can anyone let me know , what log level i have set it up, so that I can get the physical query for BI Answers request.
    Thanks
    S

    hi,
    Logging Levels
    Level 0
    No logging.
    Level 1
    Logs the SQL statement issued from the client application.
    Logs elapsed times for query compilation, query execution, query cache processing, and back-end database processing.
    Logs the query status (success, failure, termination, or timeout). Logs the user ID, session ID, and request ID for each query.
    Level 2
    Logs everything logged in Level 1.
    Additionally, for each query, logs the repository name, business model name, presentation catalog (called Subject Area in Answers) name, SQL for the queries issued against physical databases, queries issued against the cache, number of rows returned from each query against a physical database and from queries issued against the cache, and the number of rows returned to the client application.
    Level 3
    Logs everything logged in Level 2.
    Additionally, adds a log entry for the logical query plan, when a query that was supposed to seed the cache was not inserted into the cache, when existing cache entries are purged to make room for the current query, and when the attempt to update the exact match hit detector fails.
    Do not select this level without the assistance of Technical Support.
    Level 4
    Logs everything logged in Level 3.
    Additionally, logs the query execution plan. Do not select this level without the assistance of Technical Support.
    Level 5
    Logs everything logged in Level 4.
    Additionally, logs intermediate row counts at various points in the execution plan. Do not select this level without the assistance of Technical Support.
    Level 6 and 7
    Reserved for future use.
    Hope this helps,
    cheers,
    vineeth

  • What is the diff b/w logical query and physical query?

    Thanks In advance

    In OBIEE terms the logical query is how you query the BI Server, the Presentation services sends logical SQL to the BI Server, you can also write your own using JDBC , pull from BI Server using ODI etc.
    The BI Server engine takes this logical query and writes (a number of) phyiscal querie(s) to satisfy the logical request, depeninding on how your BMM and Physical layer is setup. There are a number of rules the BI Server evaluates before deciding the most appropriate Physical query to generate, rules include Physical Joins, Aggregate tales / Hierarchy levels and so on.
    Hope this helps,
    Good luck with interview :-)
    Alastair

Maybe you are looking for