OBIEE Issue - Physical Query not picking cascaded Conditions

In one the OBIEE Reports, I have given a set of NOT LIKE conditions as below:
Session Name is not LIKE (pattern match) '%AUDIT%'
AND Session Name is not LIKE (pattern match) '%audit%'
AND Session Name is not LIKE (pattern match) '%Audit%'
But when we refresh the report, it filters only records which uses AUDIT keyword as part of Session Names. When I checked the session log (attached for reference), I found that though logical table query takes those three conditions, while firing against database Physical Query contains condition only for AUDIT wild card as filter. Whether there is any limitation applied on using NOT LIKE conditions or is it a bug or the way the conditions are sequenced is wrong (in OBIEE sense).

Thanks buddy. Though this workaround will solve the issue, I am curious to know why OBIEE behaves such a way. Its peculier to see OBIEE admits all 3 conditions in logical query where the Physical query skips few of the conditions in session log itself.

Similar Messages

Service entry Sheet does not pick any Condition charges From Service PO

Hi All
Service entry Sheet does not pick any Condition charges From Service PO. What could be the reason ?

HI,
Please check Sap note 381030
Along with other thing It says
"Delivery costs are generally not supported in external services management and in case
of blanket purchase orders, item category D or B. Instead of representing delivery
costs via conditions, in case of service documents, freight costs and other, SAP
recommends to add in additional service lines."
So that is the reason you are not getting those account entry in the time of service entry sheet
Use another service line with text ( or service master) for the additional costs as suggested by SAP
Hope it clarifies

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

Service PO is not picking the condition type defined for services

Hi Friends,
I am trying to create a PO for services.. but in conditions tab..the system is picking standard PO pricing procedure. It is not picking the service Pricing procedure MS0000. request your help in understanding the issue.
Also the PO is picking the Standard PO release strategy, but not the release startegy define for service..
thank you.
Kireeti

Hi Kireeti,
Your condition schemes for services probably have been modified. Please check
schemes MS0000 and MS0001 in your customizing. For a correct price
determination it is important that for example condition type PRS
is in the first position, further the settings for the flag
'Condition determined manually' should'nt be altered.
Actually the standard schema looks like:
4 0 PRS Total Price                       X 5
5 1 PRS0 General Price Compon             X
5 3 PRS1 Percentage of Wage               X
5 5 PRS2 Overheads                        X
5 7 PRS3 Misc Price Component             X
13 0 KR01 Header Discount                 X
14 0 KZ01 Header Surcharge                X
Could you please change your schema and retest?.
Best Regards,
Arminda Jack

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

Commission Query not picking up payment on Account linked later

Hi Experts,
I created a query for a Client who need to pay Sales Commission to Sales Employees. This report must show only the Invoices that was Paid.
The Query works fine, exept that it will not pick up the following Payments: When they makie a Incoming Payment on Account and then later link it to an Invoice via the Internal Reconciliation screen.
SELECT T0.[DocNum] AS 'Incoming Payment', T0.[DocDate] AS ' Incoming Payment Date', T0.[CardCode], T0.[CardName], T3.[SlpName], T3.[Commission], T1.[DocNum] AS 'Invoice Number', T2.[OpenSum] AS 'Invoice Line Amounts', T2.[OpenSum] * T3.[Commission] / 100 AS 'Commission Amount'
FROM ORCT T0 INNER JOIN OINV T1 ON T0.DocEntry = T1.ReceiptNum INNER JOIN INV1 T2 ON T1.DocEntry = T2.DocEntry INNER JOIN OSLP T3 ON T1.SlpCode = T3.SlpCode
WHERE T0.[DocDate] >=[%0] AND T0.[DocDate] <=[%1]
How can I get these Invoices that was linked to a Payment to also show in this query?
Thanks,
Marli

I know that this is an old post, but in case someone else wants to use this code I wanted to point out that this code assumes that only invoices are included in payments. If other types such as deposits or credits are included in the payment, then you will get the wrong results.
Need to change the link to OINV slightly to check the document type for Invoices
JOIN
OINV T1 ON T1.DocEntry = T4.DocEntry AND T4.InvType = 13 -- AR Invoice Hdr
Then need to do this same for the other possible document types.

PO having Item Category u0091Pu0092 or u0091Qu0092 price not picking from Condition Record

Hi Guru,
Purchase order having Item Category P or Q Price should pick from the condition type.
Where my condition type against on material and WBS based on this Price will be fixed.
Now I create the PO for same, which the price was not picking from the Condition Record.
Please help on this.
Thanks
Muthukumar

The condition record was created and is being picked up in the calculation. Also, I am now testing with a material that does not have a PIR created, so the PIR does have an impact on my current results.
My current test has results as follows: condition P101 = Std. Cost (as expect) $100.00; ZUPP = calculated at 5% (as expected) $105.00. However, the Net Price in the PO line item is showing only $100.00, not the $105.00.
A look at table EKPO shows the following: Net Price (NETPR) $100.00; Net Value (NETWR) $100.00 ; Gross Value (BRTWR) $105.00.
Can you tell me what I am missing with this setup?

OBIEE 11g Physical Query changes after Check In

Hi
I am facing a strange issue at a customer's.
They migrated an RPD from 10g to 11.1.1.6.2 using the repository upgrade tool.
Right after the upgrade everything works fine but when we connect online using Admin Tool and perform any change on a business model (even if it's only a Check out / Check in without any modification) the next time we execute a report based on that business model we found that every row of a aggregated column displays the Total SUM.
ie.
*10g result :*
2007     11965297458,356
2008     4610283517,31
2009     278693686490,603
2010     2769503695,204
2011     39282794442,407
2012     11167079772,3594
select T60482.N_ANIOEJERCITACION as c1,
sum(T60804.I_SDO_INI_CREDITO / nullif( 1000, 0)) as c2
from
D_FOP_VN_ESCENARIO T60482,
F_FOP_VN_ESCENARIO T60804
where ( T60482.ID_ESCENARIO = T60804.ID_ESCENARIO )
group by T60482.N_ANIOEJERCITACION
order by c1
*11g result:*
2007 348488645376,239
2008 348488645376,239
2009 348488645376,239
2010 348488645376,239
2011 348488645376,239
2012 348488645376,239
WITH
SAWITH0 AS (select sum(T54445.I_SDO_INI_CREDITO / 1000) as c1
from
F_FOP_VN_ESCENARIO T54445),
SAWITH1 AS (select distinct T54426.N_ANIOEJERCITACION as c1
from
D_FOP_VN_ESCENARIO T54426)
select 0 as c1,
D2.c1 as c2,
D1.c1 as c3
from
SAWITH0 D1,
SAWITH1 D2
order by c2
Has anyone experienced this issue? It would be a great help if someone can give me a hint as to where to check.
I've rebuilt all physical joins, check database properties are set to default, no change.
Thanks

The problem was that the server was updated to patch 11.1.1.6.2. and Administration Tool was 11.1.1.6.0
We downloaded a new Admin tool from patch 14142868.
This solved all our issues.
It struck me as odd that in previous versions it used to have a warning when a repository from an unsopported version was open with Admin Tool, but not in this case.
Regards
Miguel

Query not picking up Cache

Guys
I am probably misunderstanding but would appreciate some explaination.
I have run an OLAP Cache pre-populate Bex Broadcast, which sets up (as I can see in RSRCACHE) a cache setting of:
Fixed Forecast EQ 01.07.2014
Calendar Week EQ 01.2014
Calendar Week EQ 02.2014
Material Group EQ 182
Material Group EQ 183
Material Group EQ 184
So as you can see the OLAP Cache populate variant sets up 2 weeks in alist, and 3 Material Groups in a list.
I then manually run the same query with the following selection:
Fixed Forecast = 01.07.2014
Calendar Week = 01.2014
Material Group = 182
I expected this to use the cache I had populated, but it appears it didn't because I now have a new setting showing in RSRCACHE:
Fixed Forecast EQ 01.07.2014
Calendar Week EQ 01.2014
Material Group EQ 182
Effectively this new cache is a full subset of the pre-populate cache I initially setup.
I want to pre-populate cache for a range of selection that the customer typically does, but there are far too may Week/Material combinations to set each one up individually. Am I setting something wrong?
I also tried the initial cache pre-populate as a range rather than a list, and saw the same behaviour (the only difference being the initial cache used a BT rather than 2 EQ lines.
By the way, globally and for InfoProvider we are set as Cache Mode=1, but this specific uery is using cache mode 4 (this is a test as we are multiple application server environment)
Regards
Simon

I know that this is an old post, but in case someone else wants to use this code I wanted to point out that this code assumes that only invoices are included in payments. If other types such as deposits or credits are included in the payment, then you will get the wrong results.
Need to change the link to OINV slightly to check the document type for Invoices
JOIN
OINV T1 ON T1.DocEntry = T4.DocEntry AND T4.InvType = 13 -- AR Invoice Hdr
Then need to do this same for the other possible document types.

Pricing conditions are not picked in print preview of purchase order.

Dear experts
Purchase order was created for imports vendor.
there is difference of amount in purchase order and purchase order print preview.
In purchase order print preview the system is not picking the values of custom value and custom clearing charges.
Import pricing procedure is assigned to vendor.
what else more be checked since the print preview is not picking the conditions , custom value and custom clearing charges.
Any solutions.
Thanks & Regards.
Erfan.

Hi,
Purchase order was created for imports vendor & must have separate documement type for Import Purchase order or new PO output type for import.
Check FORM or PDF/SmartForm Form used for your Import PO out put type for application EF in NACE t.code. Check SmartForm in t.code: SMARTFORMS and see condition types of custom value and custom clearing charges is there or not. Just consultant with ABAP consultant about condition types of custom value and custom clearing charges inclusion in SmartForm.
Regards,
Biju K

Extremely urgent: append cast function in physical query

Experts...
I have a physical query generated with a condition as:
T101123.date1 = T6786678.date2
But, I need that condition to be generated as..
T101123.date1 = CAST(T678878.date2 AS SMALLDATETIME)
Any help..this is an emergency issue..

Deep wrote:
when doing your physical join use a complex join and specify the condition you want to manually.Hi..I tried that..but its taking only DATE for cast....not smalldatetime ..
I tested i for varchar..its taking only CHAR.
Is there any way that it supports smalldateime?

Partner VN is not picking in sales order pricing

Hi
My client requirement is system has to calculate commission amount depend on the combination of sold to party and commission agent(created as vendor).
I defined one condition type by adding access sequence in that access sequence i have maintained one table which is having fields of VKORG, KUNNR, LIFNR. and i have maintained condition records with this combination,
And i maintained VN partner in CMR & it is coming into sales document header and item
Even thou system is not picking the condition value, in analysis system is not picking the vendor number (access not made)
can any body suggest me on this issue
regards
bvdv
Edited by: bvdv on Oct 14, 2008 3:13 PM

Vendor will not be automatically populated in the pricing stuctures. You will have to use exit USEREXIT_PRICING_PREPARE_TKOMK in program MV45AFZZ to fill the pricing communication structure.
Regards,
GSL.

VL10B does not pick NB Po

Hi
Have a strange issue, VL10B does not pick the PO, cross company purchases
The delivery date is more than 60 dyas, while the delivery creation date is within VL10B std time period of 30 days.
Also do not get anything in VETVG
If I put route, VL10B starts picking the PO. And if I now remove the route and rerun VL10B the PO is still picked??
Any advise is appreciated..

Hello,
Make a variant for the transaction VL10B.
Run the transaction VL10B --> Remove all the entries --> Go to --> Variants --> Save as a variant.
Whenever you want to excute this transaction, call the variant from VL10B --> Go to --> Variants --> Get varints --> Execute.
Prase

Physical query issued by Obiee when cache is on is different and slow

When the same report runs in OBIEE 10g and cache is OFF it takes less then 1min to get results. If cache is turned ON physical query issued by Obiee is totally different and it takes 2h to get results. Has anyone experienced this with having cache on that some queries are performing poorly.
Thanks,
Tatjana

We are using BI Apps Order Management and Fulfillment Analytics and all tables are cached anyway. Dimensions used are not that huge up to 40K rows. What should I check when it comes to DB query? As I said is different than one generated when cache is disabled although both have the almost the explain plan.

Re: View physical query issued by Obiee 11g

Guys,
I want to view the physical query generated by the report in OBIEE 11g, but in the logs, i can only see these queries: (Just writing the first line to illustrate)
SELECT
0 s_0,
"Marketing Contact List"."- Account Address"."Billing Abode Name" s_1,
And this query:
RqList distinct
0 as c1 GB,
Account.Billing Abode Name as c2 GB,
Both these queries are NOT the physical ones.
I have the appropriate log level, and even set it manually from the front end, but I'm unable to view the physical query. Please help!

A.Budd,
After running a report in OBIEE, click the Administration Link in the top right corner. New window appears and select "Manage Sessions". Look for the latest time executed that applies to the time you executed your report and click View Logs. Scroll almost to the bottom of the log.
What you are looking for is the generated logic that starts with "*With*"
WITH
SAWITH0 AS (select sum(T443244.AGING030) as c1,
sum(T443244.AGING6190) as c2,
sum(case when T443244.CURRENCYCODE = 'C
Copy the whole logic from WITH to the end of the logic (typically ends with Order By) (not the log) and paste it in your query tool. This is based on the physical layer.
Antexity

OBIEE Issue - Physical Query not picking cascaded Conditions

Similar Messages

Maybe you are looking for