SQL Trace

Former Member — Mon, 02 Apr 2007 10:40:57 GMT

can anybody tell me what the below trace means

SELECT DISTINCT T_02 . "BUKRS" , T_02 . "WAERS" , T_02 . "PRCTR" , T_01

. "KOSTL" , T_00 . "KSTAR" , T_00 . "VERSN" , T_00 . "GJAHR" , T_00 .

"WKG001" , T_00 . "WKG002" , T_00 . "WKG003" , T_00 . "WKG004" , T_00 .

"WKG005" , T_00 . "WKG006" , T_00 . "WKG007" , T_00 . "WKG008" , T_00 .

"WKG009" , T_00 . "WKG010" , T_00 . "WKG011" , T_00 . "WKG012" , T_00 .

"WKG013" , T_00 . "WKG014" , T_00 . "WKG015" , T_00 . "WKG016" FROM

"COSS" T_00 , "CSSL" T_01 , "CSKS" T_02 WHERE ( T_01 . "MANDT" = ? AND

T_00 . "OBJNR" = T_01 . "OBJNR" ) AND ( T_02 . "MANDT" = ? AND T_01 .

"KOSTL" = T_02 . "KOSTL" ) AND T_00 . "MANDT" = ? AND T_00 . "LEDNR" = ?

AND T_00 . "VERSN" = ? AND T_01 . "KOSTL" IN ( ? , ? , ? , ? , ? , ? , ?

, ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ?

Re: SQL Trace

Former Member — Mon, 02 Apr 2007 10:55:54 GMT

hi,

It is nothing but the select statement in your report.

There is an inner join in this select.

T_02(CSKS), T_01(CSSL), T_00(COSS) are different tables.

Regards,

sailaja.

Re: SQL Trace

Former Member — Mon, 02 Apr 2007 11:24:43 GMT

In your SQL Trace you are getting distinct fields from three tables coss,

cssl ,csks witjh aliases as t_01,t_02,t_03 respectively and applying a join condition on the three tables and going for a condition using fields of three tables

and these are prefixed by their alias names to find field from which table in select query.

chk this for inner join on 3 tables

<a href="http://www.sap-img.com/abap/inner-joins.htm">http://www.sap-img.com/abap/inner-joins.htm</a>

<b>example.</b>

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

--- -

-- --

--- -

|---|-|--|---|

\ /

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 F_{CARRID F}CONNID F~FLDATE

INTO (CARRID, CONNID, DATE)

FROM SFLIGHT AS F INNER JOIN SPFLI AS P

ON F_{CARRID = P}CARRID AND

F_{CONNID = P}CONNID

WHERE P~CITYFROM = 'FRANKFURT'

AND P~CITYTO = 'NEW YORK'

AND F~FLDATE BETWEEN '20010910' AND '20010920'

AND F_{SEATSOCC < F}SEATSMAX.

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 F_{CARRID F}CONNID F~FLDATE

INTO (CARRID, CONNID, DATE)

FROM SFLIGHT AS F INNER JOIN SPFLI AS P

ON F_{CARRID = P}CARRID

WHERE F_{CONNID = P}CONNID

AND P~CITYFROM = 'FRANKFURT'

AND P~CITYTO = 'NEW YORK'

AND F~FLDATE BETWEEN '20010910' AND '20010920'

AND F_{SEATSOCC < F}SEATSMAX.

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 | f 1| 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 SCUSTOM_{NAME SCUSTOM}POSTCODE SCUSTOM~CITY

SBOOK_{FLDATE SBOOK}CARRID SBOOK_{CONNID SBOOK}BOOKID

INTO (CUSTOMER-NAME, CUSTOMER-POSTCODE, CUSTOMER-CITY,

BOOKING-FLDATE, BOOKING-CARRID, BOOKING-CONNID,

BOOKING-BOOKID)

FROM SCUSTOM LEFT OUTER JOIN SBOOK

ON SCUSTOM_{ID = SBOOK}CUSTOMID AND

SBOOK~FLDATE = '20011015'

ORDER BY SCUSTOM_{NAME SBOOK}FLDATE.

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 F_{CARRID = P}CARRID AND

F_{CONNID = P}CONNID )

INNER JOIN SCARR AS C

ON F_{CARRID = C}CARRID

WHERE P~CITYFROM = 'FRANKFURT'

AND P~CITYTO = 'NEW YORK'

AND F~FLDATE BETWEEN '20010910' AND '20010920'

AND F_{SEATSOCC < F}SEATSMAX.

WRITE: / WA-CARR-CARRNAME, WA-FLIGHT-FLDATE, WA-FLIGHT-CARRID,

WA-FLIGHT-CONNID.

ENDSELECT.

Hope this is helpful.

Reward points if helpful.

Regards

Satish .

topic Re: SQL Trace in Application Development and Automation Discussions

SQL Trace

Re: SQL Trace

Re: SQL Trace

Re: SQL Trace

Re: SQL Trace

Re: SQL Trace