Diff between  filter , RKF,Condition

Hi experts,
I have doubt abt the diff between  filter , RKF,Condition.
I know the definitions. when executing the reports. how it exactly doing in backend.
    like is there any SQL query is executing behind to display the results.

Hi Venkatdas,
From the SQL perspective:
Filter criteria you specified in the "Filter" directly goes in WHERE clause.
e.g. If you have sales order data, if you only want to display sales org 1000 data.
SELECT * FROM ORDERS
WHERE sales_org = '1000'
In case of "FILTERS" you can only apply criteria on "Characteristic", you can't apply criteria on keyfigure value.
Where as in case of "_Restricted Key Figure_", instead of limiting the entire data set you will be limiting a keyfigure based on a characteristic value.
e.g. If the requirement is to show the data by division by current year vs. prior year comparison in columns.
Current Year Prior year
Division
10 $104,000.00 $8,320.00
20 $138,666.67 $124,800.00
30 $242,666.67 $169,866.67
SELECT  DIVISION, SUM( DECODE(YEAR, 2010, SALES$s, 0) ) , SUM( DECODE(YEAR,2009, SALES$s, 0) )
FROM ORDERS
GROUP BY DIVISION.
As you can see incase of "Restricted Keyfigure" entire data set is not restricted; instead a value of the output is restricted based on a characteristic value.
Condition, no data is limited at database level. From the SQL perspective there would not be any data restrictions. Once the data comes to OLAP layer, you would apply a condition to only show data meets a criteria.
e.g. Display only top 10 materials.
SELECT MATERIAL SUM( SALES$s)
FROM ORDERS
WHERE YEAR = 2010
GROUP BY MATERIAL.
The above statement would output all the material and the corresponding sales in year 2010. Once these rows comes to OLAP layer, CONDITION will kick-in and sort the data by SALES$s and only display to 10 materials.
Cheers,
Thanks
Vasu Sattenapalli

Similar Messages

  • Diff. between header & item condition

    Pls let me know the diff. between header & item condtion in SD.
    How to define header & item seprately

    Hi Prem,
    You can make a Condition Type a Header Condition by checking the "Header Condition" check box in
    SPRO -> Sales & Distribution -> Basic Functions -> Pricing -> Pricing Control -> Define Condition Types.
    In turn, it can be made an Item Condition by checking the
    "Item Condition" check box.
    In an Sales Order doc you can assign a header condition by choosing the "Display document header details" button at the top right of the screen, then move to "Conditions" tab and Add the Header Condition type to the list of Conditions.
    Similarly, item conditions can be set by selecting the line item and choosing the "Item Conditions" button and adding the Item Condition type.
    Hope it answers your query completely.
    regards,
    Raj

  • Diff. between Tax Code and Condition Types

    Hi,
    What is the diff. between Tax Code and Condition Type???
    Why we maintain Tax Codes under Invoice Tab in PO, when Condition Types are available for Calculation Procedure...???
    Please guide..

    hi..
    Tax code : Tax code in some what more specific for calculating the tax...some material is having 2% tax..some having 3 % tax..etc..and these are input tax...so..these tax code will be of type input tax..
    now..based on the nature of tax type amount will be calculated....
    suppose tax code is calculation of 2 condtion type so ..we can do it in tax code conditon record fv11 also..
    so..tax code can be a combination of cond type...
    where as through cond type also we can also achieve this..by using one statistical cond type...
    Cond Type :  cond type is for the daily pricing configuration..how system will calculate the price for a centain material we can make define the rules here...
    Try this out..
    Thans

  • Diff between two timestamp in minutes on case condition

    Hi Gurus,
    I wanted to find the diff between two timestamp in minutes on case condition
    when type=1 then min(col2) and type=2 then max(col2)
    type-(datatype-numeric)
    col2-(datatype-timestamp)
    how can i do this
    Thanks

    Hi,
    Is this a question about the Berkeley DB SQL product?
    If so, you should look at the documentation on time fields in the SQLite page here:
    http://www.sqlite.org/datatype3.html#datetime
    Otherwise, you are asking this on the wrong forum.
    Regards,
    Alex Gorrod
    Oracle Berkeley DB.

  • BADI: Diff between Multiuse & Filter Dependent

    Hi All,
    I would like to know whats the diff between Multiuse and Filter Dependent, Filter Types and Defined Filters.
    Thanks,
    Santosh

    <b>Multiple Use</b>
    This property defines whether – during the initialization of a BAdI object using GET BADI– just one implementation needs to be selected through the specified filter values, or whether an arbitrary number of implementations (or no implementation at all) can be selected.
    If more than one implementation is selected at GET BADI for a BAdI provided for single use, the exception cx_badi_multiply_implemented is triggered. If no implementation is found, the exception cx_badi_not_implemented is triggered.
    Use
    You can define whether a BAdI is to be provided for single or multiple use. In the standard version, a BAdI is provided for single use, but a multiple use can also be selected.
    In the case of a multiple use, there is a general restriction – in addition to the general restriction regarding variable attributes – that the BAdI methods must not have any EXPORTING or RETURNING parameters. The reason for this is that, if you have a call with CALL BADI, the methods of all the object plug-ins referenced by the BAdI object are called and that there is no definition regarding from which of the implementations a returned value will actually come. CHANGING parameters, on the other hand, are allowed since these are changed by all the calling methods, one after the other, so that a method can also access the parameter changed in a previous method.
    Regards
    - Gopi

  • Diff between the Start routine and Update rules?

    Hi Gurus
    Diff between the Start routine and Update rules?
    Thanks in advance
    Raj

    Hi,
    Routines are like conditions or business rules that could be applied to filter the data while entering the BW system or could be used to apply certain conditions on the info objects itself.Update rule level you manipulate your data and  write your start routine.
    There are 4 types of routines
    1. Start routine- Could be used at two levels (transfer rule level and the Update rule level)
    This Start routine written at the transfer rule level helps filter the necessary data coming from the source system.
    For Example: If you decide to extract data that contain only quantity greater than 500 , then you could specify the Start rouitne to achieve this.
    The Start routine at the Update rule level provides similar functionality but at this point it helps direct specific data to 
    different data targets.  For Example: If there 3 data targets being fed from the Infosource, you may want to apply some condition to each data target, like send year 2000 data ti Data target1, 2001 to data target 2 and so on.  This can be achieved by using Start routine at the Update rule level
    2. Transfer Routine: This feature is available at the transfer rule levels
    While performing the transfer rules operation, there are 4 features available to the developers to create business rules on top pf the Infoobjects.
    1. You could do a one to one mappping of the Infoobject
    2. Provide a constant value
    3. Include a formula
    4. Write an ABAP routine.
    These 4 options refers to the transfer routine
    3. Update Routine:
    The limitations of just having 4 options in the transfer routine is overcome at the update rule level. There are various other 
    sophisticated features avaialable apart from the 4 options mentioned above. These business rules could be specified pertaining to each data target.
    4. Conversion Routine: It provides functionality to do Currency and unit conversion.
    Regards.

  • Diff.between Taxinn& taxinj

    hi sap guru's
    can anybody give me exect diff .between Taxinn& taxinj ?which is good? and why? give me at least  2 to 3 point
    in TAXINN  where we creat tax code execept FTXP
    regard's

    TAX INN
    If you are using  TAXINN procedure you have to maintain separate condition record in tcode :FV11
    JM01
    JM02 etc
    While creating purchase order  the tax will be flowing based on the condition record
    For all the vendor the same taxes are applicable.
    currently TAXINN is commonly used
    TAXINJ
    In this procedure you have to maintain taxcode in FTXP.
    while creating P.O taxes will be flowing from the Taxcode.
    Say for Example
    V1-16 %Excise duty+4%VAT +Cess
    V2-8 %Excise Duty 4% VATCess
    For the same vendor you can use either the taxcode V1 (or) V2
    G.Ganesh Kumar

  • Types of  DTP , Diff between Standard and Error DTP

    Hi experts,
    What is DTP ,  are the Types of  DTP , Diff between Standard and Error DTP , how it works in BI 7.0.
    I will assign points for your valuable answers.

    Hello ,
    Data transfer process (DTP) to transfer data within BI from one persistent object to another object, in accordance with certain transformations and filters. In this respect, it replaces the data mart interface and the InfoPackage. As of SAP NetWeaver 7.0, the InfoPackage only loads data to the entry layer of BI (PSA).
    The data transfer process makes the transfer processes in the data warehousing layer more transparent. Optimized parallel processing improves the performance of the transfer process (the data transfer process determines the processing mode). You can use the data transfer process to separate delta processes for different targets and you can use filter options between the persistent objects on various levels. For example, you can use filters between a DataStore object and an InfoCube.
    Data transfer processes are used for standard data transfer, for real-time data acquisition, and for accessing data directly.
    1.Benefit: Data ‘Distribution’within BI Capabilities (from PSA or InfoProviders to InfoProviders)
    2.Improved transparency of staging processes across data warehouselayers (PSA, DWH layer, ODS layer, Architected Data Marts)
    3.Improved performance and high scalability
    4.Separation of delta mechanism for different data targets: delta capability is controlledby the DTP
    5.Enhanced filtering in dataflow
    6.Repair modus based on temporary buffers (buffers keep complete set of data)
    See these docs for more info
    [Data Transfer Process |http://help.sap.com/saphelp_nw04s/helpdata/en/42/f98e07cc483255e10000000a1553f7/content.htm]
    [Enterprise Data Warehouse (EDW)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/67efb9bb-0601-0010-f7a2-b582e94bcf8a]
    [What's New with SAP NetWeaver 2004s - Detailed|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/910aa7a7-0b01-0010-97a5-f28be23697d3]
    [SAP NetWeaver 7.0 ETL and EII|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e0b24053-654e-2a10-4180-b0e7c7b4c9f2]
    [How to Create Monitor Entries from a Transformation Routine (NW7.0)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/50fda171-e36e-2910-9290-e3dab26c50b5]
    FAQ on SAP NetWeaver 2004s
    [Modeling the Enterprise Data Warehousing for SAP NetWeaver 2004s FAQ|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/7c2a7c65-0901-0010-5e8c-be0ad9c05a31]
    [Enterprise Data Warehousing for SAP NetWeaver 2004s FAQ|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c9f5fb91-0c01-0010-67a8-fd35946e9403]
    Thanks
    Chandran

  • Diff between 4.6c to 4.7 abap

    diff between 4.6c to 4.7 abap

    Hi
    the differences are with respect to customer master and the CIN
    In 4.6 cc the partner function tab is not there in the customer master
    that is in the customer maste there is no display of the prtner functions in the customer master
    But in the 4.7EE the partner functions are displayed on the customer master xd01 r vd01
    And again in the 4.6CC , in the Cin version the tax procedure is TAXINJ
    is used which gets te value from the function ebased
    and in 4.7 EE the Tax procedure is TAXINN which gets te value from teh Condition based
    and also in the customer master the CIN tab is not there in the customer master in the 4.6cc which is there in the 4.7 EE
    You can find the difference in release notes of each SAP version.
    Here are the links.
    http://help.sap.com/saphelp_47x200/helpdata/en/fc/e3003deddfae4de10000000a114084/frameset.htm
    http://help.sap.com/saphelp_scm50/helpdata/en/28/b34c40cc538437e10000000a155106/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/43/68805bb88f297ee10000000a422035/frameset.htm
    Please visit the following links:
    http://service.sap.com/erp
    http://solutionbrowser.erp.sap.fmpmedia.com/ (Functional prespective)
    http://service.sap.com/instguides --> mySAP Business Suite Applications --> mySAP ERP --> mySAP ERP 2005 --> Upgrade
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
    For Functionality Differences pls refer to the below site -
    http://solutionbrowser.erp.sap.fmpmedia.com/
    After opening the site, please select the Source Release Version which is 4.6 b Then Select the Target Release Version which is "mySAP ERP 2005" or ECC 6.0
    Select the Solution Area like Financial, Human Capital Management, Sales....
    Select module like MM, PP, SD, QM.....
    Click on Search
    Then it displays the Release Version and the Delta Functionality. which can be downloaded to a word document if required.
    and also check the release notes of ECC 6.0 in service.sap.com.
    Hope this helps you.
    Regards,
    Sree
    Message was edited by:
            sree ram

  • What is the diff. between Access seq. MWST, JTAX & JST1?

    Hi,
    May I know the diff. between Access seq. MWST, JTAX & JST1,used in tax condition types?
    Kind regards,
    Kishore

    from sap help
    An access sequence is a search strategy by means of which the system searches for valid records in various condition tables. It consists of one or more accesses. The sequence of accesses controls the priority of the individual condition records among each other. Through the accesses, the system is told where to look first and where to look next for a valid condition record in each case.
    only used for condition record
    JST1-sale tax access
    JTAX-excise access sequence for condition record maintenance in Fv11
    MWST-tax classification
    check following link also
    [TAXINN Condition;
    Regards
    Kaials Ugale

  • Diff between all views

    hi all,
           can any body tell me the diff between all views
    projection view ,database view,maintance view,help view
    plz tell me the difference with a example
    hope for positive reponse

    Maintenance views offer easy ways to maintain complex application objects.
    Data distributed on several tables often forms a logical unit, for example an application object, for the user. You want to be able to display, modify and create the data of such an application object together. Normally the user is not interested in the technical implementation of the application object, that is in the distribution of the data on several tables.
    A maintenance view permits you to maintain the data of an application object together. The data is automatically distributed in the underlying database tables. The maintenance status determines which accesses to the data of the underlying tables are possible with the maintenance view.
    database view
    Data about an application object is often distributed on several database tables. A database view provides an application-specific view on such distributed data.
    Database views are defined in the ABAP Dictionary. A database view is automatically created in the underlying database when it is activated.
    Application programs can access the data of a database view using the database interface. You can access the data in ABAP programs with both OPEN SQL and NATIVE SQL. However, the data is actually selected in the database. Since the join operation is executed in the database in this case, you can minimize the number of database accesses in this way. Database views implement an inner join
    projection view
    Projection views are used to hide fields of a table. This can minimize interfaces; for example when you access the database, you only read and write the field contents actually needed.
    A projection view contains exactly one table. You cannot define selection conditions for projection views.
    There is no corresponding object in the database for a projection view. The R/3 System maps the access to a projection view to the corresponding access to its base table. You can also access pooled tables and cluster tables with a projection view.
    help views
    Help views are used if a view with an outer join is needed as selection method in a search help.
    You have to create a help view if a view with outer join is needed as selection method of a search help.
    The selection method of a search help is either a table or a view. If you have to select data from several tables for the search help, you should generally use a database view as selection method. However, a database view always implements an inner join. If you need a view with outer join for the data selection, you have to use a help view as selection method.

  • 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.

  • Hi gurus what is the diff between free & refresh

    hi gurus what is the diff between free & refresh

    Hii!
      FREE f.
    Effect
    FREE f has the same effect as CLEAR f , namely that a Data object f is reset to the initial value corresponding to its type.
    Unlike CLEAR, FREE also releases any resources taken up by the data object f. FREE can also release more resources than CLEAR for table work areas declared using the TABLES statement.
    After FREE f, the data object f can be re-addressed at any time. The only condition is that you may need to re-allocate resources to the object.
    Note
    If f is an internal table with header line (where the name f in a sense has two meanings) the statement FREE f refers to the body of the table, and the statement CLEAR f refers to the header line.
    REFRESH itab.
    Effect
    The internal table itab is reset to its initial state, i.e. all table entries are deleted.
    Der Return Code SY-SUBRC is undefined.
    Notes
    The header entry of a table with a header line remains unchanged. It can be reset to its initial value using CLEAR.
    FREE itab can be used to free up the memory allocated to the table.
    Note
    Performance:
    The runtime required to reset an internal table depends on the amount of memory previously occupied by that table.
    Resetting a small internal table takes around 15 msn (standard microseconds). Resetting a 200 KB table takes around 400 msn, and a 1 MB table, around 3000 msn.
    If the internal table has an index or a hash table (because it was edited using INSERT, DELETE, SORT or COLLECT), the runtime increases slightly, since the index or hash table has to be released as well as the table itself.
    Regards
    Abhijeet

  • What is diff between acrual key & account key

    Pls let know the diff. between acrual key & Account key SD pricing procedure

    Hi Prem,
    In Account Key pricing procedure, Account keys are assigned to the condition types in the pricing procedures, this allows conditions
    such as freight conditions to posted to special freight revenue accounts.
    You can assign the Account keys using the following menu path in SPRO transaction,
    Sales and Distribution -> Basic Functions -> Account Assignment/Costing -> Revenue account determination -> Define and assign account keys -> Assign
    account keys.
    Before doing this you need to define the Account Keys in
    Sales and Distribution -> Basic Functions -> Account Assignment/Costing -> Revenue account determination -> Define and assign account keys -> Define Account key.
    Accruals are considered during Rebate Agreement processing.
    For example, Condition records are linked to the rebate agreement specifying the rebate rate and the accrual rate.
    When the rebate -relevant billing documents are processed, accruals can be determined and posted
    automatically by accessing that condition record. Corrections regarding Accurals are done using Credit memos.
    Hope this helps.
    regards,
    Raj

  • Diff between joins & forallentries

    hi gurus  we r retreving data from 2 tables  we use either joins or forallentries , what is the actual diff between joins & forallentries .

    hi,
    Syntax of for all entries...
    *FOR ALL ENTRIES IN itab WHERE  col <operator> itab-comp *
    The addition FOR ALL ENTRIES is only possible before WHERE conditions of the SELECT statement
    If the addition FOR ALL ENTRIES is specified before the language element WHERE, then the components comp of the internal table itab can be used as operands when comparing with relational operators.
    The internal table itab must have a structured line type and the component comp must be compatible with the column col.
    eg.
    PARAMETERS p_city TYPE spfli-cityfrom.
    TYPES: BEGIN OF entry_tab_type,
             carrid TYPE spfli-carrid,
             connid TYPE spfli-connid,
           END OF entry_tab_type.
    DATA: entry_tab   TYPE TABLE OF entry_tab_type,
          sflight_tab TYPE SORTED TABLE OF sflight
                           WITH UNIQUE KEY carrid connid fldate.
    SELECT carrid connid
           FROM spfli
           INTO CORRESPONDING FIELDS OF TABLE entry_tab
           WHERE cityfrom = p_city.
    SELECT carrid connid fldate
           FROM sflight
           INTO CORRESPONDING FIELDS OF TABLE sflight_tab
           FOR ALL ENTRIES IN entry_tab
           WHERE carrid = entry_tab-carrid AND
                 connid = entry_tab-connid.
    Syntax of join...
    [(] {dbtab_left [AS tabalias_left]} | join
              {[INNER] JOIN}|{LEFT [OUTER] JOIN}
                {dbtab_right [AS tabalias_right] ON join_cond} [)] ...  .
    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.
    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.
    *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.
    eg:-
    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 )
    hope this will helps u.
    please reward if it helps.
    thanks.

Maybe you are looking for