About Generic Extraction

Hi all,
              I would like to have some links r docs to mail about DB view extraction. I am stuck in it. I would like to know it from  how to create a view and till how do i recognize a delta field in the given 2 tables.
my mail ID is [email protected]
Thanks and regards.

hi pradeep,
  Maintaining Generic DataSources 
Use
Independently of application, you can create and maintain generic DataSources for transaction data, master data attributes or texts from any kinds of transparent tables, database views, InfoSets of the SAP query or using a function module. As a result, you can make use of the generic extraction of data.
Procedure
Creating a Generic DataSource
       1.      Select the DataSource type and give it a technical name.
       2.      Choose Create.
The creating a generic DataSource screen appears.
       3.      Choose an application component to which the DataSource is to be assigned.
       4.      Enter the descriptive texts. You can choose any text.
       5.      Choose from which datasets the generic DataSource is to be filled.
                            a.      Choose Extraction from View, if you want to extract data from a transparent table or a database view. Enter the name of the table or the database view.
After generation, you get a DataSource whose extract structure is congruent with the database view or the transparent table view.
For more information about creating and maintaining database views and tables, see the ABAP Dictionary Documentation.
                            b.      Choose Extraction from Query, if you want to use a SAP query InfoSet as the data source. Select the required InfoSet from the InfoSet catalog.
Notes on Extraction Using SAP Query
After generation, you now have a DataSource whose extract structure matches the InfoSet.
For more information about maintaining the InfoSet, see the System Administration documentation.
                            c.      Choose Extraction using FM, if you want to extract data using a function module. Enter the function module and extract structure.
The data must be transferred by the function module in an interface table E_T_DATA.
Interface Description and Extraction Process Flow
For information about the function library, see the ABAP Workbench: Tools documentation.
                            d.      With texts, you also have the option of extraction from domain fixed values.
       6.      Maintain the settings for delta transfer where appropriate.
       7.      Choose Save.
When extracting, look at SAP Query: Assigning to a User Group.
Note when extracting from a transparent table or view:
If the extract structure contains a key figure field, that references to a unit of measure or currency unit field, this unit field must appear in the same extract structure as the key figure field.
A screen appears in which you can edit the fields of the extract structure.
       8.      Editing the DataSource:
        Selection
When scheduling a data  request in the BW Scheduler, you can enter the selection criteria for the data transfer. For example, you may want to determine that data requests are only to apply to data from the previous month.
If you set the Selection indicator for a field within the extract structure, the data for this field is transferred in correspondence with the selection criteria in the scheduler.
        Hide field
You should set this indicator to exclude an extract structure field from the data transfer. As a result of your action, the field is no longer made available in BW when setting the transfer rules and generating the transfer structure.
        Inversion
Reverse postings are possible for customer-defined key figures. For this reason, inversion is only possible for certain transaction data DataSources. These include DataSources that have a field that is indicated as an inversion field, for example, the field update mode in the DataSource 0FI_AP_3. If this field has a value, then the data records are interpreted as reverse records in BW.
Set the Inversion indicator if you want to carry out a reverse posting for a customer-defined field (key figure). The value of the key figure is then transferred in inverted form (multiplied by –1) into BW.
        Field only known in exit
You can enhance data by extending the extract structure for a DataSource using fields in append structures.
The indicator Field only known in Exit is set for fields of an append structure. In other words, by default these fields are not passed onto the extractor from the field list and selection table.
Deselect the indicator Field Only Known in Exit to enable the Service API to pass on the append structure field to the extractor together with the fields of the delivered extract structures in the field list as well as in the selection table.
9. Choose DataSource ® Generate.
The DataSource is now saved in the source system.
Maintaining Generic DataSources
•        Change the DataSource
To change a generic DataSource, in the initial screen of DataSource maintenance, enter the name of the DataSource and choose Change.
You can change the assignment of a DataSource to an application component as well as the texts of a DataSource. Double-clicking on the name of the table, view, InfoSet or extract structure takes you to the appropriate maintenance screen. Here you can make changes required to add new fields. You can fully swap transparent tables and database views, but not InfoSets. If you return to the DataSource maintenance and choose Create, the screen for editing a DataSource appears. To save the DataSource in the SAP source system, choose DataSource  ® Generate.
If you want to test extraction in the source system independently of a BW system, choose DataSource  ®  Test Extraction.
•        Delta DataSource
In the Change Generic DataSource screen, you can delete any DataSources that are no longer relevant. If you are extracting data from an InfoSet, delete the associated query. If you want to delete a DataSource, this must not be connected to a BW system.
For more information about extracting using SAP Query, see Extraction using the SAP Query.
if helpfull assign points
regards,
yunus

Similar Messages

  • Generic Extraction-example

    hello EXPERTS
    I am trying to give one presentation about 'Generic Extraction using View'...I know how to explain the process.But as I donot have project experience,I have never worked with Generic Extraction.
    Can any one give an example where they used generic extraction(by view) on SAP standard tables.Its enough if you can mention the fields you used and from which tables you took these fields?
    Thanks
    S

    Hi,
    Processing steps for creating the Generic Datasource by useing View:
    1.Goto RSo2.
      Datasource can be created for
      a). Transaction Data
      b). Master data Attributes
      c). Master data Text
    2.Specify Application component(SD/MM..)
    3.There are three extraction methods to fill datasource.
        i).Transparent table or Database view
        ii).InfoSets of the SAP query
        iii).Using a Function Module
    4.Select extraction method extracts the data from a transparent  table or database view.
    5.select Extraction from View, then we have to create the View.
       a).specify the view name.
       b).choose the view type (Database view) from bellow mentioned views.
          Database view.
          projection view.
          maintainance view.
          help view.
    6. Specify Tables and Join Conditions and define view fields.
    7. Assign View to Datasource
    8. Once you specify view in Data source, the extract structure willgenerate.
    9. then select the filds in selection column.
    10. Specify Delta-Specific Field and type.
    11. Specify Safety Interval and Delta Type and select Save button.
    12. Testing the Generic extraction.
    Select Datasource option from menu bar-->select Test Extraction or you can check in RSA3.
    Regards,
    Suman.

  • Reg Generic Extraction

    Hi Gurus,
    Can any one explain me about generic extraction like,
    1) when we go for Generic extraction
    2) what is the business scenario
    3) generic delta
    Please explain me with step by step by choosing some data fields as example for this. One request, plz don't send sap help file as i have it. If any one have screen shots for this plz send me.
    Thanks in advance.
    Regards
    K.M.Reddy

    hi,
      we go for generic extraxctor when standard cube or datasource do not suite the
    requirement.
    for eg in satandard sd datasource donot have the field we require  then we
    go for generic datasource.
    if standard datasource do not have shipping point field in datasource then we
    can either append the structure or go for generic datasource.
    for generic delta refer link.
    http://help.sap.com/saphelp_nw04s/helpdata/en/37/4f3ca8b672a34082ab3085d3c22145/frameset.htm
    regards
    pls assign points if helpful.

  • Generic extraction with function module

    hai experts,
    can u please forward the material about Generic extraction using FM
    and  infoset query with step by step and real-time requirements to my
    mail id.([email protected])
    Regards
    DJReddy

    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a0f46157-e1c4-2910-27aa-e3f4a9c8df33

  • Give me details about differrent views in generic extraction give details

    give me details about differrent views in generic extraction give details  such as  database view, projection view, help view, etc please give detail

    Dear Deba,
    Projection view - Just retrieves some fields from a single table.
    Help View - This is used for search help.
    Database View - This is inner join view of one or more tables
    Maintenance View - Helps in creating maintaining data of the application object. The data can be distributed among several tables
    Data Base View:
    A database view is defined in the ABAP Dictionary and automatically created on the database during
    activation. Accesses to a database view are passed directly to the database from the database interface.
    The database software performs the data selection.
    If the definition of a database view is changed in the ABAP Dictionary, the view created on the database
    must be adjusted to this change. Since a view does not contain any data, this adjustment is made by
    deleting the old view definition and creating the view again in the ABAP Dictionary with its new definition.
    The maintenance status defines whether you can only read with the view or whether you can also write
    with it. If a database view was defined with more than one table, this view must be read only.
    The data read with a database view can be buffered. View data is buffered analogously to tables. The
    technical settings of a database view control whether the view data may be buffered and how this should
    be done. The same settings (buffering types) can be used here as for table buffering. The buffered view
    data is invalidated when the data in one of the base tables of the view changes.
    Maintainance View:
    Data that is distributed on more than one table often forms a logical unit, called an application object.
    You should be able to display, change and create the data of such an application object together. Users
    usually are not interested in the technical implementation of the application object, such as the distribution of the data on several tables.
    You can maintain complex application objects in a simple way using a maintenance view. The data is
    automatically distributed on the underlying database tables.
    All the tables used in a maintenance view must be linked with a foreign key. This means that the join
    conditions are always derived from the foreign key in the maintenance view. You cannot enter the join
    conditions directly as in a database view.
    A maintenance interface with which the data of the view can be displayed, changed and created must be
    generated from the definition of a maintenance view in the ABAP Dictionary.
    When the maintenance interface is created, function modules that distribute the data maintained with the
    view on the underlying tables are automatically generated.
    The maintenance interface is generated with the Transaction Generate Table View (Transaction SE54)
    or from the view maintenance screen with Environment -> Tab.maint.generator.
    Database views implement an inner join. You only get those records which have an entry in all the tables
    included in the view.
    Maintenance views implement an outer join.
    Help View:
    A help view is defined analogously to a maintenance view. Help views can only be used as selection
    methods in search helps. Since the R/3 System cannot pass the selection directly to the database using
    a help view, it must generate its own access routines. The database view should therefore be used as
    selection method in preference to the help view.
    http://help.sap.com/saphelp_nw2004s/helpdata/en/cf/21ecf9446011d189700000e8322d00/frameset.htm
    Difference between "Help View" and "Search Help"
    http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ed06446011d189700000e8322d00/frameset.htm
    for more detailed info look on:
    http://www.sap-img.com/abap/what-is-the-different-types-and-usage-of-views.htm
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/abap+dictionary&
    Regards,
    Ram.

  • Generic Extraction (or) How to use table in R/3 system as datasource in BW?

    Hi all,
    Hope all are having a great day
    Can any1 tell me the steps, for Generic Extraction.
    It will be very helpful, if the steps are as much as simpler as posible.
    I know to create a simple cube in BW.
    I have this much knowledge, depending on this can any1 tell me the steps for Generic Extraction from R/3.
    examples wud be vry useful
    Regards,
    Sourav

    hi,
    Maintaining Generic DataSources 
    Use
    Independently of application, you can create and maintain generic DataSources for transaction data, master data attributes or texts from any kinds of transparent tables, database views, InfoSets of the SAP query or using a function module. As a result, you can make use of the generic extraction of data.
    Procedure
    Creating a Generic DataSource(RSO2)
           1.      Select the DataSource type and give it a technical name.
           2.      Choose Create.
    The creating a generic DataSource screen appears.
           3.      Choose an application component to which the DataSource is to be assigned.
           4.      Enter the descriptive texts. You can choose any text.
           5.      Choose from which datasets the generic DataSource is to be filled.
                                a.      Choose Extraction from View, if you want to extract data from a transparent table or a database view. Enter the name of the table or the database view.
    After generation, you get a DataSource whose extract structure is congruent with the database view or the transparent table view.
    For more information about creating and maintaining database views and tables, see the ABAP Dictionary Documentation.
                                b.      Choose Extraction from Query, if you want to use a SAP query InfoSet as the data source. Select the required InfoSet from the InfoSet catalog.
    Notes on Extraction Using SAP Query
    After generation, you now have a DataSource whose extract structure matches the InfoSet.
    For more information about maintaining the InfoSet, see the System Administration documentation.
                                c.      Choose Extraction using FM, if you want to extract data using a function module. Enter the function module and extract structure.
    The data must be transferred by the function module in an interface table E_T_DATA.
    Interface Description and Extraction Process Flow
    For information about the function library, see the ABAP Workbench: Tools documentation.
                                d.      With texts, you also have the option of extraction from domain fixed values.
           6.      Maintain the settings for delta transfer where appropriate.
           7.      Choose Save.
    When extracting, look at SAP Query: Assigning to a User Group.
    Note when extracting from a transparent table or view:
    If the extract structure contains a key figure field, that references to a unit of measure or currency unit field, this unit field must appear in the same extract structure as the key figure field.
    A screen appears in which you can edit the fields of the extract structure.
           8.      Editing the DataSource:
            Selection
    When scheduling a data  request in the BW Scheduler, you can enter the selection criteria for the data transfer. For example, you may want to determine that data requests are only to apply to data from the previous month.
    If you set the Selection indicator for a field within the extract structure, the data for this field is transferred in correspondence with the selection criteria in the scheduler.
            Hide field
    You should set this indicator to exclude an extract structure field from the data transfer. As a result of your action, the field is no longer made available in BW when setting the transfer rules and generating the transfer structure.
            Inversion
    Reverse postings are possible for customer-defined key figures. For this reason, inversion is only possible for certain transaction data DataSources. These include DataSources that have a field that is indicated as an inversion field, for example, the field update mode in the DataSource 0FI_AP_3. If this field has a value, then the data records are interpreted as reverse records in BW.
    Set the Inversion indicator if you want to carry out a reverse posting for a customer-defined field (key figure). The value of the key figure is then transferred in inverted form (multiplied by –1) into BW.
            Field only known in exit
    You can enhance data by extending the extract structure for a DataSource using fields in append structures.
    The indicator Field only known in Exit is set for fields of an append structure. In other words, by default these fields are not passed onto the extractor from the field list and selection table.
    Deselect the indicator Field Only Known in Exit to enable the Service API to pass on the append structure field to the extractor together with the fields of the delivered extract structures in the field list as well as in the selection table.
    9. Choose DataSource ® Generate.
    The DataSource is now saved in the source system.
    Maintaining Generic DataSources
    •        Change the DataSource
    To change a generic DataSource, in the initial screen of DataSource maintenance, enter the name of the DataSource and choose Change.
    You can change the assignment of a DataSource to an application component as well as the texts of a DataSource. Double-clicking on the name of the table, view, InfoSet or extract structure takes you to the appropriate maintenance screen. Here you can make changes required to add new fields. You can fully swap transparent tables and database views, but not InfoSets. If you return to the DataSource maintenance and choose Create, the screen for editing a DataSource appears. To save the DataSource in the SAP source system, choose DataSource  ® Generate.
    If you want to test extraction in the source system independently of a BW system, choose DataSource  ®  Test Extraction.
    •        Delta DataSource
    In the Change Generic DataSource screen, you can delete any DataSources that are no longer relevant. If you are extracting data from an InfoSet, delete the associated query. If you want to delete a DataSource, this must not be connected to a BW system.
    For more information about extracting using SAP Query, see Extraction using the SAP Query.
    hope this helps.
    assign point if so
    partha

  • Generic extraction loading and performances issues

    hi,
          any one can give the details about the generic extraction loading as well as performance issues.
    advance thanks
    regards
    praveen

    Hi,
    when there is no suitable business content datasource we go for creating generic data source.
    by using generic data source we can extract data present in single or multiple tables.
    If the data is present in the single table we go for generic data source extracting from table.
    If the data that is to be extracted is present in multiple tables and the relation between the tables is one to one and if there is a common field in both the tables we create a view on these tables and create a generic data source extracting from view.
    if you want to extract data from different tables and there is no common field we create a info set on these tables and create a generic datasource extracting from query.
    if you want to extarc the data from different tables and the relation is one to many  or many to many we create a generic data source from function module.
    If we extarct from function module ,at run time it has to execute the code and brings the data to BW.so it degrades the loading performance.
    regards,

  • Delta for Generic Extraction

    Hi all,
    Can anyone tell about delta for generic extraction i.e 3 options in detail and when do we use it.
    thanks in advance,
    chandra sekhar

    When you want to customize existing datasources at R/3 sides then you can do that with customer exits.
    Suppose if you want to add a column to the existing datasource then you will use append structures (Transaction SBIW-> Edit Data sources - Enhance Datasource) then to fill the column you will write the code in these Exits.
    There are 4 types of Exits available.Function Group (XRSA)
    EXIT_SAPLRSAP_001 Customer Function Call for Supplying Transaction Data
    EXIT_SAPLRSAP_002 Customer Function Call for Supplying Master Data (Attributes)
    EXIT_SAPLRSAP_003 Customer Function Call for Supplying Text
    EXIT_SAPLRSAP_004 Customer Function Call for Supplying Hierarchies
    As you are aware there 4 types since the datasources in R/3 are predefined to fill the data of BW viz, attributes,Text,Hierarchy and Transaction.
    Check the below forum discussion for more information..
    DataSource Enhancement
    Regs
    Gopi
    Assign point if it helps ...

  • Generic extraction -Infoset

    Hello Gurus,
    I searched a lot on this but could not find Why  and when we do we use Infoset for Generic extraction?
    when i searched the SDN they give info about why a Table/View and Function Module is used but not on Infoset.
    Any document is helpful with a scenario.
    I am asking this query after lot of research itself.
    I read the help and could not understand why joins in Infoset.
    Thanks,
    Sahasra.

    Hi Sahasra,
    Go through the below thread and article, you will get clear idea on when to create and how to to create generic data source using Infoset query
    when we would create genric extractor on a infoset query
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/9018e4f3-5537-2e10-238e-ef06d9ab31e8?QuickLink=index&overridelayout=true
    Regards,
    Venkatesh

  • Displaying Application is specified in Generic Extraction

    Hi All,
    I am working on Generic Extraction,
    I had created ZMASTER in SE11 and in next screen I entered 2 fields 1 is MATNO and MATNAME,
    and I had assigned MATNO as Primary  Key and Inti option, while I am entering ZMATNO and activating it is displaying Application is not specified
    What does that mean, I tried in several ways but result has not come
    2) when I click F4 at Dataelemts it is leading to Varient screen and asking to assign or create a variant(thugh I created its not getting activated my cretaed fields
    Pls tell me the scenario or any other methods and about the VARIENT
    i just want to create  some fields and enter data manually
    Thanks for the friends who is going to help me in it
    Mohhan

    Hi Mohhan..........
    U r trying to create a table ZMASTERt..............In that table u are using two fields......MATNO and MATNAME.........right?.......
    Then where did u get this ZMATNO...............did u want to create field also...............?
    Look........we can create field....................Domain ...........as well as  Data element......but for that u hav to use the correct sequesnce............
    First u hav to create a Domain.......assign the Domain to a Data element............then u hav to create a field.........and assign this Data element in to that field...........then athe u can use this field to create a table............u can use an existing Domain also........and using it create a field............that is also possible..........I think u r doing something wrong........
    Field,Domain...........u can create these in SE11........
    Regards,
    Debjani.........

  • Reagrding Generic Extraction Delta

    hai
    Can anyone explain in detail with example or reak time scenarios about "Generic delta extraction for '0calday'" , "Generic Delta extraction for Numaric Pointer" , "Generic Delta extraction for timestamp" individually ..
    Please also send some documents or forums or weblog or screen shots to [email protected] now
    Thanks
    Bye
    mohammed

    Dear shylaja,
    can you please send the documents related to generic extraction to [email protected] &/  to [email protected] ?
    hope you will help.
    Waiting for your reply.
    Regards
    Vinay

  • Generic Extraction & delta

    Hi Experts,
    Can anyone tell me regarding the generic extraction and how delta happens in this case.
    regards,
    MGR

    MGR,
    Please find the below links for more better understanding about the generic delta and extraction:
    Business Content and Extractors
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
    ****Assign Points*********
    Gattu

  • HI could you pls explaing  generic extraction delta mechanism

    I  know what is delta . but i couldnt differentiate when we go for time stamp and numeric pointer
    i have the document for how to generic delta but inthat it is mentioned about how to use . but i want to know when shoudl i use time stamp and numeric pointer
    all answers would be rewarde

    Hi Dolly,
    Here the changed records can be isentified by :
    1. Based on the date of creation or last change ( Delta based on 0Calday)
    2. Based on the record number ( Numeric Pointer )
    3. Based on time of change ( Timestamp)
    real time examples would be
    1. Master Record creation like customer ID creation
    2. Timesheets in SAP PS
    3. Invoive details / Sales Order Details.
      Here is a weblog from Siggi for Generic Delta Extraction with Function Module.
    /people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
    Check previous posts as well.
    Generic delta
    Data Warehousing
    regards
    @jay

  • Generic Extraction business Requirement, through function module,

    Generic Extraction business Requirement, specifically through function module and source code in function module.

    Dear Karthik,
    Go to transaction SBIW -> Generic Datasource -> Maintain Generic Datasources -> Choose Master/Transaction Data -> Maintain proper entries (Application Component, Descriptions) -> Extraction by FM if you want to extract using FM.
    Maintaining Generic DataSources - Independently of application, you can create and maintain generic DataSources for transaction data, master data attributes or texts from any kinds of transparent tables, database views, InfoSets of the SAP query or using a function module. As a result, you can make use of the generic extraction of data.
    Creating a Generic DataSource
           1.      Select the DataSource type and give it a technical name.
           2.      Choose Create. The creating a generic DataSource screen appears.
           3.      Choose an application component to which the DataSource is to be assigned.
           4.      Enter the descriptive texts. You can choose any text.
           5.      Choose from which datasets the generic DataSource is to be filled.
                                a.      Choose Extraction from View, if you want to extract data from a transparent table or a database view. Enter the name of the table or the database view.
    After generation, you get a DataSource whose extract structure is congruent with the database view or the transparent table view.
    For more information about creating and maintaining database views and tables, see the ABAP Dictionary Documentation.
                                b.      Choose Extraction from Query, if you want to use a SAP query InfoSet as the data source. Select the required InfoSet from the InfoSet catalog.
    After generation, you now have a DataSource whose extract structure matches the InfoSet.
    For more information about maintaining the InfoSet, see the System Administration documentation.
                                c.      Choose Extraction using FM, if you want to extract data using a function module. Enter the function module and extract structure.
    The data must be transferred by the function module in an interface table E_T_DATA.
    For information about the function library, see the ABAP Workbench: Tools documentation.
                                d.      With texts, you also have the option of extraction from domain fixed values.
    Maintain the settings for delta transfer where appropriate.
           7.      Choose Save.
    Note when extracting from a transparent table or view:
    If the extract structure contains a key figure field, that references to a unit of measure or currency unit field, this unit field must appear in the same extract structure as the key figure field.
    A screen appears in which you can edit the fields of the extract structure.
           8.      Editing the DataSource:
           Selection
    When scheduling a data  request in the BW Scheduler, you can enter the selection criteria for the data transfer. For example, you may want to determine that data requests are only to apply to data from the previous month.
    If you set the Selection indicator for a field within the extract structure, the data for this field is transferred in correspondence with the selection criteria in the scheduler.
           Hide field
    You should set this indicator to exclude an extract structure field from the data transfer. As a result of your action, the field is no longer made available in BW when setting the transfer rules and generating the transfer structure.
           Inversion
    Reverse postings are possible for customer-defined key figures. For this reason, inversion is only possible for certain transaction data DataSources. These include DataSources that have a field that is indicated as an inversion field, for example, the field update mode in the DataSource 0FI_AP_3. If this field has a value, then the data records are interpreted as reverse records in BW.
    Set the Inversion indicator if you want to carry out a reverse posting for a customer-defined field (key figure). The value of the key figure is then transferred in inverted form (multiplied by –1) into BW.
           Field only known in exit
    You can enhance data by extending the extract structure for a DataSource using fields in append structures.
    The indicator Field only known in Exit is set for fields of an append structure. In other words, by default these fields are not passed onto the extractor from the field list and selection table.
    Deselect the indicator Field Only Known in Exit to enable the Service API to pass on the append structure field to the extractor together with the fields of the delivered extract structures in the field list as well as in the selection table.
    9. Choose DataSource -> Generate.
    The DataSource is now saved in the source system.
    Maintaining Generic DataSources
    ·        Change the DataSource
    To change a generic DataSource, in the initial screen of DataSource maintenance, enter the name of the DataSource and choose Change.
    You can change the assignment of a DataSource to an application component as well as the texts of a DataSource. Double-clicking on the name of the table, view, InfoSet or extract structure takes you to the appropriate maintenance screen. Here you can make changes required to add new fields. You can fully swap transparent tables and database views, but not InfoSets. If you return to the DataSource maintenance and choose Create, the screen for editing a DataSource appears. To save the DataSource in the SAP source system, choose DataSource  -> Generate.
    If you want to test extraction in the source system independently of a BW system, choose DataSource  ->  Test Extraction.
    ·        Delta DataSource
    In the Change Generic DataSource screen, you can delete any DataSources that are no longer relevant. If you are extracting data from an InfoSet, delete the associated query. If you want to delete a DataSource, this must not be connected to a BW system.
    Also visit :[Data Extraction from SAP Source System | http://help.sap.com/saphelp_nw04/helpdata/en/28/4c553c42360a40e10000000a114084/content.htm]
    Regards,
    Naveen.

  • Generic extraction

    Hi,
    in generic extraction in which scenarios you extract data from  table,view,infoset query,FM
    sridhar

    Transparent Table
    If you're wishing to create a generic DataSource based on a single Transparent Table in the source R3/ECC system, then using that table as the source for your generic DataSource would be appropriate because it will expose all of the columns in that table to your generic extraction structure. There is one exception to this and that is, if you have more than one date field (e.g. Created On and Changed On dates) that you're going to use for generic delta. Pool/Cluster tables and structures wouldn't be allowable for this type of generic DataSource setup.
    View on Transparent Tables
    If your requirement is to create a generic DataSource based on multiple Transparent Tables in your source R3/ECC system, then a view would be appropriate. You can either use SAP delivered views in the source R3/ECC environment or create a custom view. The same exceptions (generic delta on more than one date field, pool/cluster tables and structures).
    Function Module
    A custom Function Module can be coded for the extraction of data for a generic DataSource. This type would be appropiate if you're extracting data from pool/cluster tables or structures. Another use for a Function Module as the source for a generic DataSource would be if you're going to use more than one data field for a generic delta. Finally, a Function Module would be used if there is some transformational-type logic required to be done on the extracted data before it is passed to BW.
    InfoSet Query
    An InfoSet (not to be confused with an InfoSet in BW) query in a source R3/ECC environment, is created in tocde SQ01, and is a way of creating "quick-and-dirty" reports with summarized values, derived values, et. al. This can be used as the basis for a DataSource, if the queries are already built. If not, then a Function Module can perform and necessary aggregations, derivations or other transformational-type logic, instead of creating a query. I say this because I'd highly discourage using this as a source for a generic DataSource because InfoSet queries are usually extremely inefficient and can consume a lot of the valuable system resources.

Maybe you are looking for