What is temporal join  in infoset

what is temporal join  in infoset?

Dear Viswnadha,
Description of a specific kind of InfoProvider: InfoSet describes data sources that are defined as a rule as joins of DataStore objects, standard InfoCubes  and/or InfoObjects (characteristics with master data). If one of the InfoObjects contained in the join is a time-dependent characteristic, the join is a time-dependent or temporal join.
An InfoSet is a semantic layer over the data sources.
Unlike the classic InfoSet, an InfoSet is a BI-specific view of data.
Please refer to link:
http://help.sap.com/saphelp_nw04s/helpdata/en/ed/084e3ce0f9fe3fe10000000a114084/content.htm
Best Regards,
Tim
SAP Business One Forums Team

Similar Messages

  • What are the joins availabe in infosets pls explain

    hi all,
    what are the joins availabe in infosets pls explain each joins with an example.
    thanxs in advance
    hari

    Hi Hari,
       there are
    Outer join
    some records will come as an output even if no records matches from the two tables while comparasion depending on if it is left ourter or right outer join. Values frm the base table will always come as an output by base table i mean if it is a left outer join that my base table is left table and so on
    Inner join
    untill and unless there are some records matching in both the tables i wont get any output i mean there shud b some records mathcing than only i will get some result from the inner join
    Temporal Join
    A temporal join is a join that contains at least one time-dependent characteristic or a pseudo time-dependent InfoProvider
    if you join  in  normall way it was called inner join... that means.. it was possible to link only comman fields..(with saem data type fileds)..
       so, if you join ur data targets with inner join means.. it will fetch only common  data from  all the data targets.. where as if you link with  outer join means.. it will fetch all the data even there is no match with data targets..
    thanks
    @jay

  • Hierarchy with Intervals and Temporal Join

    Hi,
      I am loading a hierarchy structure (Time dependant and with Temporal Join and Intervals)
    in the flat file structure for hier loading we have leaf to and leaf from fields which means Page of the hierarchy to and page of the hierarchy from.
    can anyone let me know what is the use of these fields, and the values we have to pass for these fields with an example.
    i haven't come across Hier loading with intervals and termporal join.
    can anyone please help me in this?
    Regards,
    p423168.

    Hi,
    BI Process (Loading Hierarchies from Flat file to BI)
    Go to RSA1
    Create info object for customer as zcust_b5 and activate
    Create info object as zcust_b5 and activate it
    Select the info object and double click on it
    Select the hierarchies tab and select the option with hierarchies
    And select Hierarchies not time dependent
    Click external characteristics in hierarchies
    Select your Infoobjects in the list and pass it and activate it
    After activating the objects we will see tables of hierarchies at maintain Hierarchies
    Create an application component
    Create the transfer rules for the info object and activate (for hierarchies, texts, attributes)
    This screen will show the communication structure.
    After creating the data source at info source level the field attributes are shown in above
    Create an excel sheet with required values and save it in CSV file.
    Uploading the Hierarchy Data into BW
    a) Create Info Package for Hierarchy Upload. Select the Hierarchy to be uploaded
    and also the Full Update button as we are uploading the entire Hierarchy.
    b) There are three update methods for uploading the hierarchy.
    Full Update: For Uploading the entire hierarchy structure
    Insert Sub tree: For appending the hierarchy with new nodes.
    Update Sub tree: For modifying the nodes of the hierarchy.
    Create info package and schedule the data loads
    Select the Hierarchy and name it before scheduling
    Schedule and Start the data loads
    After creating the info package of the info object the above screen shows the initial hierarchy maintenance
    Hierarchy is done successfully by extracting data from flat file.
    time dependent :
    a) For making the hierarchy time dependent select the u2018Time-Dependent Hierarchy structureu2019 radio button and activate the info object ZSREP
    b) In the transfer structure there will be 2 more additional fields date from and date to for the time dependent nodes.
    c) Consider that Sales Representative u2018SREP2u2019 was in England up to 31/12/1995 and moved to USA
    d) Flat file structure for the above hierarchy is shown below . It contains two extra columns Date-to and Date-from.
    e) In the info-package Update tab , select Fixed Time interval radio button and give start date as 01/01/1000 and End date as 31/12/9999 so that all nodes are uploaded.
    f) Upload the hierarchy data from flat-file to BW.
    g) Display the loaded hierarchy.
    Regards
    Sudheer
    Edited by: SUDHEER on Dec 30, 2008 12:52 PM

  • Temporal Join Hierarchies

    Hi,
    I am currently working on BW HR reporting and in that context temporal join of hierarchies seems relevant for reporting organizational assignment.
    Three questions:
    1. I can see that temporal join of hierarchies must be enabled on infoobject level, e.g. on 0ORGUNIT. Will it afterwards be necessary to enable it on hierachy or query level? We do not want to get in a situation where just enabling temporal join of hierarchies on infoobject level affects existing hierarchies or reports based on this infoobject.
    2. To what degree will performance be affected?
    3. Will temporal join of hierarchies work in both BW 3.5 and BI 7 reporting environments? (We have done a technical upgrade to BI7 but still using BW 3.5 queries / web templates)
    Appreciate any input on this!
    thanks,
    Ørnulf Andresen

    Dear Ørnulf,
    1.  Besides enabling it on InfoObject level, you also have to specify settings in the query designer (in the properties of the query).
    2. Performance will be affected, because the hierarchy could be larger than with a single key date. If necessary you can also increase the hierarchy buffer (notes exist).
    3. For using temporal hierarchy join, you must make the settings in the Query Designer 7.0. But the query can be used in 3.x templates
    Kind regards,
    Luc Boodts

  • What is the Join condition between mtl_system_items_b and mtl_onhand_quantities_detail

    Hi,
    What is the Join condition between mtl_system_items_b and mtl_onhand_quantities_detail?
    Thanks & Regards,
    Hari Babu

    Please see the query in (Consolidate Onhand Quantity /Sum Quantity Zero in MTL_ONHAND_QUANTITIES_DETAIL (MOQD) / Concurrent Program Consolidate Inventory Onhand Quantities / Datafix for 0 Quantity Displayed For Finished Goods (Doc ID 353345.1)), is shows how to join those 2 tables.
    http://etrm.oracle.com
    Thanks,
    Hussein

  • Suppres the validity period in a time dep hierarchy with a temporal join

    Dear all,
    With our customer we have an reporting presentation issue that we cannot solve. Can you please help us with a solution?
    It is a hierachy display problem in a report.
    We present a time dependent hierarchy structure with a temporal join. This is to have the postings in the correct periods of the hierarchy. A characteristic of this hierarchy is the validity period. This validity period is default displayed in the report. This cannot be suppressed in the query designer. Is there a way to suppress this? This is a wish form the customer.
    Can you please help us with a sloution?
    Thanks in advance.

    Ondrej,
    Please refer to the below post, it is helpful.
    Re: BI HR Structural Authorizations
    Also, refer to the below document. It is old but provides very useful steps to be followed.
    [http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/business-intelligence/a-c/bw_hr%20authorization%20-%20asap%20for%20bw%20accelerator]
    Update your findings.
    -Mann

  • What is the Join Between structures (sdpartnerlist) and (vbak or komv )

    Hi Dear ,
    can anyone tell me that  " what is the  Join Between structures (sdpartnerlist) and (vbak or komv ) "
    or how can i join these structures .

    Please do your own research before asking others.
    Thread locked.
    Thomas

  • What is left join /right join / out join/ inner join/please give example!

    what is left join /right join / out join/ inner join/please give example!
    thanks

    Maybe these examples will give you an idea...
    SQL> select * from t1;
            ID
             1
             2
             3
             4
    SQL> select * from t2;
            ID
             3
             4
             5
             6
    -- LEFT OUTER JOIN
    SQL> select t1.id, t2.id
      2  from t1 LEFT OUTER JOIN t2 ON (t1.id = t2.id);
            ID         ID
             3          3
             4          4
             1
             2
    -- RIGHT OUTER JOIN
    SQL> select t1.id, t2.id
      2  from t1 RIGHT OUTER JOIN t2 ON (t1.id = t2.id);
            ID         ID
             3          3
             4          4
                        6
                        5
    -- LEFT JOIN (SAME AS LEFT OUTER JOIN)
    SQL> ed
    Wrote file afiedt.buf
      1  select t1.id, t2.id
      2* from t1 LEFT JOIN t2 ON (t1.id = t2.id)
    SQL> /
            ID         ID
             3          3
             4          4
             1
             2
    -- RIGHT JOIN (SAME AS RIGHT OUTER JOIN)
    SQL> ed
    Wrote file afiedt.buf
      1  select t1.id, t2.id
      2* from t1 RIGHT JOIN t2 ON (t1.id = t2.id)
    SQL> /
            ID         ID
             3          3
             4          4
                        6
                        5
    -- INNER JOIN (REGULAR JOIN)
    SQL> ed
    Wrote file afiedt.buf
      1  select t1.id, t2.id
      2* from t1 INNER JOIN t2 ON (t1.id = t2.id)
    SQL> /
            ID         ID
             3          3
             4          4
    -- FULL OUTER JOIN
    SQL> ed
    Wrote file afiedt.buf
      1  select t1.id, t2.id
      2* from t1 FULL OUTER JOIN t2 ON (t1.id = t2.id)
    SQL> /
            ID         ID
             3          3
             4          4
             1
             2
                        6
                        5
    6 rows selected.
    SQL>

  • Temporal Join

    Hi gurus,
      Can anyone explain me in detail about the temporal join in the hierarchy.
    thx in advance.

    Hi........
    Use of Temporal Join :
    The temporal join of time-dependent hierarchies allows you to view the leaves within a hierarchy under two (or more) nodes, depending on the validity period (attribute of the characteristic value).
    To use this function you have to select the indicator for the "Use temporal hierarchy join" option. You make this setting in InfoObject maintenance on the "Hierarchy" tab page.
    http://help.sap.com/saphelp_nw04s/helpdata/en/11/723c3b35703079e10000000a114084/content.htm
    Check these links :
    http://help.sap.com/saphelp_erp2004/helpdata/en/11/723c3b35703079e10000000a114084/content.htm
    http://help.sap.com/saphelp_nw04s/helpdata/en/03/eca042bde0c611e10000000a1550b0/frameset.htm
    Hope this helps you.........
    Thanks == Points as per SDN..........;)
    Regards,
    Debjani..........
    Edited by: Debjani  Mukherjee on Oct 1, 2008 12:43 PM
    Edited by: Debjani  Mukherjee on Oct 1, 2008 12:44 PM

  • Inner join and outer  join in infosets

    hi everyone,
    i have a doubt in infosets...
    when and why we use inner and outer joins(right outer join and left outer join) for infoset
    please give a real time scenario........
    Thanks in advance.
    Bye.

    Hello,
    Inner join:
    For example, the requirement is to show all sales documents where you have delivery exists. In this case, you join both sales ods and delivery ods in a infoset as inner join. This will match the record against the reference documents and pull only matched records.  
    Outer Join:
    Suppose you want to pull all billing/invoice details along with their FI documents related data in a report. Assume that always there might be a situation that invoice exists but not posted to FI, however, you want to have all billing documents details either it has FI document or not. In this case, you link both Billing data and FI document data in a outer join.  This will pull all invoices data either FI document exists or not.   Other words, you want to show one side of data always but adding additional details from differenent source if data exists.
    Hope, it clarifies your doubt. Let me know if any questions.
    Thanks
    Viswa

  • FULL OUTER JOIN In InfoSet

    Hi, all
    Is it possible to make FULL OUTER JOIN in BI InfoSet?
    If no, another question - is it possible to switch base InfoProvider? I have an InfoSet with InfoCube1 and DSO1 which I can outer join. I want to outer join InfoCube1 , not DSO1 that's why I need to switch them in the InfoSet.

    Hi,
       In BI 7.0 Infoset has given chance to include an Info cube also,maximum you can include 2 info Cubes only in a infoset.
    check the below link which helps you in understanding of the join conditions so that you can apply to your scenario.
    http://help.sap.com/saphelp_nw2004s/helpdata/en/f1/713c3b35703079e10000000a114084/content.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/67/7e4b3eaf72561ee10000000a114084/content.htm
    Regards,
    Praveena.

  • BI 7.0 Left outer join in Infoset

    Hi Everybody,
    I am using BI 7.0 and have two cubes in my Infoset.
    How do we set left outer join option in Infoset.
    Thanks
    Shilpa

    Look at  <a href="http://help.sap.com/saphelp_nw2004s/helpdata/EN/05/7ce2416149c717e10000000a155106/frameset.htm">this</a> page. Note the text: <i>For performance reasons, you cannot define an InfoCube as the right operand of a left outer join.</i> Hope this helps...

  • What are the joins are available in abap.

    Hi all,
    What are all the joins are avaialble in abap. Can anyone explain me with examples.
    thanxs in advance
    hari

    Hi,
    There are two types of JOINS
    INNER JOINS and OUTERJOINS
    In the case of INNER JOIN only the records from tables for which the JOIN condition is met are retrieved.
    In the case of OUTER JOIN you will get all the fields that are there in the LEFT table irrespective of the join condition.
    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.
    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.
    Regards,
    Priyanka.

  • What happened to JOIN SMOOTH? (It's gone?!?)

    Title says it all.
    I've searched around for where it went. I used to use it ALL the time. This elimination of this long-standing feature is just SLOWING ME DOWN.  :-(
    What's the work-around, without having to go select another tool and try to match the previous position of the control points after joining as a CORNER?
    Thanks for any help.

    Have a look here:
    http://forums.adobe.com/message/3162884

  • What is HASH JOIN ANTI

    Hi ,
    From my explain plan i see HASH JOIN ANTI .
    what arises to this join in my select query ?
    select * from ( select * from tbl1 where not exists (select * from tbl2 where tbl1.col1 = tbl2.col1) jj
    where not exist (select * from tbl3 where  jj.col1 = tbl3.col1))i think it's the dbl not exists that cause this hash join anti
    but what impact will this type of join has on my query performance ?
    tks & rdgs

    Hi ,
    but i tot when using SELECT where xx in ( ) or XX NOT in ( ) then it'll for every single record then it would perform the select query within the IN ( ) or NOT IN ( )
    wherelse EXISTS or NOT EXISTS will actually do prelisting and then compare from there onwards ?
    tks & rdgs

Maybe you are looking for