Join with 2 itab

Hi expert
I don't able to write this abap code. I have 2 itab and I shoul add lt_ausp into lt_equi
lt_equi
EQUNR                               SERNR
000000000010001803     000000000000008795
000000000010001805     000000000000001233
lt_ausp
Cx                 OBJECT                              ATINN           ATWRT
1     000000000010001803     0000001620     AAAAA
2     000000000010001803     0000001624     BBBBBB
3     000000000010001803     0000001651     SREWREWR
4     000000000010001803     0000001658      EREWR
5     000000000010001803     0000001703     18
1     000000000010001805     0000001620     ZZZZZZZZZ
2     000000000010001805     0000001624     REWREW
3     000000000010001805     0000001651     STANDARD
4     000000000010001805     0000001659     STANDARD
5     000000000010001805     0000001704     4-1/2-8
this is my abap code
LOOP AT lt_ausp.
      READ TABLE lt_equi WITH KEY equnr = lt_ausp-objek BINARY SEARCH.
      IF sy-subrc = 0.
        lt_equi-lv_count = lt_ausp-lv_count.
        lt_equi-atinn    = lt_ausp-atinn.
        lt_equi-atwrt    = lt_ausp-atwrt.
        APPEND lt_equi .
      ENDIF.
    ENDLOOP.
but doens't work.
Edited by: Giorgio Vecchiato on Oct 29, 2009 3:31 PM

hi Harini
this is the structure of table
DATA: BEGIN OF lt_equi OCCURS 0,
equnr     LIKE equi-equnr,
equnr50   LIKE ausp-objek,
sernr     LIKE equi-sernr,
objnr     LIKE equi-objnr,
parvw     LIKE ihpa-parvw,
parnr     LIKE ihpa-parnr,
mganr     LIKE bgmkobj-mganr, "
gwldt     LIKE bgmkobj-gwldt,
cuobj     LIKE equi-cuobj,
atinn     LIKE cawn-atinn,
lv_count TYPE sy-index,
atwrt     LIKE ausp-atwrt,
END OF lt_equi.
DATA: BEGIN OF lt_ausp OCCURS 0,
lv_count TYPE sy-index VALUE 1,
objek     LIKE ausp-objek,
atinn     LIKE ausp-atinn,
atwrt     LIKE ausp-atwrt,
END OF lt_ausp.

Similar Messages

All Joins with Example

Hi Experts,
Pls let me know what are all joins available in ABAP??
One example program for each for better understanding...
Any useful inputs on this will be highly rewarded.
Thanks in advance
Rgds ~ Lakshmiraj

Hi,
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.
Syntax
... [(] {dbtab_left [AS tabalias_left]} | join
{[INNER] JOIN}|{LEFT [OUTER] JOIN}
{dbtab_right [AS tabalias_right] ON join_cond} [)] ... .
Effect
The join syntax represents a recursively nestable join expression. A join expression consists of a left-hand and a right- hand side, which are joined either by means of [INNER] JOIN or LEFT [OUTER] JOIN . Depending on the type of join, a join expression can be either an inner ( INNER) or an outer (LEFT OUTER) join. Every join expression can be enclosed in round brackets. If a join expression is used, the SELECT command circumvents SAP buffering.
On the left-hand side, either a single database table, a view dbtab_left, or a join expression join can be specified. On the right-hand side, a single database table or a view dbtab_right as well as join conditions join_cond can be specified after ON. In this way, a maximum of 24 join expressions that join 25 database tables or views with each other can be specified after FROM.
AS can be used to specify an alternative table name tabalias for each of the specified database table names or for every view. A database table or a view can occur multiple times within a join expression and, in this case, have various alternative names.
The syntax of the join conditions join_cond is the same as that of the sql_cond conditions after the addition WHERE, with the following differences:
At least one comparison must be specified after ON.
Individual comparisons may be joined using AND only.
All comparisons must contain a column in the database table or the view dbtab_right on the right-hand side as an operand.
The following language elements may not be used: BETWEEN, LIKE, IN.
No sub-queries may be used.
For outer joins, only equality comparisons (=, EQ) are possible.
If an outer join occurs after FROM, the join condition of every join expression must contain at least one comparison between columns on the left-hand and the right-hand side.
In outer joins, all comparisons that contain columns as operands in the database table or the view dbtab_right on the right-hand side must be specified in the corresponding join condition. In the WHERE condition of the same SELECT command, these columns are not allowed as operands.
Resulting set for inner join
The inner join joins the columns of every selected line on the left- hand side with the columns of all lines on the right-hand side that jointly fulfil the join_cond condition. A line in the resulting set is created for every such line on the right-hand side. The content of the column on the left-hand side may be duplicated in this case. If none of the lines on the right-hand side fulfils the join_cond condition, no line is created in the resulting set.
Resulting set for outer join
The outer join basically creates the same resulting set as the inner join, with the difference that at least one line is created in the resulting set for every selected line on the left-hand side, even if no line on the right-hand side fulfils the join_cond condition. The columns on the right-hand side that do not fulfil the join_cond condition are filled with null values.
Example
Join the columns carrname, connid, fldate of the database tables scarr, spfli and sflight by means of two inner joins. A list is created of the flights from p_cityfr to p_cityto. Alternative names are used for every table.
PARAMETERS: p_cityfr TYPE spfli-cityfrom,
p_cityto TYPE spfli-cityto.
DATA: BEGIN OF wa,
fldate TYPE sflight-fldate,
carrname TYPE scarr-carrname,
connid TYPE spfli-connid,
END OF wa.
DATA itab LIKE SORTED TABLE OF wa
WITH UNIQUE KEY fldate carrname connid.
SELECT ccarrname pconnid f~fldate
INTO CORRESPONDING FIELDS OF TABLE itab
FROM ( ( scarr AS c
INNER JOIN spfli AS p ON pcarrid = ccarrid
AND p~cityfrom = p_cityfr
AND p~cityto = p_cityto )
INNER JOIN sflight AS f ON fcarrid = pcarrid
AND fconnid = pconnid ).
LOOP AT itab INTO wa.
WRITE: / wa-fldate, wa-carrname, wa-connid.
ENDLOOP.
Example
Join the columns carrid, carrname and connid of the database tables scarr and spfli using an outer join. The column connid is set to the null value for all flights that do not fly from p_cityfr. This null value is then converted to the appropriate initial value when it is transferred to the assigned data object. The LOOP returns all airlines that do not fly from p_cityfr.
PARAMETERS p_cityfr TYPE spfli-cityfrom.
DATA: BEGIN OF wa,
carrid TYPE scarr-carrid,
carrname TYPE scarr-carrname,
connid TYPE spfli-connid,
END OF wa,
itab LIKE SORTED TABLE OF wa
WITH NON-UNIQUE KEY carrid.
SELECT scarrid scarrname p~connid
INTO CORRESPONDING FIELDS OF TABLE itab
FROM scarr AS s
LEFT OUTER JOIN spfli AS p ON scarrid = pcarrid
AND p~cityfrom = p_cityfr.
LOOP AT itab INTO wa.
IF wa-connid = '0000'.
WRITE: / wa-carrid, wa-carrname.
ENDIF.
ENDLOOP.
Cheers,
vasavi.
kindly reward if helpful.

How to join two ITAB

Hai
         i have created an program using ALV and i had created two internal tables namely ITAB and ITAB1.But i wasn't unable to get an output.so i like to know how to join two ITAB in ALV.

MAhesh,
Check this ex:
ITAB1 is having fields "A","B", "C".
ITAB2 is having fields "A","D", "E".
Create i_final internal table to have all fields of 2 internal tables.
i_final is having "A","B","C","D","E".
SORT itab1 ,itab2 by A
LOOP AT ITAB1.
READ TABLE itab2 WITH KEY a = itab1-a BINARY
                                                              SEARCH.
   IF SY-SUBRC EQ 0.
     MOVE : itab1-a TO i_final-a,
                  itab1-b TO i_final-b,
                  itab1-c TO i_final-c,
                  itab2-d TO i_final-d,
                  itab2-e TO i_final-e.
    APPEND i_final.
   ENDIF.
ENDLOOP.
Don't forget to reward if useful.....

Coupling INNER JOIN with FOR ALL ENTRIES statement

Hi All,
 I am coupling INNER JOIN with FOR ALL ENTRIES statement .....
 Would you please highlight its implications ?? Is it a best practise ?
 Is it advicable to use MULTIPLE INNER JOINs with a FOR ALL ENTRIES ???
 SORT itab BY matnr.
 IF NOT itab[] IS INITIAL.
 SELECT epmatnr epebeln ep~ebelp
 epwerks epmenge ep~netpr
 ekps_psp_pnr ebbelnr eb~menge
 INTO TABLE iekpo
 FROM ekpo AS ep
 INNER JOIN ekkn AS ek
 ON ekebeln = epebeln
 AND ekebelp = epebelp
 INNER JOIN ekbe AS eb
 ON ebebeln = epebeln
 AND ebebelp = epebelp
 AND eb~bwart = '101'
 FOR ALL ENTRIES IN itab
 WHERE ep~matnr = itab-matnr.
 IF sy-subrc EQ 0.
 SORT iekpo BY matnr werks.
 LOOP AT itab ASSIGNING <itab>.
 READ TABLE iekpo WITH KEY matnr = <itab>-matnr
 werks = <itab>-werks
 BINARY SEARCH.
 IF sy-subrc EQ 0.
 MOVE iekpo-matnr TO itab1-matnr.
 MOVE iekpo-ebeln TO itab1-ebeln.
 MOVE iekpo-ebelp TO itab1-ebelp.
 MOVE iekpo-netpr TO itab1-poprice.
 MOVE iekpo-werks TO itab1-werks.
 MOVE iekpo-menge TO itab1-menge1.
 MOVE iekpo-menge1 TO itab1-menge2.
 MOVE iekpo-belnr TO itab1-belnr.
 MOVE iekpo-ps_psp_pnr TO itab1-pspel.
 MOVE <itab>-pspel TO itab1-tpspel.
 MOVE <itab>-sobkz TO itab1-sobkz.
 MOVE <itab>-fo_qty TO itab1-fo_qty.
 MOVE <itab>-schgt TO itab1-schgt.
 MOVE <itab>-postp TO itab1-postp.
 MOVE <itab>-beskz TO itab1-beskz.
 pend_qty = iekpo-menge1 - iekpo-menge2.
 MOVE pend_qty TO itab1-pending.
 APPEND itab1.
 pend_qty = 0.
 ENDIF.
 ENDLOOP.
 ENDIF.
 ENDIF.
ENDIF.
Regards
Jaman
Edited by: ABAP Techie on Sep 15, 2008 12:39 PM
Edited by: ABAP Techie on Sep 15, 2008 12:41 PM

best practise ... don't know ... it is allowed and o.k.
If possible you should of coourse to have no FOR ALL ENTRIES at all !
Joins, there is no general rule, check indexes etc.
The first SORT, I don't that it help for anything, use it together with the delete adjacent duplicates if you expect duplicates in the driver table.
o.k., it can help, if there is a loop afterwards and an append inside, because the new table itab1 is then sorted.
Siegfried

Problem with outer join with filter on join column

Hi,
In physical layer I have one dimension and two facts, and there's an outer join between the facts.
dim_DATE ,
fact_1 ,
fact_2
Joins:
dim_DATE inner join fact_1 on dim_DATE.DATE = fact_1.DATE
fact_1 left outer join fact_2 on fact_1.DATE = fact_2.DATE and fact_1.SOME_ID = fact_2.SOME_ID
When I run a report with a date as a filter, OBIEE executes "optimized" physical SQL:
select fact1.X, fact2.Y
from
Fact_1 left outer join on fact_1.DATE = fact_2.DATE and fact_1.SOME_ID = fact_2.SOME_ID
where Fact_1.DATE = TO_DATE('2009-05-28' , 'YYYY-MM-DD' )
and Fact_2.DATE = TO_DATE('2009-05-28' , 'YYYY-MM-DD')
The filter on Fact_2.DATE effectively replaces outer join with inner.
Is there a way to disable this "optimization", which is actually very good for inner joins, but doesn't allow outer joins?
Thanks in advance,
Alex
Edited by: AM_1 on Aug 11, 2009 8:20 AM

If you want to perform a Fact-based partitioning with OBIEE (two fact with the same dimension), you have to :
* create in your physical layer for each fact table the joins with the dimension
* create in the Business Model layer ONE star schema with ONE logical fact table containing the columns of your two physical fact table
In this way when you choose minimal one column of your fact1 and one column of your fact2, OBIEE will perform two query against each fact table/dimension, join them with an OUTER JOIN and your problem will disappear.
Cheers
Nico

How Can We Tune the Joins with "OR" Caluse ?

Hi
We've identified one Query in one of Our PL/SQL Stored Procedure which is taking huge time to fetch the records. I have simulated the problem as shown below. The problem Is, How can i tune the Jions with "OR" Clause. i have tried replacing them with Exists Caluse, But the Performance was not much was expected.
CREATE TABLE TEST
(ID NUMBER VDATE DATE );
BEGIN
FOR i IN 1 .. 100000 LOOP
    INSERT INTO TEST
    VALUES
      (i, TO_DATE(TRUNC(DBMS_RANDOM.VALUE(2452641, 2452641 + 364)), 'J'));
    IF MOD(i, 1000) = 0 THEN
      COMMIT;
    END IF;
END LOOP;
END;
CREATE TABLE RTEST1 ( ID NUMBER, VMONTH NUMBER );
INSERT INTO RTEST1
SELECT ID, TO_NUMBER(TO_CHAR(VDATE,'MM'))
FROM TEST ;
CREATE TABLE RTEST2 ( ID NUMBER, VMONTH NUMBER );
INSERT INTO RTEST2
SELECT ID, TO_NUMBER(TO_CHAR(VDATE,'MM'))
FROM TEST;
CREATE INDEX RTEST1_IDX2 ON RTEST1(VMONTH)
CREATE INDEX RTEST2_IDX1 ON RTEST2(VMONTH)
ALTER TABLE RTEST1 ADD CONSTRAINT RTEST1_PK PRIMARY KEY (ID)
ALTER TABLE RTEST2 ADD CONSTRAINT RTEST2_PK PRIMARY KEY (ID)
SELECT A.ID, B.VMONTH
FROM RTEST1 A , RTEST2 B
WHERE A.ID = B.ID
AND ( (A.ID = B.VMONTH) OR ( B.ID = A.VMONTH ) )
BEGIN
DBMS_STATS.gather_table_stats(ownname => 'PHASE30DEV',tabname => 'RTEST1');
DBMS_STATS.gather_table_stats(ownname => 'PHASE30DEV',tabname => 'RTEST2');
DBMS_STATS.gather_index_stats(ownname => 'PHASE30DEV',indname => 'RTEST1_IDX1');
DBMS_STATS.gather_index_stats(ownname => 'PHASE30DEV',indname => 'RTEST2_IDX2');
DBMS_STATS.gather_index_stats(ownname => 'PHASE30DEV',indname => 'RTEST1_IDX2');
DBMS_STATS.gather_index_stats(ownname => 'PHASE30DEV',indname => 'RTEST2_IDX1');
END; Pls suggest !!!!!!! How can I tune the Joins with "OR" Clause.
Regards
RJ

I don't like it, but you could use a hint:
SQL>r
1 SELECT A.ID, B.VMONTH
2 FROM RTEST1 A , RTEST2 B
3 WHERE A.ID = B.ID
4* AND ( (A.ID = B.VMONTH) OR ( B.ID = A.VMONTH ) )
Execution Plan
   0      SELECT STATEMENT Optimizer=CHOOSE (Cost=94 Card=2 Bytes=28)
   1    0   TABLE ACCESS (BY INDEX ROWID) OF 'RTEST2' (Cost=94 Card=1 Bytes=7)
   2    1     NESTED LOOPS (Cost=94 Card=2 Bytes=28)
   3    2       TABLE ACCESS (FULL) OF 'RTEST1' (Cost=20 Card=100000 Bytes=700000)
   4    2       BITMAP CONVERSION (TO ROWIDS)
   5    4         BITMAP AND
   6    5           BITMAP CONVERSION (FROM ROWIDS)
   7    6             INDEX (RANGE SCAN) OF 'RTEST2_PK' (UNIQUE)
   8    5           BITMAP OR
   9    8             BITMAP CONVERSION (FROM ROWIDS)
10    9               INDEX (RANGE SCAN) OF 'RTEST2_IDX1' (NON-UNIQUE)
11    8             BITMAP CONVERSION (FROM ROWIDS)
12   11               INDEX (RANGE SCAN) OF 'RTEST2_PK' (UNIQUE)
Statistics
          0 recursive calls
          0 db block gets
     300332 consistent gets
          0 physical reads
          0 redo size
        252 bytes sent via SQL*Net to client
        235 bytes received via SQL*Net from client
          2 SQL*Net roundtrips to/from client
          0 sorts (memory)
          0 sorts (disk)
          2 rows processed
SQL>SELECT /*+ ordered use_hash(b) */ A.ID, B.VMONTH
2    FROM RTEST1 A, RTEST2 B
3   WHERE A.ID = B.ID AND(A.ID = B.VMONTH OR B.ID = A.VMONTH)
4 ;
Execution Plan
   0      SELECT STATEMENT Optimizer=CHOOSE (Cost=175 Card=2 Bytes=28)
   1    0   HASH JOIN (Cost=175 Card=2 Bytes=28)
   2    1     TABLE ACCESS (FULL) OF 'RTEST1' (Cost=20 Card=100000 Bytes=700000)
   3    1     TABLE ACCESS (FULL) OF 'RTEST2' (Cost=20 Card=100000 Bytes=700000)
Statistics
          9 recursive calls
          0 db block gets
        256 consistent gets
        156 physical reads
          0 redo size
        252 bytes sent via SQL*Net to client
        235 bytes received via SQL*Net from client
          2 SQL*Net roundtrips to/from client
          0 sorts (memory)
          0 sorts (disk)
          2 rows processed

Outer Join with Where Clause in LTS

HI all,
I have a requirement like this in ANSI SQL:
select p1.product_id, p1.product_name, p2.product_group
from product p1 left outer join product_group p2 on p1.product_id = p2.product_id
and p2.product_group = 'NEW'
In Regular SQL:
select p1.product_id, p1.product_name, p2.product_group
from product p1, product_group p2
WHERE p1.product_id *= p2.product_id and p2.product_group = 'NEW'
In OBIEE, I am using a left outer join between these two in Logical table Source, and also, Gave
p2.product_group = 'NEW' in WHERE clause of LTS.
This doesn't seem to solve purpose.
Do you have any idea how to convert WHERE clause in physical query that OBIEE is generating to something like
product p1 left outer join product_group p2 on p1.product_id = p2.product_id AND p2.product_group = 'NEW'
I am using Version 10.1.3.4.1
Creating an Opaque view would be my last option though.

Hello
I have read your post and the responses as well. and I understand that you have issues with the Outer Join with where Clause in LTS.
Try this solution which worked for me (using your example ) -
1. In the Physical Layer created a Complex join between PRODUCT and PRODUCT_GROUP tables and use this join relationship :
PRODUCT.PROD_ID = PRODUCT_GROUP.PROD_ID AND PRODUCT_GROUP.GROUP_NAME = 'MECHANICAL'
2. In the General Tab of PRODUCT table LTS add PRODUCT_GROUP table and select Join Type as Left Outer Join.
3. Check Consistency and make sure there are no errors .
when you run a request you should see the following query generated -
select distinct T26908.PROD_ID as c1,
     T26908.PROD_NAME as c2,
     T26912.GROUP_NAME as c3
from
     PRODUCT T26908 left outer join PRODUCT_GROUP T26912 On T26908.PROD_ID = T26912.PROD_ID and T26912.GROUP_NAME = 'MECHANICAL'
order by c1, c2, c3
Hope this works for you. If it does please mark this response as 'Correct' .
Good Luck.

TS1398 I cannot join with a nearby Wi-Fi network. We have wi-fi in our apt. and our IBM laptop is connecting with no problem; but, when I try to use my iPod touch, the wi-fi is locked and asks for a password. I do not know it.

How do I join with the network that is in our apt? The iPod asks for a password and I do not have one. What to do?

You have to enter the correct password to connect.
Ask the person who setup the router for the password.

Self join with fact table in Obie 10G

I am a newbie to obiee.I have a development requirement as follows-
I need to find supervisors designation with the existing star RPD design. explanation is below
                                                    DIM_Designation(Desig_Wid)
                                                  |(Row_wid)
                                                  |
DIM_EMPLOYEE--------WORKER_FACT------------DIM_Supervisor
(Row_Wid)-----------------(Employee_Wid)
                                  (Supervisor_Wid)------------(Row_Wid)
3 dimension is joined to fact to get employee, his supervisor and designation of employee. now i want to get the supervisor's designation? how is it possible? already employee and supervisor dimension is same W_employee_d table joined with fact as alias DIM_EMPLOYEE and DIM_SUPERVISOR. how to do self join with fact to get supervisor's designation. i do not have any supervisor_desig_wid in fact table. any help is deeply appreciated.

Yes,Duplicate the fact table create a primary key on the newly fact table alias dimension table.So you can ur data modelling as usual.

Maximum number of tables that can be outer joined with one table in a query

Hi All,
Iam new to sql, so can you please let me know What is the maximum number of tables that can be outer joined with one table in a query?
Thanks,
Srini

srinu2 wrote:
Iam new to sql, so can you please let me know What is the maximum number of tables that can be outer joined with one table in a query?
There is no limit to the number of tables you can outer join as long as you join them correctly.
SQL> with a as
2      (
3      select 1 id, 2 b_key, 3 c_key from dual union all
4      select 2 id, 1 b_key, 4 c_key from dual union all
5      select 3 id, 3 b_key, 1 c_key from dual union all
6      select 4 id, 4 b_key, 2 c_key from dual
7      ),
8      b as
9      (
10      select 1 id, 1 c_key2 from dual union all
11      select 2 id, 5 c_key2 from dual union all
12      select 3 id, 3 c_key2 from dual union all
13      select 4 id, 2 c_key2 from dual
14      ),
15      c as
16      (
17      select 1 key1, 1 key2, '1-1' dta from dual union all
18      select 1 key1, 2 key2, '1-2' dta from dual union all
19      select 1 key1, 3 key2, '1-3' dta from dual union all
20      select 1 key1, 4 key2, '1-4' dta from dual union all
21      select 2 key1, 1 key2, '2-1' dta from dual union all
22      select 2 key1, 2 key2, '2-2' dta from dual union all
23      select 2 key1, 3 key2, '2-3' dta from dual union all
24      select 2 key1, 4 key2, '2-4' dta from dual union all
25      select 3 key1, 1 key2, '3-1' dta from dual union all
26      select 3 key1, 2 key2, '3-2' dta from dual union all
27      select 3 key1, 3 key2, '3-3' dta from dual union all
28      select 3 key1, 4 key2, '3-4' dta from dual union all
29      select 4 key1, 1 key2, '4-1' dta from dual union all
30      select 4 key1, 2 key2, '4-2' dta from dual union all
31      select 4 key1, 3 key2, '4-3' dta from dual union all
32      select 4 key1, 4 key2, '4-4' dta from dual
33      )
34 select d.a_id, d.b_id, c.key1 as c_key1, c.key2 as c_key3, c.dta
35 from
36      c,
37      (
38      select
39          a.id as a_id, b.id as b_id, a.c_key, b.c_key2
40      from a, b
41      where a.b_key = b.id
42      ) d
43 where d.c_key = c.key1 (+)
44 and   d.c_key2 = c.key2 (+);
      A_ID       B_ID     C_KEY1     C_KEY3 DTA
         3          3          1          3 1-3
         4          4          2          2 2-2
         2          1          4          1 4-1
         1          2
SQL>

Replacing a inner join with for all entries

Hi Team,
   In a already developed program I am replacing a inner join with select query follow up with for-all-entris and passing the data to final internal table but in both the case the result should be same then only my replacement will be correct. But my no records in both cases differs. This happening because when i am selecting data from first data base table is 32 lines. then I am doing fo-all-entries moving all the duplicate entries then the no records are four. but in final internal table i am looping the first internal table. So in final internal table the no of records are 32. But in inner join query the records are 16.So please let me know how resolve this issue?
Thanks and REgards
Deepa

Hi Thomas,
Thanks for ur suggestion.
The solved that in below.
In select query I did not change anything The way I had written the code was correct.
I think many of us know how to write that how to make the performance better in that way.
I made the change when I transfered the to final internal table.
The original Inner join code:
select a~field1 a~field2 a~field3 b~field2 b~field3 b~field4
           from dbtab1 as a inner join dbtab2 as b
          on a~field1 = b~field1 into it_final where
          a~field1 in s_field1. [Field1 in both the table are key field]
Before code:
Sort itab1 by key-fields.
sort itab2 by keyfields.
loop at itab1 into wa1.
move: wa1-field1 to wa_final-field1,
           wa1-field2 to wa_final-field2,
           wa1-field3 to wa_final-field3.
read table itab2 into wa2 witk key field1 = wa1-field1 binary search.
if sy-subrc = 0.
move : wa2-field2 to wa_final-field4,
             wa2-field3 to wa_final-field5,
             wa2-field4 to wa_final-field6.
append wa_final to it_final.
endif.
Clear : wa1, wa2, wa_final.
endloop.
In this case if the one key fieild value is not present there in second internal table but its there in first internal table still it will read that row with 2nd internal values having zeroes. Normally what does not happen in inner join case if the key field value will same in both the case ,then that will fetch only those rows.
Changed Code
loop at itab1 into wa1.
read table itab2 into wa2 witk key field1 = wa1-field1 binary search.
if sy-subrc = 0.
move: wa1-field1 to wa_final-field1,
           wa1-field2 to wa_final-field2,
           wa1-field3 to wa_final-field3.
move : wa2-field2 to wa_final-field4,
             wa2-field3 to wa_final-field5,
             wa2-field4 to wa_final-field6.
append wa_final to it_final.
endif.
Clear : wa1, wa2, wa_final.
endloop.
In this case the values will read to final internal table if both key field matches.
With Regards
Deepa

INNER JOIN with FOR ALL ENTRIES IN Performance ?

I am using following the following Select using Inner join with For All Entries in.
 SELECT kebeln kebelp kvbeln kvbelp
 FROM ekkn AS k INNER JOIN ekbe AS b ON kebeln = bebeln
 AND kebelp = bebelp
 INTO TABLE gi_purchase
 FOR ALL ENTRIES
 IN gi_sales
 WHERE k~mandt EQ sy-mandt
 AND k~vbeln EQ gi_sales-vbeln
 AND k~vbelp EQ gi_sales-posnr
 AND b~budat EQ p_date.
If i am not doing inner join then I will have to do 2 select with for all entries in on ekkn and ekbe tables and then compare them.
I want to know which one has better performance
Inner join with for all entries in
 or
2 Selects with for all entries in

the join is almost aways faster:
<a href="/people/rob.burbank/blog/2007/03/19/joins-vs-for-all-entries--which-performs-better">JOINS vs. FOR ALL ENTRIES - Which Performs Better?</a>
<a href="http://blogs.ittoolbox.com/sap/db2/archives/for-all-entries-vs-db2-join-8912">FOR ALL ENTRIES vs DB2 JOIN</a>
Rob

Inner Join with For All Entries - Performance ?

I am using following the following Select using Inner join with For All Entries in.
 SELECT kebeln kebelp kvbeln kvbelp
 FROM ekkn AS k INNER JOIN ekbe AS b ON kebeln = bebeln
 AND kebelp = bebelp
 INTO TABLE gi_purchase
 FOR ALL ENTRIES
 IN gi_sales
 WHERE k~mandt EQ sy-mandt
 AND k~vbeln EQ gi_sales-vbeln
 AND k~vbelp EQ gi_sales-posnr
 AND b~budat EQ p_date.
If i am not doing inner join then I will have to do 2 select with for all entries in on ekkn and ekbe tables and then compare them.
I want to know which one has better performance
Inner join with for all entries in
 or
2 Selects with for all entries in

An Inner Join with for all entries should be done if you add this....
IF NOT gi_sales[] IS INITIAL.
SELECT k~ebeln k~ebelp k~vbeln k~vbelp
FROM ekkn AS k INNER JOIN ekbe AS b ON k~ebeln = b~ebeln
AND k~ebelp = b~ebelp
INTO TABLE gi_purchase
FOR ALL ENTRIES
IN gi_sales
WHERE k~mandt EQ sy-mandt
AND k~vbeln EQ gi_sales-vbeln
AND k~vbelp EQ gi_sales-posnr
AND b~budat EQ p_date.
ENDIF.
Also, while you use an index or the complete key for the SELECT, your not going to suffer from lack of performance -;)
Greetings,
Blag.

Oracle 8i, left join with conditional

Coming from the MySQL world, I'm trying to do a left join with a
condition:
select c.givenname,c.surname,c.userid,r.letternr
from cand c,responses r
where (c.userid=r.username(+))
and
c.activeprofile=1
No problem whatsoever.
If there is no corresponding "response" in R for a given
candidate, I get a NULL return for R.letternr.
However, there is a flag in R, called "VISIBLE" that I wish to
use to mean "Don't count this entry in R". R.VISIBLE=0 means
that the response is not active/present/visible/valid.
Am I making any sense? :-)

If you don't want to display a row with a null value for
r.letternr when r.visible = 0, then:
SELECT     c.givenname,
           c.surname,
           c.userid,
           r.letternr
FROM       cand c,
           responses r
WHERE      c.userid = r.username (+)
AND        c.activeprofile = 1
AND        r.visible != 0
Or, if you do want to display a row with a null value for
r.letternr when r.visible = 0, then:
SELECT     c.givenname,
           c.surname,
           c.userid,
           r.letternr
FROM       cand c,
           responses r
WHERE      c.userid = r.username (+)
AND        c.activeprofile = 1
AND        r.visible (+) != 0

SQL JOIN with BPM sql component

Hello friends.
How to use SQL JOIN with BPM sql component?
The tables objects are created but the joined tables belong to different sql components .
I tried something like that, but a error "table doesn't exist" occours.
Ex:
for each element in
SELECT imuImovelCd
FROM IMOVEIS_URBANOS,
Integracao.FGLP.IMOVEIS_PRE_EDITAIS
WHERE IMOVEIS_URBANOS.imuImovelCd = Integracao.FGLP.IMOVEIS_PRE_EDITAIS.ipeImuCd
AND Integracao.FGLP.IMOVEIS_PRE_EDITAIS.ipePedNr = 1
AND Integracao.FGLP.IMOVEIS_PRE_EDITAIS.ipePedAa = 2008
do
extend this.imoveis using cdImovel = element.imuimovelcd,
                              nrImovel = call(DEC_ENDERECO, codimovel : element.imuimovelcd, tipoimovel : 1)
end
Edited by: user9008295 on 26/01/2010 05:19

ok, ok you are right.
When I try use SQL Statement to make a JOIN with 2 tables on different sql objects, BPM returns "table dosn't exists".
So.... I change my code. I dont know if this is the best way to do, but... i hope u, or everyone, can help me to do a best work.
This code works fine.
for each element in
SELECT ipeImuCd
     FROM Integracao.FGLP.IMOVEIS_PRE_EDITAIS
     WHERE Integracao.FGLP.IMOVEIS_PRE_EDITAIS.ipePedNr = 1
     AND Integracao.FGLP.IMOVEIS_PRE_EDITAIS.ipePedAa = 2008
do
     for each element2 in
          SELECT imuImovelDv
          FROM IMOVEIS_URBANOS
          WHERE imuImovelCd = element.ipeImuCd
     do
          extend this.imoveis using cdDvImovel = String(element2.imuImovelDv),
                                        cdImovel = Decimal(element.ipeImuCd),
                                        endereco = call(DEC_ENDERECO, codimovel : element.ipeImuCd, tipoimovel : 1)
     end
end
Thx a lot!!!

Outer join With a constant value

Hi all,
In one of query i have found out that the outer join with a constant value like
to_currency(+)='USD'
to_currency is a column name in a table.can any one please explain this outer join condtn.
Thanks in advance
Senthil

Hallo,
if you write var (+) = constant
var can be equal constant, and also can be null
Compare these 2 queries
select e.* from scott.emp e, scott.dept d
where e.deptno = d.deptno(+)
and d.deptno(+) = 10EMPNO ENAME JOB MGR HIREDATE SAL COMM DEPTNO
7369     SMITH      CLERK      7902     17-Dez-1980     800          20
7499     ALLEN      SALESMAN      7698     20-Feb-1981     1600     300     30
7521     WARD      SALESMAN      7698     22-Feb-1981     1250     500     30
7566     JONES      MANAGER      7839     2-Apr-1981     2975          20
7654     MARTIN      SALESMAN      7698     28-Sep-1981     1250     1400     30
7698     BLAKE      MANAGER      7839     1-Mai-1981     2850          30
7782     CLARK      MANAGER      7839     9-Jun-1981     2450          10
7788     SCOTT      ANALYST      7566     19-Apr-1987     3000          20
7839     KING      PRESIDENT           17-Nov-1981     5000          10
7844     TURNER      SALESMAN      7698     8-Sep-1981     1500     0     30
7876     ADAMS      CLERK      7788     23-Mai-1987     1100          20
7900     JAMES      CLERK      7698     3-Dez-1981     950          30
7902     FORD      ANALYST      7566     3-Dez-1981     3000          20
7934     MILLER      CLERK      7782     23-Jan-1982     1300          10
select e.* from scott.emp e, scott.dept d
where e.deptno = d.deptno(+)
and d.deptno = 10 EMPNO ENAME JOB MGR HIREDATE SAL COMM DEPTNO
7782     CLARK      MANAGER      7839     9-Jun-1981     2450          10
7839     KING      PRESIDENT           17-Nov-1981     5000          10
7934     MILLER      CLERK      7782     23-Jan-1982     1300          10
As you can see, this (+) is very important
Regards
Dmytro

Join with 2 itab

Similar Messages

Maybe you are looking for