Between Operator in physical join

Hello,
Can we use between operator in physical join. We did that, its successfully checking in, but when we re-open the join, its show in RED color.
So, got doubt, can we use between?
and we have another error
"No fact table exists at the requested level of detail"; what does this error mean
Waiting for reply...
Regards
Kiran

Can we use between operator in physical join. We did that, its successfully checking in, but when we re-open the join, its show in RED color.
So, got doubt, can we use between?When you checkout the rpd object in online mode it would display in red, this is not an error.
"No fact table exists at the requested level of detail"; what does this error meanThis error usually happens if you have not mapped the content level correctly in the logical table source.
Rgds,
Dpka

Similar Messages

How to use BETWEEN Operator in physical layer in OBIEE 11g

Hi Experts,
How do I do the BETWEEN Operator functionality in Physical layer if my requirements is like this?
TABLE_1.COLUMN_1 = TABLE_2 is between COLUMN_2 and COLUMN_3
Below is the syntax for BETWEEN Operator function when I am trying to insert them.
<<expression>> BETWEEN <<Upper Bound>> AND <<Lower Bound>>
Thanks,
Edited by: OBIEE/BIP Forumer on Nov 3, 2012 11:37 PM

Below is an example diagram, as you can see, FACT TABLE have a join (an arrow one) towards TABLE_1 and TABLE_3. AS for the TABLE_3, this table is the one which I implement with the BETWEEN Operators function in Physical Layer. Also, the arrow in FACT TABLE and TABLE_3 is a red one with no arrow head line.
TABLE_2
^
l
l
l
FACT TABLE ---------> TABLE_1
l
l
l
TABLE_3
Edited by: OBIEE/BIP Forumer on Nov 4, 2012 2:33 AM

Between operator is taking as = and = in physical query

Hi,
i am implementing filter in obiee as follows,
calendar date between 01/01/2010 and 01/01/2010
or
calendar date between 01/01/2009 and 01/01/2009
when i executed the query it is showing the above logic in obiee logical query,where as in physical query it is taking as
(T1233290."CALENDAR_DATE" >= DATE '2009-01-01' or T1233290."CALENDAR_DATE" >= DATE '2010-01-01') and (T1233290."CALENDAR_DATE" >= DATE '2009-01-01' or T1233290."CALENDAR_DATE" <= DATE '2010-01-01') and (T1233290."CALENDAR_DATE" >= DATE '2010-01-01' or T1233290."CALENDAR_DATE" <= DATE '2009-01-01') and (T1233290."CALENDAR_DATE" <= DATE '2009-01-01' or T1233290."CALENDAR_DATE" <= DATE '2010-01-01') )
how to get the between operator in physical query.
please help me out in this.

Why are u using the same dates in between option ?

What is the different between Logical complex join and Physical join?

hi,
Do somebody know what is the function different between logical complex join in BMM layer and physical join in physical layer?
Thanks.

Thank you very much1
I understand their differentiation:
In the BMM Complex join (intelligent), means OBI picks the best way from possibly many different ways to join using physical join. FK join forces the same join always, which limits flexibility.

Difference between physical join and logical join

Hi Gurus,
Can anyone tell me what is the difference between physical join and logical join
Thanks,
Chandra

Hi,
A physical join is at the physical layer and defines the join between two physical tables. Logical joins live at the BMM (logical) layer and define a join between two logical tables.
The important differentiation is that at the BMM layer you do not tell the OBIEE server how to do the join, you just tell it that there is a relationship between these two logical entities. When the server comes to this logical join it will use the information in the physical joins and decides how the two logical tables are joined together.
In BMM you use complex joins to establish which logical tables are joined which another, the OBI EE server will go to the physical level to search the physical join to make the query. You can also use physical joins in the BMM to override the join in the physical layer but only in very specific conditions.
If you also set complex join in the physical layer OBI EE won't be able to construct the physical query.
Hope this answers your question.
Award points if helpful.
Thanks,
-Amith.

Physical Joins Difference Between 10G and 11G?

Hi All, I have started using OBIEE 11G. Anybody please let me know is there any difference in applying physical joins in OBIEE 10G and 11G.
I heard that we need to join Fact and Dim tables in reverse way in 11G.
Thanks in Advance.

# Fast-Start Failover for Maximum Performance Mode in a Data Guard Configuration
# Compression of Redo Traffic (Only for Gap Resolution) Over the Network in a Data Guard Configuration
# Real-Time Query Capability of Physical Standby Database
# Fast Role Transitions in a Data Guard Configuration
# Data Guard Integration, Simplification, and Performance
# Dynamic Setting of Oracle Data Guard SQL Apply Parameters
# Enhanced Data Guard Broker Based Management Framework
# Histogram for Redo Transport Response Time in a Data Guard Configuration
# Snapshot Standby
# Strong Authentication for Data Guard Redo Transport
# Enhanced DDL Handling in Oracle Data Guard SQL Apply
# Enhanced Oracle RAC Switchover Support for Logical Standby Databases
# Data Guard Logical Apply Completeness
# Oracle Scheduler Support in Data Guard SQL Apply
# Support Transparent Data Encryption (TDE) with Data Guard SQL Apply
# Support XMLType Data Type (Only CLOB) in Data Guard SQL Apply
# Virtual Private Database (VPD) Support in Data Guard SQL Apply
See Also:
Oracle Data Guard Concepts and Administration for details
Ref. Oracle® Database New Features Guide
11g Release 1 (11.1)
Part Number B28279-01
~ Madrid

Diff between logical and physical file path

Hi ,
Could you please explain difference between logical and physical file path's and their importance in ABAP.
Thanks and regards,
shyla

Hi
The function module FILE_GET_NAME convert a logical path into its corresponding physical path.
The advantage of using logical pathes within your applications is obivous:
If you need to change the physical path you just adjust it within transaction FILE yet no changes are required to your application.
http://help.sap.com/saphelp_erp2005vp/helpdata/en/25/ab3a57df3b11d189fc0000e829fbbd/frameset.htm
The file names that you use in ABAP statements for processing files are physical names. This means that they must be syntactically correct filenames for the operating system under which your R/3 System is running. Once you have created a file from an ABAP program with a particular name and path, you can find the same file using the same name and path at operating system level.
Since the naming conventions for files and paths differ from operating system to operating system, ABAP programs are only portable from one operating system to another if you use the tools described below.
To make programs portable, the R/3 System has a concept of logical filenames and paths. These are linked to physical files and paths. The links are created in special tables, which you can maintain according to your own requirements. In an ABAP program, you can then use the function module FILE_GET_NAME to generate a physical filename from a logical one.
Maintaining platform-independent filenames is part of Customizing. For a full description, choose Tools ® Business Engineer ® Customizing, followed by
Implement. projects ® SAP Reference IMG. On the next screen, choose Basis Components System Administration ® Platform-independent File Names.
For a more detailed description of the function module FILE_GET_NAME, enter its name on the initial screen of the Function Builder and choose Goto Documentation. On the next screen, choose Function module doc.
Another way of maintaining platform-independent filenames is to use the Transaction FILE. The following sections provide an overview of the transaction.
To create a logical filename, choose Logical filename definition, client-independent from the Navigation group box in Transaction FILE, then choose New entries. You define logical filenames
You can either define a logical filename and link it to a logical path (as displayed here), or you can enter the full physical filename in the Physical file field. In the latter case, the logical filename is only valid for one operating system. The rules for entering the complete physical filename are the same as for the definition of the physical path for the logical file. To display further information and a list of reserved words, choose Help.
If you link a logical path to a logical file, the logical file is valid for all syntax groups that have been maintained for that logical path. The filename specified under Physical file replaces the reserved word in the physical paths that are assigned to the logical path. To make the name independent of the operating system, use names that begin with a letter, contain up to 8 letters, and do not contain special characters.
Save your changes.

Logical joins vs Physical joins

Hello,
Can anyone tell me what is the difference between physical joins and logical joins. And how OBI Server treats the joins in relation to the Logical and Physical Layer.
I'm a little confused also with the place to configure the joins, since there is more than one option.
Thanks in advance,
Sofiane

Well actually no. The actual sql fired would depend on both the logical and physical joins. Logical join would be the entry point. Think of it this way. Business Model layer helps you designing a star schema(like a data warehouse) out of your source data. So logical joins are joins that you define on your star schema. But the star schema in itself derives its data from physical layer. So the Physical layer joins would be necessary as well. But if you have a star schema already in your physical layer the physical joins alone would suffice and logical joins are redundant but necessary.
Thanks,
Venkat
http://oraclebizint.wordpress.com

Hi guru's what is the diff between for all entries & joins

hi guru's what is the diff between for all entries & joins

Hi Vasu,
Joins are used to fetch data fast from Database tables:
Tables are joined with the proper key fields to fetch the data properly.
If there are no proper key fields between tables don't use Joins;
Important thing is that don't USE JOINS FOR CLUSTER tableslike BSEG and KONV.
Only use for Transparenmt tables.
You can also use joins for the database VIews to fetch the data.
JOINS
... FROM tabref1 [INNER] JOIN tabref2 ON cond
Effect
The data is to be selected from transparent database tables and/or views determined by tabref1 and tabref2. tabref1 and tabref2 each have the same form as in variant 1 or are themselves Join expressions. The keyword INNER does not have to be specified. The database tables or views determined by tabref1 and tabref2 must be recognized by the ABAP Dictionary.
In a relational data structure, it is quite normal for data that belongs together to be split up across several tables to help the process of standardization (see relational databases). To regroup this information into a database query, you can link tables using the join command. This formulates conditions for the columns in the tables involved. The inner join contains all combinations of lines from the database table determined by tabref1 with lines from the table determined by tabref2, whose values together meet the logical condition (join condition) specified using ON>cond.
Inner join between table 1 and table 2, where column D in both tables in the join condition is set the same:
Table 1 Table 2
A
B
C
D
D
E
F
G
H
a1
b1
c1
1
1
e1
f1
g1
h1
a2
b2
c2
1
3
e2
f2
g2
h2
a3
b3
c3
2
4
e3
f3
g3
h3
a4
b4
c4
3
|--|||--|
Inner Join
A
B
C
D
D
E
F
G
H
a1
b1
c1
1
1
e1
f1
g1
h1
a2
b2
c2
1
1
e1
f1
g1
h1
a4
b4
c4
3
3
e2
f2
g2
h2
|--||||||||--|
Example
Output a list of all flights from Frankfurt to New York between September 10th and 20th, 2001 that are not sold out:
DATA: DATE LIKE SFLIGHT-FLDATE,
CARRID LIKE SFLIGHT-CARRID,
CONNID LIKE SFLIGHT-CONNID.
SELECT FCARRID FCONNID F~FLDATE
INTO (CARRID, CONNID, DATE)
FROM SFLIGHT AS F INNER JOIN SPFLI AS P
ON FCARRID = PCARRID AND
FCONNID = PCONNID
WHERE P~CITYFROM = 'FRANKFURT'
AND P~CITYTO = 'NEW YORK'
AND F~FLDATE BETWEEN '20010910' AND '20010920'
AND FSEATSOCC < FSEATSMAX.
WRITE: / DATE, CARRID, CONNID.
ENDSELECT.
If there are columns with the same name in both tables, you must distinguish between them by prefixing the field descriptor with the table name or a table alias.
Note
In order to determine the result of a SELECT command where the FROM clause contains a join, the database system first creates a temporary table containing the lines that meet the ON condition. The WHERE condition is then applied to the temporary table. It does not matter in an inner join whether the condition is in the ON or WHEREclause. The following example returns the same solution as the previous one.
Example
Output of a list of all flights from Frankfurt to New York between September 10th and 20th, 2001 that are not sold out:
DATA: DATE LIKE SFLIGHT-FLDATE,
CARRID LIKE SFLIGHT-CARRID,
CONNID LIKE SFLIGHT-CONNID.
SELECT FCARRID FCONNID F~FLDATE
INTO (CARRID, CONNID, DATE)
FROM SFLIGHT AS F INNER JOIN SPFLI AS P
ON FCARRID = PCARRID
WHERE FCONNID = PCONNID
AND P~CITYFROM = 'FRANKFURT'
AND P~CITYTO = 'NEW YORK'
AND F~FLDATE BETWEEN '20010910' AND '20010920'
AND FSEATSOCC < FSEATSMAX.
WRITE: / DATE, CARRID, CONNID.
ENDSELECT.
Note
Since not all of the database systems supported by SAP use the standard syntax for ON conditions, the syntax has been restricted. It only allows those joins that produce the same results on all of the supported database systems:
Only a table or view may appear to the right of the JOIN operator, not another join expression.
Only AND is possible in the ON condition as a logical operator.
Each comparison in the ON condition must contain a field from the right-hand table.
If an outer join occurs in the FROM clause, all the ON conditions must contain at least one "real" JOIN condition (a condition that contains a field from tabref1 amd a field from tabref2.
Note
In some cases, '*' may be specified in the SELECT clause, and an internal table or work area is entered into the INTO clause (instead of a list of fields). If so, the fields are written to the target area from left to right in the order in which the tables appear in the FROM clause, according to the structure of each table work area. There can then be gaps between table work areas if you use an Alignment Request. For this reason, you should define the target work area with reference to the types of the database tables, not simply by counting the total number of fields. For an example, see below:
Variant 3
... FROM tabref1 LEFT [OUTER] JOIN tabref2 ON cond
Effect
Selects the data from the transparent database tables and/or views specified in tabref1 and tabref2. tabref1 und tabref2 both have either the same form as in variant 1 or are themselves join expressions. The keyword OUTER can be omitted. The database tables or views specified in tabref1 and tabref2 must be recognized by the ABAP-Dictionary.
In order to determine the result of a SELECT command where the FROM clause contains a left outer join, the database system creates a temporary table containing the lines that meet the ON condition. The remaining fields from the left-hand table (tabref1) are then added to this table, and their corresponding fields from the right-hand table are filled with ZERO values. The system then applies the WHERE condition to the table.
Left outer join between table 1 and table 2 where column D in both tables set the join condition:
Table 1 Table 2
A
B
C
D
D
E
F
G
H
a1
b1
c1
1
1
e1
f1
g1
h1
a2
b2
c2
1
3
e2
f2
g2
h2
a3
b3
c3
2
4
e3
f3
g3
h3
a4
b4
c4
3
|--|||--|
Left Outer Join
A
B
C
D
D
E
F
G
H
a1
b1
c1
1
1
e1
f1
g1
h1
a2
b2
c2
1
1
e1
f1
g1
h1
a3
b3
c3
2
NULL
NULL
NULL
NULL
NULL
a4
b4
c4
3
3
e2
f2
g2
h2
|--||||||||--|
Example
Output a list of all custimers with their bookings for October 15th, 2001:
DATA: CUSTOMER TYPE SCUSTOM,
BOOKING TYPE SBOOK.
SELECT SCUSTOMNAME SCUSTOMPOSTCODE SCUSTOM~CITY
SBOOKFLDATE SBOOKCARRID SBOOKCONNID SBOOKBOOKID
INTO (CUSTOMER-NAME, CUSTOMER-POSTCODE, CUSTOMER-CITY,
BOOKING-FLDATE, BOOKING-CARRID, BOOKING-CONNID,
BOOKING-BOOKID)
FROM SCUSTOM LEFT OUTER JOIN SBOOK
ON SCUSTOMID = SBOOKCUSTOMID AND
SBOOK~FLDATE = '20011015'
ORDER BY SCUSTOMNAME SBOOKFLDATE.
WRITE: / CUSTOMER-NAME, CUSTOMER-POSTCODE, CUSTOMER-CITY,
BOOKING-FLDATE, BOOKING-CARRID, BOOKING-CONNID,
BOOKING-BOOKID.
ENDSELECT.
If there are columns with the same name in both tables, you must distinguish between them by prefixing the field descriptor with the table name or using an alias.
Note
For the resulting set of a SELECT command with a left outer join in the FROM clause, it is generally of crucial importance whether a logical condition is in the ON or WHERE condition. Since not all of the database systems supported by SAP themselves support the standard syntax and semantics of the left outer join, the syntax has been restricted to those cases that return the same solution in all database systems:
Only a table or view may come after the JOIN operator, not another join statement.
The only logical operator allowed in the ON condition is AND.
Each comparison in the ON condition must contain a field from the right-hand table.
Comparisons in the WHERE condition must not contain a field from the right-hand table.
The ON condition must contain at least one "real" JOIN condition (a condition in which a field from tabref1 as well as from tabref2 occurs).
Note
In some cases, '*' may be specivied as the field list in the SELECT clause, and an internal table or work area is entered in the INTO clause (instead of a list of fields). If so, the fields are written to the target area from left to right in the order in which the tables appear in the llen in der FROM clause, according to the structure of each table work area. There can be gaps between the table work areas if you use an Alignment Request. For this reason, you should define the target work area with reference to the types of the database tables, as in the following example (not simply by counting the total number of fields).
Example
Example of a JOIN with more than two tables: Select all flights from Frankfurt to New York between September 10th and 20th, 2001 where there are available places, and display the name of the airline.
DATA: BEGIN OF WA,
FLIGHT TYPE SFLIGHT,
PFLI TYPE SPFLI,
CARR TYPE SCARR,
END OF WA.
SELECT * INTO WA
FROM ( SFLIGHT AS F INNER JOIN SPFLI AS P
ON FCARRID = PCARRID AND
FCONNID = PCONNID )
INNER JOIN SCARR AS C
ON FCARRID = CCARRID
WHERE P~CITYFROM = 'FRANKFURT'
AND P~CITYTO = 'NEW YORK'
AND F~FLDATE BETWEEN '20010910' AND '20010920'
AND FSEATSOCC < FSEATSMAX.
WRITE: / WA-CARR-CARRNAME, WA-FLIGHT-FLDATE, WA-FLIGHT-CARRID,
WA-FLIGHT-CONNID.
ENDSELECT.
And for all entries,
this will help u.
use of FOR ALL ENTRIES:
1. INNER JOIN
DBTAB1 <----
> DBTAB2
It is used to JOIN two DATABASE tables
having some COMMON fields.
2. Whereas
For All Entries,
DBTAB1 <----
> ITAB1
is not at all related to two DATABASE tables.
It is related to INTERNAL table.
3. If we want to fetch data
from some DBTABLE1
but we want to fetch
for only some records
which are contained in some internal table,
then we use for alll entries.
1. simple example of for all entries.
2. NOTE THAT
In for all entries,
it is NOT necessary to use TWO DBTABLES.
(as against JOIN)
3. use this program (just copy paste)
it will fetch data
from T001
FOR ONLY TWO COMPANIES (as mentioned in itab)
4
REPORT abc.
DATA : BEGIN OF itab OCCURS 0,
bukrs LIKE t001-bukrs,
END OF itab.
DATA : t001 LIKE TABLE OF t001 WITH HEADER LINE.
itab-bukrs = '1000'.
APPEND itab.
itab-bukrs = '1100'.
APPEND itab.
SELECT * FROM t001
INTO TABLE t001
FOR ALL ENTRIES IN itab
WHERE bukrs = itab-bukrs.
LOOP AT t001.
WRITE :/ t001-bukrs.
ENDLOOP.
cheers,
Hema.

Unable to do Physical Join in rpd

Hi
I tried to join table Ra_Customer_trx_all and OE_order_header_all but the join condition is to_char(OE_order_header_all .order_number) = Ra_Customer_trx_all .Attribute6
can i use this join condition in physical layer..Because in physical join we staraightway give the join condition but here we are changing the column type and then using the join.
I am using OBIEE 11g
thanks in advance for the help
Debo

Hi
Thanks for the solution in physical join but when i simply join the two tables in the business layer the logical join is not pulling any data..Do we need to do something else to do the logical join between those tables
Regards
Debo

Use of complex join in BMM and Physical Join in Physical layer ?

Hi All ,
Why we need to use complex join in BMM layer not the Physical Join ?
Why we need to use Physical Join in Physical layer not Complex join ?
thanks in advance

Hi,
A physical join is at the physical layer and defines the join between two physical tables.
Logical joins live at the BMM (logical) layer and define a join between two logical tables.
The important differentiation is that at the BMM layer you do not tell the OBIEE server how to do the join,
you just tell it that there is a relationship between these two logical entities.
when the server comes to this logical join it will use the information in the physical joins and decides how the two logical tables are joined together.
thanks,
pramod.

Diff bw complex join and physical join

hi all
Can sumbody explain me the all the differences between complex join and physical join in the admin tool
Thanks
Shobhit

Hi,
Suggest you to go through this link. It may be helpful in detail.
http://st-urriculum.oracle.com/obe/fmw/bi/biee/r1013/bi_admin/biadmin.html
Thanks,
Vengatesh.

Error while using between operator with sql stmts in obiee 11g analytics

Hi All,
when I try to use between operator with two select queries in OBIEE 11g analytics, I'm getting the below error:
Error Codes: YQCO4T56:OPR4ONWY:U9IM8TAC:OI2DL65P
Location: saw.views.evc.activate, saw.httpserver.processrequest, saw.rpc.server.responder, saw.rpc.server, saw.rpc.server.handleConnection, saw.rpc.server.dispatch, saw.threadpool.socketrpcserver, saw.threads
Odbc driver returned an error (SQLExecDirectW).
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 27002] Near <select>: Syntax error [nQSError: 26012] . (HY000)
can anyone help me out in resolving this issue.

Hi All,
Thank u all for ur replies, but I dint the exact solution for what I'm searching for.
If I use the condition as
"WHERE "Workforce Budget"."Used Budget Amount" BETWEEN MAX("Workforce Budget"."Total Eligible Salaries") AND MAX("Workforce Budget"."Published Worksheet Budget Amount"",
all the data will be grouped with the two columns which I'm considering in the condition.
my actual requirement with this query is to get the required date from a table to generate the report either as daily or weekly or monthly report. If I use repository variables, variables are not getting refreshed until I regenerate the server(which I should not do in my project). Hence I have created a table to hold weekly start and end dates and monthly start and end dates to pass the value to the actual report using between operator.
please could anyone help me on this, my release date is fast approaching.

Diff between logical and physical page ?

hi
what exactly difference between logical and physical pages?
where to set page size in report designer?
after seting paper size in report designer can i readjust in print dialogue box?
which is will be effected?
please explain

A logical page can contain several physical pages. Assume you want to create a format which is larger then your printer is able to print, then you can define a logical size, which contains n pages horizontally and m pages vertically.
To set the page size for your report have a look at the properties in the main section of your paper layout.
Regards
Rainer

Difference in between operator in oracle 8i and 9i version

Is their any difference between the functioning of Between operator in 8i and 9i?

I agree that there should be no differences in behavior of the between operator from version 8.1 to 9.2. If you can run the same query with the same data on the two versions and get different results then you would need to look for version specific, possibly platform specific, bugs on metalink.
HTH -- Mark D Powell --

Between Operator in physical join

Similar Messages

Maybe you are looking for