Infoset Query in Datasource.

I'm using a Infoset query based on an ABAM program as a datasource. For passing parameters, form Infopack to the program I defined the parameters in the Infoset (SQ02 -> Extras -> Selections -> parameters). After doing this, when I include this Infoset in my new Datasource and save it, I'm not getting the paramter defined in the Infoset. All other fields in Infoset look fine. The parameter defined should appear in Datasource as PARAM_P_<param name>, which can be used as selection parameter in the Infopack. Can anyone tell what I'm missing out and where?
Thanks in advance!
- Sree

Hi Sree,
Try testing your datasouce in your source system with tcode RSA3? Can you get data back from that?
Have you defined that field as a selection field in RSO2?
Hope this resolves the issue for you. Cheers!

Similar Messages

  • Extract error for an Infoset Query based Datasource

    Hello All,
    When I test a Info set Query Extraction in RSA3, I am facing the error message:
    The field 'ZBW_EXTRACT' is unknown, but there are following fields with similar name '%COUNT-ZBW_EXTRACT'.
    Syntax Error in Program 'AQZZSYSTBWGENER.....'
    The Program is an Internal system generated program.
    Has anyone faced the issue and know the way out..?
    Definitely, will award points..
    Thanks in advance,
    Ameya.

    Hi Ameya,
    which system are you testing this? I mean are you testing this in dev or qa? If you are testing in QA, make sure you import the infoset correctly. It is a different procedure. Hope it helps.
    Thanks and Regards
    Subray Hegde

  • BW Datasource on an Infoset Query based on 2 DSO Active tables

    Hello,
    We have created a Datasource in the BW system over an Infoset query (through SQ02) built on 2 DSO tables.
    In RSA3, this datasource is working fine - it shows us some data (close to 1000 records).
    The issue is when i try and run a infopackage for the datasource.
    The request times out and no records are fetched.
    I have added all the users to the Infoset user group - so, no issue with the authorization.
    IDoc Statuses changes from 53 --> 62 --> 64 --> 50.
    The extraction process does not complete - does not get the no. of records sent.
    Can anybody point to a probable cause here?
    Thank you.

    IDoc logs do not say much.
    Status Record 53: IDoc was successfully transferred
    Status Record 62: IDoc passed to application; Direct call started
    Status Record 64: IDoc ready to be transferred to application; No filter, no conversion
    Status Record 50: IDoc added
    Then, it does not go any further.
    We're using the Datasource on the Infoset query because we could not use the traditional BW infoset.
    Datsource is used to feed a DSO as we directly could not use anything else (we're trying with an expert routine also).
    The issue is that the base DSO tables are huge and querying on them (using SELECT) is taking a very long time.
    So, we thought of using an Infoset to create a view and then populatet he data.
    In an traditional infoset, we could not specify a condition with a range. So, the infoset query through SQ02.
    I have not tried using an APD, but that might be a good option.
    Only thing, we'll have to use a Direct DSO - which i am not sure will satisfy our requirement.
    Thank you.

  • Advices about creating a datasource from an infoset query

    Hi all,
    i have to create a datasource with extraction from an infoset query in R3, i have many questions:
    1- i have heard about the bad performance using a Datasource from an Infoset query, how can i improve this?
    2- The infoset query doesnt exist in R3 Develop, but this exist in R3 Prod, what do i must to do? create a false infosetquery in R3 D, with just the same name of the info set query in R3 Prod? or what else?,
    3- some material to improve this development about create datasources from an infoset query.
    thanks guys!

    Hi,
    You can verywell use infoset query if you are doing following things
    Join using Keyfields to retreive data from tables
    If not using keyfields create index for those table fields  in those fields which will improve in accessing database
    Try to use minimum of tables of small size dont try to join big tables like GLPCA and all.
    Try to load small set of data like a period or month. Dont try for a year or so.
    if your performance is good for aperiod you can go for a year.
    If you are good in function module you can try function module in which you will have the option of specifying no of records to be selected usign package size.
    Hope this helps for you.
    Thanks,
    Arun

  • Additional fields in infoset query can not be used as datasource fields

    I create one infoset query with additional fields (using ABAP code) in R/3. When I create datasource RSO2 using this infoset query, system only show all fields without additional fields that I enhanced in infoset query. Does that mean we can not get additional fields information in generic datasource creation that we enhanced in infoset query?

    dear Awa,
       you are enhanced some fields in r/3.right that fields are  shown in
    rsa6 select your data source click on display your datasource then select
    extract structure its shows how many fields are haveing particular
    datasource .or otherwise goto rso2 select your data source display
    double click on  your extractstructure  its show how many fields haveing
    the particular datasource. check the Rsa6 what ever fields you newly added that field default hide mode
    you remove the hide tickmark.

  • Data load failure with datasource Infoset Query

    Dear Experts,
    I had a data load failure today,where i am getting data from the datasource which was built on Infoset Query.
    we had a source system upgrade and when i checked Infoset query in the development of Source sytem  im getting the below message :
    "Differences in field EKES-XBLNR
         Output Length in Dictionary : 035
         Output Length in Infoset : 020
    Message was saying Adjust the INFOSET,I dont have authorisation to create the transport in the source system.I requested the respective person to Adjust the Infoset and also to regenerate the same and move to production system.
    I think this will solve my problem,Please correct me if am wrong.
    Regards,
    Sunil Kumar.B

    Hi Suman,
    i am still facing the problem even after adjusting the Infoset.The problem is we are facing the short dump with length mismatch.
    when i checked the Infoset we are taking the field xblnr from table EKES and data element for teh field was XBLNR_LONG(char-35) but when i checked the datasource in RSA2 the dataelement for XBLNR was showing as BBXBL(char20).
    i think this was causing the problem and i checked in SQ02 we will take the field directly from the table and how there is chance to change the dataelement.
    Please help me to correct the same.
    Regards,
    Sunil Kumar.B

  • Creating Infoset query based on ABAP program

    Hello
    I have 3 tables FEBEP, BKPF and BSEG and I need to join the 3 tables based on:
    FEBEP-MANDT = BKPF-MANDT = BSEG-MANDT
    FEBEP-NBBLN = BKPF-BELNR = BSEG-AUGBL
    FEBEP-GJAHR = BKPF-GJAHR = BSEG-GJAHR
    Then I have a few view fields from all the 3 tables. After this I can build an infoset query based on structure + ABAP program, and a generic datasource on top of it.
    Can someone give me the ABAP code to be written SE38? Also should I select integrated program/external program in the infoset query?
    Thanks,
    Srini.

    Hi,
    Even if you create an ABAP program for infoset, you will writing a SELECT statement from BSEG table which is quite huge.
    And you will putting JOIN with other tables.
    Performance wise this is not advisble.
    Why do not try the following other tables and check if the fields you need are available?
    You can't join BSEG as it is a Cluster Table.In the place of BSEG you can use:
    Account Recivables data use BSID and BSAD tables
    GL Account Related data use BSIS and BSAS tables
    Account payables data use BSIK and BSAK tables
    Thanks.

  • When we would create genric extractor on a infoset query

    hi  All,
    we have infoset queries inour R/3 But very confused whether i should i go for generic with querry or genric with views.
    Actually the scenario is I have the insfoset query on logical data base
    I can create a generic extractor with view from the tables used by above infoset query. but there are structures in that infoset query .
    so to create an generic extractor with  view on a structure  is not possible neither a function module is  possible.
    last option is creating generic extractor with view and enhancing the extractor with  required fields form structure.
    but i feel it would be very easy creating a generic with the same infoset querry
    can u give me suggestion pls
    All the answers  would be appreciated by points
    Thanks and Regards,
    D

    Hi...
    SAP Query / InfoSet Query is a powerful tool for defining reports in the SAP
    source systems and supports different forms of reporting. It allows users to define
    and execute their own reports on data in the SAP system without any knowledge
    of the ABAP programming language.
    Reports are structured by entering texts and selecting fields and options in SAP
    Query. The relevant fields can be selected more easily using InfoSets (before
    release 4.6C, InfoSets were known as functional areas).
    InfoSets are viewed as DataSources. These data sources can be used for extracting into SAP BW.
    To create an InfoSet from the DataSource definition, perform these steps:
    1. Fill out all the required entry fields (application component, descriptions).
    2. Choose Extraction from Query.
    3. Choose Save. A new screen is displayed.
    4. Assign a name for your InfoSet and choose InfoSet Maintenance.
    5. In the screen that follows, choose Create.
    6. Select the data source (DB tables/views, joins, logical DB, and so on).
    7. Define the field groups and assign the fields
    An InfoSet is a special view of a dataset (logical database, table join, table,
    sequential file) that is used by SAP Query as a data source. InfoSets, therefore,
    determine the tables or fields in these tables that can be referenced by a report. In
    most cases, InfoSets are based on logical databases.
    SAP Query features a component for maintaining InfoSets. When you create an
    InfoSet, a data source in an application system is selected. SAP Query is relevant
    for the Business InformationWarehouse because it allows you to define the extract
    structure by selecting fields in a logical database, table join or other datasets in the form of an InfoSet. In this way, you can use the generic data extraction function for master or transaction data from any InfoSet. When you do so, a query is created for an InfoSet that retrieves data and transfers it to the generic extractor.
    InfoSets represent an additional, convenient data source for extracting data
    generically. Logical databases in all SAP applications, table joins and further
    datasets can be used as a data source for SAP BW.
    Hope this would help u
    with regards,
    hari kv

  • Rso2 infoset query  generation procedure

    How to generate data source in rso2 using infoset query to get distinct record

    Hi,
       Generating Datasource from Infoset is not different from Generating DataSource from View or Function Module.
    Create infoset in the source system from SQ02.
    go to RSO2. Provide the Datasource Name. go wiht create.
    Select the Infoset Push Button, provide description.
    provide the infoset Name. Let me know if you have any Issue.
    Save the DataSource. check RSA3 for Data.
    Regards,
    Nagesh Ganisetti.

  • When to go for generic extraction using view and infoset query?

    Hi,
                        Can anyone clarify me when we should go for generic extraction using view and when we should go for generic extraction using infoset query....
    Also what is the difference between view and infoset?
    I tried but could not find out....
    Regards,
    Kalyani.

    Hi Kalyani,
    We normally go for View or infoset when the data to be fetched in BW is distributed in different tables in SAP R/3.
    Had the data been available in one table we can easily build our datasource on that table but if there are more tables then its not possible to do it without Views or Infosets. You can use Function Modules to build your datasource in case it involves complex logic to figure out the data from various tables.
    Depending upon the table relationships we create view and include various fields from these tables in that view. Same is with the Infosets, you can have more flexible options like Outer Join, left outer Join etc.
    Regards,
    Pratap Sone

  • Generic Extractors for HR Reports using views and Infoset Query

    Hi Friends... I am working to come out with the HR reports in BW for the HR reports which are already there in R/3. The HR reports in R/3 are created based on Infoset Query.I could not find any standard business content cubes which can give me these reports.
    1)So please can anyone give me step by step approach so to create a generic extractors based on Infoset Query.
    2)And also how to populate the data into the fields of the generic extractor which is created by Infoset Query( Please provide any sample ABAP code if available)
    3)can anyone give me step by step approach so to create a generic extractors based on View/Table.
    4)And also how to populate the data into the fields of the generic extractor which is created by View/Table( Please provide any sample ABAP code if available)
    Thanks

    Hi Kalyani,
    We normally go for View or infoset when the data to be fetched in BW is distributed in different tables in SAP R/3.
    Had the data been available in one table we can easily build our datasource on that table but if there are more tables then its not possible to do it without Views or Infosets. You can use Function Modules to build your datasource in case it involves complex logic to figure out the data from various tables.
    Depending upon the table relationships we create view and include various fields from these tables in that view. Same is with the Infosets, you can have more flexible options like Outer Join, left outer Join etc.
    Regards,
    Pratap Sone

  • Mandatory fields for Infoset query

    Hi all,
       I am creating a datasource using Infoset queries.to test it, how to make a field as mandatory in selection screen.
    thanks in advance.
    Reagrds,
    Murali

    hi murali,
    Mandatory selection screen:
    When you display infoset go into the infoset>Goto >selections or click on the app tool bar button for selections,
    it will open up a table will all the screen fields. Adjacent to these, there are 3 check boxes for Standard selection, required entry and default. Check the required entry field.
    You would have to place the code in the PBO. In case of selection screens, you will have to do it in the AT SELECTION-SCREEN OUTPUT EVENT.
    Doesn't really make much sense to try and do it in the PAI ( = AT SELECTION-SCREEN).
       You can do it using customer exit. You have the options to verify a variable input and display a message back to the users, check the attached documents. The check can be done in the customer exit step I_STEP = 3.
    https://websmp102.sap-ag.de/~sapdownload/011000358700002765042003E/HowToVerifyVariableInput.pdf
    A tool that provides reporting on one or multiple ODS Objects. InfoSet Query provides Web reporting capabilities (known as ABAP Query or SAP Query).
    Check this link.May be it can help you.
    http://help.sap.com/saphelp_nw04/helpdata/en/ed/084e3ce0f9fe3fe10000000a114084/content.htm
    Hope IT solves ur problem
    Thanks
    Varun CN

  • Help with Infoset Query

    HI i have created an Infoset Query in SQ02.
    what would be my next step, before assigning it to a datasource, i want to check whther it has the valid data in it or not. could it be possible.
    If so can some one guide me how can i do that and so on...
    Thank You,
    kris..

    You can chekc the data with Query on InfoSet. This can be done with SQ01 transaction code.

  • How to see the underlying program for Infoset  query in ECC?

    HI all ,
    we have generic datasource based on Infoset .
    now ii need to add 2 fields from batch characteristics .
    my question is how to go & edit the underlying abap program .
    i have added the fields to the extract structure , but not populated the 2 fiields .
    regards ,
    srinivas .

    Hello,
    Go to SQ02 T code -
    > Give your Info set Name -
    >Click on your Info set -
    >There top you will find Option GO TO click on Go To then you will get Global Properties -
    >if you click on Global Properties -
    >You will get another scree there if you click on External Program------->You will get  underlying program for Infoset  query in ECC.
    if you find the answer usefull kindly asign some points.
    Regards,

  • Infoset Query is not available for generic Extractor

    Hi,
    I've created an infoset in SAP ECC with sq02. Then I've created an Infoset Query on top of this Infoset, because I wanted to exclude records with specific values. Now I want to use this Infoset Query (with the filter restrictions) in my generic DataSource. I can only chosse the Infoset, but not the InfoSet Query. Normally I use the filter in the InfoPackage, but neither IP nor DTP can exclude values with a pattern (f.e. exclude all record that contains a $ symbol in the string)
    Any suggestions?
    Thanks and regards,
    Sebastian

    I agree with Jen, that BW side routines would work just fine.
    If it is extractor performance you are worried about and that is why you want to build the $ exclusion in the select, then I would suggest just creating an extractor from scratch using a custom written function module.  It's actually very strait forward and provides many advantages over table/view/InfoSet based generic extractors.
    I am not a fan of using InfoSets for generic extractors.. but you can create InfoSets based on a data read program in which case you code all the selects and whatnot.  But if you go that far with the InfoSet, why not just write the FM...
    Thanks

Maybe you are looking for

  • Inutilização de NF - Não atualiza ERP - ERP error 104

    Olá! Estamos com um problema na inutilização de uma NF. A mesma teve a inutilização autorizada pelo SEFAZ e consta com o status code 102 no GRC. Porém houve um problema na atualização do ERP e este consta como ERP error 104. Na J1BNFE esta NF aparece

  • UMEBackendconnection (pool size)

    Hi, We are configuring AS Abap as our UME connection in SAP NW 7.3 ehp6, however we are unaware of the fact as to how to define the parameters for RFC destination "UMEBackendConnection" We require information about how to configure the pool settings

  • IPhoto unable to import photos

    When iPhoto first comes up, i get two messages that say that there are two photos that were not imported from the library. I tried selecting "do not import" and also "import" but they are never imported even though they say that they were put in the

  • "Unsupported image format"- Has nothing to do with RAW images-

    I have a very weird problem with one of my Aperture 3 libraries. This only seems to apply to one library, all the others I tested seem to work just fine. This library was created on my MBA and transfered to my iMac when I returned from my trip. It wo

  • Duplicate Birthdays in Calendar

    I have an issue of when the Birthday Calendar is activated, birthdays are showing up multiple times.  The only account I use for my calendar is my work Exchange Account.  When I deactive that account, they go away.  However, doesn't seem to be a prob