Infoset quesry extraction

hello friends,
i hope you all r well and doing good at yr places.
friends, can you please tell me how to create a genric datasource based on infoset. how can we extract the data from infoset...if anyone is having any document then please send me,,,it will be a nice help for me.
please suugest me navigation sterps as well...
my mail id is [email protected]
regards
manoj

Hello ManoJ,
How r u ?
In R/3 System
1. Go To SQ02 and create the InfoSet.
2. Go TO RSO2 and create the Data Source (Transactional Data or Attributes or Texts)
3. Provide Application Component and Descriptions then under "EXTRACTION FROM SAP QUERY" maintain the entry with the InfoSet which u created in step 1. SAVE DataSource.
4. Go To RSA3 and type the DataSource name & check the data.
In BW System
5. Replicate the DataSource & proceed.
Best Regards....
Sankar Kumar
+91 98403 47141

Similar Messages

  • Infoset query extract

    Hi BW gurus
    Can someone give me a solution to do query extracts to a flat file on queries built on infosets.
    rscrm_bapi does not support it, and creating infospokes is not feasible for this, i tried APD as well and looks like APD does not support infoset queries either. we are on 3.5
    Sam

    Try creating a multiprovider based on your Infoset, I had the same problem, awhile ago. RSCRM_BAPI doenst support flat file extraction from Infoset and we are in BI 7, eventually we took another route to get the flat file to them and not from the query.
    However, while testing it, it seemed to have worked. Let us know how you progressed.
    Best Wishes...

  • Extraction using infoset query.

    Hi,
    I have an extractor in R/3 which is using infoset  for extraction. The infoset contains some logic for extraction. I want to debugg the infoset. As the infoset is not attached to a query how can i debugg the code written in infoset.
    Thanks & Regards,
    Soumya.

    Soumya,
    If the problem is in the data which is being extracted from R/3 then debug the datasource by:
    use transaction RSA3 in R/3 to execute the datasource and put a tick in the option "Debug Mode".
    Mark

  • 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

  • Reg Infoset query

    Hi,
    What is infoset query in generic extraction? Why and when do we go for it? What is the advantage of it?
    Any help would be appreciated the sdn way.
    Regards,
    Jon.

    Hi ,
    <b>What are Info sets ?</b>
    An InfoSet is a special view of a set of data (logical database, table join, table, sequential file). It serves as the data source for SAP Query. An InfoSet determines which tables or fields of these tables are referenced in an evaluation. InfoSets are usually based on logical databases.
    InfoSets are only available if you have created them globally, independent of a client. You set this global area in the initial screen of InfoSet maintenance under Environment Work Areas.
    If you are using an InfoSet to extract data, the system first collects all data in the main memory. The data is transferred to the BI system in packages using the Service API interface. The size of the main memory is therefore important with this type of extraction. It is suitable for limited datasets only.
    When an InfoSet is created, a data source is selected in an application system. Since a data source can have a large number of fields, fields can be combined into logical units; the functional groups. Functional groups are groups of several fields that form a logical unit within an InfoSet. Any fields that you want to use in an extraction structure have to be assigned to a functional group. In generic data extraction using an InfoSet, all the fields of all functional groups for this InfoSet are available.
    The relevance of SAP Query to BI lies in the definition of the extraction structure by selecting fields of a logical database, a table join or other datasets in an InfoSet. This allows you to use generic data extraction for master or transaction data from any InfoSet.
    A query is generated for an InfoSet. The query gets the data and transfers it to the generic extractor.
    <b>Extraction Step By Step :</b>
    <b>R3 Side :</b>
    SQ02 -> Create info set , Generate .
    RS02 -> Create data source by giving info set name .
    RSA3 -> Check the data source for entries.
    <b>BW  Side :</b>
    Replicate DS.
    Assign DS for IS .
    Create TR , Activate
    Create Cube , UR .
    Create Info Pack ,Schedule the extraction .
    Hope this helps..
    Message was edited by:
            Renjith Kumar

  • BW infoset VS Classic infoset

    Hello all
    BW 3.5 patch 13
    I have created a BW infoset on an ods. When I try to create a extract structure in RSO2 in BW I don't see the BW infoset.
    I can create a Classic infoset (SQ01..3) on a ODS table and see that infoset in RSO2. 
    Am I missing some steps or we can use bw infosets for extraction? I thought we were suppose to go away from Calssic infosets?
    thanks
    parmjit

    I am trying to extract from BW to BW.
    thanks
    Parmjit

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

  • How to  extract  master data  attribute from  r/3 to bw give steps details

    how to  extract  master data  attribute from  r/3 to bw give steps details screenshots

    Hi
    Go through the below process to extract Master Data Attribute from R/3
    Hi,
    Maintaining Generic DataSources
    Use
    Regardless of the application, you can create and maintain generic DataSources for transaction data, master data attributes or texts from any transparent table, database view or SAP Query InfoSet, or using a function module. This allows you to extract data generically.
    Procedure
    Creating Generic DataSources
    1. Select the DataSource type and specify a technical name.
    2. Choose Create.
    The screen for creating a generic DataSource appears.
    3. Choose the application component to which you want to assign the DataSource.
    4. Enter the descriptive texts. You can choose any text.
    5. Select the datasets from which you want to fill the generic DataSource.
    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 you generate the DataSource, you have a DataSource with an extraction structure that corresponds to the database view or transparent table.
    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 you generate the DataSource, you have a DataSource with an extraction structure that corresponds to 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 extraction structure.
    The data must be transferred by the function module in an interface table E_T_DATA.
    Interface Description and Extraction Process
    For information about the function library, see the ABAP Workbench: Tools documentation.
    d. With texts you also have the option of extracting from fixed values for domains.
    6. Maintain the settings for delta transfer, as required.
    7. Choose Save.
    When performing extraction, note SAP Query: Assigning to a User Group.
    Note when extracting from a transparent table or view:
    If the extraction structure contains a key figure field that references a unit of measure or a currency unit field, this unit field has to be included in the same extraction structure as the key figure field.
    A screen appears on which you can edit the fields of the extraction structure.
    8. Edit the DataSource:
    &#9675; Selection
    When you schedule a data request in the BI scheduler, you can enter the selection criteria for the data transfer. For example, you can 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 extraction structure, the data for this field is transferred in correspondence with the selection criteria in the scheduler.
    &#9675; Hide field
    You set this indicator to exclude an extraction structure field from the data transfer. The field is no longer available in BI when you set the transfer rules or generate the transfer structure.
    &#9675; Inversion
    Reverse postings are possible for customer-defined key figures. Therefore inversion is only active for certain transaction data DataSources. These include DataSources that have a field that is marked as an inversion field, for example, the update mode field in DataSource 0FI_AP_3. If this field has a value, the data records are interpreted as reverse records in BI.
    If you want to carry out a reverse posting for a customer-defined field (key figure), set the Inversion indicator. The value of the key figure is transferred to BI in inverted form (multiplied by –1).
    &#9675; Field only known in exit
    You can enhance data by extending the extraction structure for a DataSource by adding fields in append structures.
    The Field Only Known in Exit indicator is set for the fields of an append structure; by default these fields are not passed to the extractor from the field list and selection table.
    Deselect the Field Only Known in Exit indicator 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 and in the selection table.
    9. Choose DataSource ® Generate.
    The DataSource is saved in the source system.
    Maintaining Generic DataSources
    &#9679; Change 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 or change the texts of a DataSource. Double-click on the name of the table, view, InfoSet or extraction structure to get to the appropriate maintenance screen. Here you make the changes to add new fields. You can also completely swap transparent tables and database views, though this is not possible with InfoSets. Return to 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 BI system, choose DataSource ® Test Extraction.
    &#9679; Delta DataSource
    On 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 corresponding query. If you want to delete a DataSource, make sure it is not connected to a BI system.
    NR

  • 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:
    &#61601;        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.
    &#61601;        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.
    &#61601;        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.
    &#61601;        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

  • Extraction from different datasources

    hi,
    my problem is we need some fields from one datasource and some in other and some in another.so how can i extract these fields and can use them .can any body give a solution how to achive this.or can we extract the fields from the tables in r/3 which is better option.

    Sekhar
    There are 3 options of doing this :
    Option 1:- If fields that you want from different datasources are related to one particular application area say purchasing/sales then you can enhance the base datasource(contains max no of fields you want) with the required fields from other data sources ...write an ABAP user exit to populate these fields .
    Option 2 :- You always have option of creating generic data source based on view/infoset query extraction/function module .
    Option 3 : If the required fields are from one particular application area then extract data from these data sources into respective ODS objects . Then you can manipulate the data into Infocube/ODS on top of these base ODS objects if it suits ur requirement.

  • Transports BWD - BWQ !?

    Hello all,
    How r u ?
    We transported the BWD myself Objects(InfoSets, Extract Structures & DataSources) to BWQ. The transport was successful and we could see the InfoSets and extract structures in the BWQ and not the DataSources.
    The SourceSystem Conversion is fine. We replicated the BWQ myself SourceSystem, even after that the DataSources are not shown. Then we tried many times transporting using many ways but did not help.
    Another request was created in the BWD for the Cube with Indata Flow Before and After, the error came out like,
    <b> DataSource ZCV_ZCV_CLINT_TRANS does not exist in source system BWA100 of version A
    Mapping between data source ZCV_ZCV_CLINT_TRANS and source system BWA100 is inconsistent
    DataSource ZCV_ZCV_CLINT_TRANS does not exist in source system BWA100 of version A
    Field /BIC/ZCV_ANAAM will not be delivered from DataSource ZCV_ZCV_CLINT_TRANS in source system BWA100
    Field /BIC/ZCV_BSNNO will not be delivered from DataSource ZCV_ZCV_CLINT_TRANS in source system BWA100
    Field /BIC/ZCV_BURST will not be delivered from DataSource ZCV_ZCV_CLINT_TRANS in source system BWA100
    Field /BIC/ZCV_CLINT will not be delivered from DataSource ZCV_ZCV_CLINT_TRANS in source system BWA100</b>
    Like this for all the objects.
    Finally we decided to create the DataSources by hand as the InfoSets & Extract Structures are available. Here comes the nightmare,
    While giving the same (BWD)DataSource name in RSO2(BWQ) it allowed us to select the Create the button without saying any error, agter entering all the needed entries while saving it shows
    <b>InfoSource ZORG_CLIENT_TEXT already exists</b>
    How come in RSO2 it will show like this ? What could be the problem ?
    Could anyone get why this problem occurs ? all the attempts to create or transport the DataSources failed. This should go live soon....
    Any clues ?
    Best Regards....
    Sankar Kumar
    +91 98403 47141

    Hi,
    First transpot the ALL ODSs with DFB .So here you need to take tick mark for DEV R/3 only. Once it is imported into BWQ, then replicate the datasources from self system in QA BIW.
    And then transport all Cubes with DFB and DFA .Here you need to take tick mark for both R/3 DEV and DEV BIW in the transport connector tool .
    Donot forget to have the conversion of source systems in QA BIW.
    i,e the mapppinf should be like:
    DEV R/3---> QA R/3
    DEV BIW---> QA BIW.
    With rgds,
    Anil Kuamr Sharma .P

  • Datasource from a logical database.

    Hi all,
      I am in need of creating a datasource from a std.. Logical Database IMA in R/3. Is it possible to create a datasource directly from logical database or it is essential to find the base tables fetching data to the logical databse and look for the appropriate business content.
    Regards,
    Murali

    Thank you,
      The document helped me to create a Infoset.Can anyone share ur experience of creating a datasource using a INFoset which extracts data from a LDB. The LDB which i am supposed to use has few structures,hence, I am having some performance isssues which i believe a more elaborate better document can help me with.. The LDB I am looking for is IMA.
    Thanks in advance.

  • Pulling the latest records from the datasource to BW

    Hi,
    I need to pull the most recent records from a custom table on R/3 side. I make use of infoset query to retrieve data from two different tables. One custom table and the other SAP table MAKT. I created a transaction data... Datasource make use of infoset to extract the data on R/3 side.
    Is there a place where I can write code to play around with the data... is there any user exit to write the code for this purpose.
    Need help...

    Trx CMOD:
    1. Enter the Project name; if you dont have an existing project and u have to create one.
    Select a good name for a project..say ZBIW..and then enter the name and click on create button.It will take u to new screen.There give short text for project name.
    Above u will see 'enhancement assignments' button.Click it and in the new screen add enhancement RSAP0001.
    Save and remember to activate project too..
    (save in appropriate transport request)
    2. go to components select the required function module.
    EXIT_SAPLRSAP_001 for Transactional DS
    EXIT_SAPLRSAP_002 for Master DS
    Hope it helps.
    Regards

  • Field catalog does not agree with the fields of the functional area

    G'day everyone,
    I am using a generic extractor via infoset to extract data from R/3 source system.
    Using RSA3, I have obtained an error message and no further details.
    ****ERROR MESSAGE
    "Field catalog does not agree with the fields of the functional area
    Message no. RSUQ134
    ****ERROR MESSAGE
    I have checked and adjusted my infoset in SQ02 and they seems fine but still obtain the same error.
    In BW, replicated the datasource and activate the transfer rules but still obtain the same error.
    Anyone knows how to get more details for this type of error? Or how to fix this problem?
    Regards
    Wayne

    I think I have just solved it.
    Transaction RS02 delete and recreate after checking the structure in BW and Source system are the same.
    Cheers

  • Generic example

    Please tell me a generic datasource with scenario. I want to learn how to put join condition.

    Hi deepthi,
    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:
    &#61601; 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&#61601;
    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.
    &#61601; 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&#61601; 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.
    Plz assign points if helpful. This is the only way to say thanks.
    And give me ur ID i send u some helpful documents...
    Regards
    Rakesh Jangir

Maybe you are looking for