topic Re: join command in Application Development and Automation Discussions

join command

Former Member — Tue, 03 Jul 2007 09:17:42 GMT

i want to select all items from table say table1, 2 items from another table say table2, 1 item from another table say table3 using the joiin command. how can i achieve this

Re: join command

Former Member — Tue, 03 Jul 2007 09:19:24 GMT

See how these three tables are related...based on that, you can form the join conditions...

Regards

Raj

Re: join command

S0025444845 — Tue, 03 Jul 2007 09:20:27 GMT

Hi,

take help of the below code

SELECT a_{mblnr a}cpudt a_{bldat a}usnam a~xblnr

b_{bwart b}matnr b_{werks b}insmk b~lifnr

c~ekgrp

INTO CORRESPONDING FIELDS OF TABLE it_final

FROM mkpf AS a INNER JOIN

mseg AS b ON a_{mblnr = b}mblnr

INNER JOIN ekko AS c ON b_{ebeln = c}ebeln

WHERE a~mblnr IN s_mblnr AND

a~cpudt IN s_cpudt AND

a~usnam IN s_usnam AND

a~xblnr IN s_xblnr AND

b~matnr IN s_matnr AND

b~werks IN s_werks AND

b~lgort IN s_lgort AND

b~charg IN s_charg AND

b~lifnr IN s_lifnr AND

b~ps_psp_pnr IN s_wbs AND

b~bwart IN s_bwart AND

b~insmk IN s_insmk AND

c~ekgrp IN s_ekgrp.

regards,

sudha

Re: join command

Former Member — Tue, 03 Jul 2007 09:20:56 GMT

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 c_{carrname p}connid f~fldate

INTO CORRESPONDING FIELDS OF TABLE itab

FROM ( ( scarr AS c

INNER JOIN spfli AS p ON p_{carrid = c}carrid

AND p~cityfrom = p_cityfr

AND p~cityto = p_cityto )

INNER JOIN sflight AS f ON f_{carrid = p}carrid

AND f_{connid = p}connid ).

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 s_{carrid s}carrname p~connid

INTO CORRESPONDING FIELDS OF TABLE itab

FROM scarr AS s

LEFT OUTER JOIN spfli AS p ON s_{carrid = p}carrid

AND p~cityfrom = p_cityfr.

LOOP AT itab INTO wa.

IF wa-connid = '0000'.

WRITE: / wa-carrid, wa-carrname.

ENDIF.

ENDLOOP.

Reward points for useful Answers

Regards

Anji

Re: join command

Former Member — Tue, 03 Jul 2007 09:21:56 GMT

hi,

Let the tables be A,B,C.

select a_{f1 a}f2 a_{f3 a}f4 b_{f1 b}f2 c~f1

from( ekko as a join ekpo as b) join eket as c

into table itab

where a_{f1 = b}f1

and b_{f1 = c}f1.

Re: join command

Former Member — Tue, 03 Jul 2007 09:22:32 GMT

Hi,

HAVE A LOOK .......

REPORT demo_select_inner_join.

DATA: BEGIN OF wa,

carrid TYPE spfli-carrid,

connid TYPE spfli-connid,

fldate TYPE sflight-fldate,

bookid TYPE sbook-bookid,

END OF wa,

itab LIKE SORTED TABLE OF wa

WITH UNIQUE KEY carrid connid fldate bookid.

SELECT

p~carrid

p~connid

f~fldate

b~bookid

INTO CORRESPONDING FIELDS OF TABLE itab

FROM ( ( spfli AS p

INNER JOIN sflight AS f ON p_{carrid = f}carrid AND

p_{connid = f}connid )

INNER JOIN sbook AS b ON b_{carrid = f}carrid AND

b_{connid = f}connid AND

b_{fldate = f}fldate )

WHERE p~cityfrom = 'FRANKFURT' AND

p~cityto = 'NEW YORK' AND

f_{seatsmax > f}seatsocc.

LOOP AT itab INTO wa.

AT NEW fldate.

WRITE: / wa-carrid, wa-connid, wa-fldate.

ENDAT.

WRITE / wa-bookid.

ENDLOOP.

Regards,

Padmam.

Re: join command

Former Member — Tue, 03 Jul 2007 09:29:08 GMT

Hi in addition to Ms.Roja's thread,

Let the tables be A,B,C.

select a_{f1 a}f2 a_{f3 a}f4 b_{f1 b}f2 c~f1

from( ekko as a join ekpo as b) join eket as c

into table itab

where a_{f1 = b}f1

and b_{f1 = c}f1.