Infoset Query Modification Suggestion

I'm new to ABAP Infoset and logical database, and need your help.
  I have a query running based on Infoset Z_FI_CHILE_XX(same copy from /SAPQUERY/FI_CHILE_PERU) and logical database SDF. Now I'm trying to modify the selection screen, for example: get rid of 'Fiscal year' and 'Period', and adding 'Posting data' criteria.
  As I can see so far, 'Fiscal year' critieria is from logical database SDF, and 'Period' was adding in Infoset. Please give me some suggestion, should we modified logical database, or you have better solution?
  Also do you have better documentation on how to modify the selection criteria in infoset rather than SAP library?
  Thanks a lot!

Thanks for all help from you.
  I realised that my problem actually can not be just simply solved by modify the selection screen, since I need selection some periods from one fiscal year, then get some periods from another fiscal year, which two part of periods are not the same. Also I need the sum the total from all the periods that I selected, instead of list them in report.
  My solution is modified the code behind the infoset to control selection in different periods for different fiscal year, then adding the subtotal total section in infoset Query, finally use a menu function(total drilldown) to leave only subtotal sections in report.
  Thanks anyway, if you think there has better solution, please feel free to let me know. I would like to learn from you.

Similar Messages

  • InfoSet Query modification error

    Hi,
    I am trying to modify a InfoSet Query in SQ01 developed by a SD consultant last time. I already assigned my user ID in the User Group (in SQ03) which is referred by this Query. At the same time, I also assigned the Change Authorization to my ID.
    After that, I modified this InfoSet in the SQ02 to add on 1 table and the Save is successful. Then I try to modify the display layout of the Query in SQ01. When I save it, it give me a message "The query is locked for changes by SDUSER". The ID SDUSER is used by the SD consultant last time. Then the modification is not saved.
    I already checked in AL08 and also SM04, and found that this user is not log in at that time.
    I already done whatever I know to try to solve this problem but I still can't settle it. Can anyone please help me on this? Why can this happen? How can I unlock it?
    Thank you.

    Hi,
    the lock was made by SDUSER when he created the querie. It's an option in the first screen "Title, Format" (specials attributes). When this option is select, only the specific user can change the query (sometimes some modifications are allowed by other user's in specific conditions).
    The only way of resolving the problem, is the SDUSER to disable that option from there. After that you will be able to change it.
    If that user doesn't exists, you must call the Basis team to create the user again, log on, and change the option.
    Regards,

  • I am facing a problem in a crystal report which is based on Infoset query

    Hi All,
    I am facing a problem in a crystal report which is based on Infoset query.in the Cost Analysis - Planned vs. Actual Order Costs
    There are two querys like Query: CO_OM_CA_20_Q1 and InfoSet: ZBPBI131_INFO_ODVR. I build infoset query based on sap best practice user guide but problem is not able to find CO_OM_CA_20_Q1
    Best Regards,
    Srinivas

    Hi,
    I would first of all suggest you don't open the same question twice. this looks like a duplicate to this entry:
    Best Practices v3.31 - SAP InfoSet Query connection
    Did you assign the queries and the infosets to an InfoSet user group and you assign the SAP account to it as well ?
    Ingo

  • InfoSet Query - Long Description while selecting variable values

    Dear Experts,
    We have an InfoSet Query on different InfoObjects like 0CUSTOMER, 0CUST_COMPC etc and the common link between these InfoObjects is CUSTOMER.
    We have a variable created on this CUSTOMER. The requirement is that when this query is executed, user should be able to select a value of Customer (F4 help) and at that time, he should be able to view both Key and Long Text of Customer.
    We know that if we change the CUSTOMER InfoObject --> BEx Properties tab, then we can display Long Text and Key in Query Selection Screens. However we can not do that because it would affect all queries in which this InfoObject is used.
    If we go to Query Design, and choose "Long Text and Key" in properties of Customer, then system displays Long Text and Key of Customer but after the report execution is done.
    We want to display the Long Text of Customer to User at the time of selection and that too without making any InfoObject level change.
    If it was InfoProvider, we could have done it using "Provider specific properties of Characteristic" option. But this is InfoSet and that option does not appear here.
    Please suggest the solution.
    Regards
    P

    Rohit,
    Are you looking to display long text for infoobject instead of short description ?
    Then go tp rsd1>infoobject>display/change-->master data/texts -->text table properties -->check long text exists.
    It supports a long text field with a length of 60 characters
    Activate the infoobject
    --Doodle
    Message was edited by: Doodle

  • Infoset Query Wrong result after removing document number in the drilldown

    Hi Friends,
    I have 2 oDS,billing ODS and Condition ODS.I have created an infoset query based on these two ODS.
    From my Billing ODS i need QTY and from Condition ODS i need Value,Discount etc.
    Since there are more than one record in condition ods for each and every document of billin gods,i have divided the qty using number of records in the query.
    Im getting wrong qty if i run report based on customer or material,but if i drilldown based on document im getting the correct quanity.
    Can any one help me..
    Thanks & Regards
    Sudhakar

    Thnaks Oscar and Ganesh for your interest.
    FYI,my infoset is created based on bill doc and item number which is available in both the ODS.
    Here,for every document in Billing ODS,there are more number of documnets in Condition ODS,so the bill qty is getting added according to the numvber of records in Condition ODS.
    Eg.Billing ODS: Doc Num:100012, Qty = 8.if 10 records are ther in condition ODS,then in the infoset my QTY becomes,
    Doc Num:100012, Qty = 80.
    So in the query i divided it by number of records to get the qty and is coming correctly for documnet wise report.
    Problem comes when i remove documnet from the report and drilldown to higher level,say material,then it is calculated wrongly.
    Your suggestions plz..
    Regards
    Sudhakar

  • Infoset Query Returns Wrong Data

    Hi there exports,
    I created a infoset query based on 3 DSO's 0PUR_O01 (Purchase Order Items), 0PUR_DS03 (Purchase Order Item Schedule Line) & a Z-DSO (Material Consumption).
    I need information by PO Number (Item, Material) and the total consumption for that material from the Z-DSO irrespective what the item & PO Number is.
    My link to Z-DSO is material & plant. My problem is that the info from the orther 2 DSO is triple when I run my query.
    Any suggestions?
    Thank you
    Dirk

    Hi,
    This issue arrises due to the infoset property, ie. Infoset provides intersection of data.
    So for a single combination of material and plant in Z-DSO, there might be multiple (here 3)records in other two DSO so you get the triple amount in Query.
    Inorder to overcome it you must ideally join the DSO in a infoset based on the same key fields..
    Hope it helps..
    Regards..
    Umesh.

  • Infoset Query Error

    We have created infoset in 2004s which includes 2 cubes. As the navigational attributes of the Cubes were not available in the infoset, we had included the Infoobjects in the infoset.
    But after patch upgradation to patch 16, the infoset structure was changed and now in the infoset the Navigational attributes of the cubes are also available. Because of which the Queries based on the infoset are currently not executable. And pops the below mentioned error:
    But, the query based in the INFOSET started giving errors:
    1.type_X
    2.The “Infosetname_FX” object not in infoprovider(Where FX is like F1,F2….)
    Has any one encountered such kind of issue……..

    hi rohit,
      after you make any changes in cube or info object levels and these are using in infoset.
    any modification has done in cube level we have to adjust the infoset,with that you can encount your prob.
    goto t.code rsiset
    give u r infoset name
    goto to infoset option---select the adjust activate this
    with this you can come out error
    expecting quries can work now...........
    Note*--please reward points if solutin found helpful to you
    mahesh.

  • 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

  • Problem in InfoSet Query data

    Hello All,
    I have a specification to develop an infoset query in HR.The problem i am facing is i need  particular PERNR's listed in output of query which satisfy few condtions like p000-massn = 31 and p0000-massg = Ub or Uc. this is an example of one condition. I tried to wirte my code in record processing and end of selection( before listing) . but there is no data coming at all.
    Please suggest how to go about this .
    Thanks in advance
    Nidhi.

    Hi Nidhi,
    Please write your code in Record Processing event of code section of Infoset . And instead of IF , use CHECK condition statement.
    CHECK P0000-MASSN = '31' AND ( P0000-MASSG = 'UB' or P0000-MASSG = 'UC' )
    OR P0000-MASSN = '91' AND P0000-MASSG = 'UE'
    OR P0000-MASSN = '10' AND P0000-MASSG = 'U2'.
    CHECK SY-SUBRC EQ 0.
    Edited by: Dinesh Tiwari on Oct 1, 2009 1:42 PM

  • Information message in infoset query.

    hi all,
    i have added a field into the infoset query adn im using s_pho_48000513 . my probelm is when ever im opennig the query im getting information message as some selection fields are not available.does any have idea why im getting this message ..where i went wrong in ading the field to infoset.what check should i do.please suggest.and another thing when im doing switch off object selection from extras im not getting this information message but this field is comming in selection fields from infoset with default selected with enable mode and all other fields selected with disable mode.
    any inputs is apreciated..
    regards,
    suha

    Remove those fields/Infotypes from the infoset with the help of SQ02 from that infogroup
    Thanks
    Jaydeep jadhav

  • Email Infoset Query Result

    Is anyone aware of a way to email the results of a infoset query run on R/3 . Would like to schedule the query to run then have it emailed out automatically.
    Any help at all will be rewarded with points
    Thanks
    Richard

    You can try this..Write a custom Program that runs the query using SUBMIT <query> to SAP-SPOOL and RETURN. Retrieve the spool using the function module 'RSPO_RETURN_SPOOLJOB' & email it using another function 'SO_NEW_DOCUMENT_ATT_SEND_API1'.
    Regards,
    Suresh Datti
    I like Rich's suggestion
    Message was edited by: Suresh Datti

  • Infoset query to query

    Hi ,
    If i run a existing query it is showing any display.
    If i run it through infoset query it is giving output ,if i want to get output through query execution how to do it. give me some useful suggestions.
    Thank u.
    Regds,
    devika

    Hi Gaurav ,
    Thank you . I recreated the variant and the problem is solved.
    Regds,
    devika.

  • Employee search : Infoset query

    Hi All,
    We are trying to configure the employee search in ESS. We have requirement in order to display the Position, date of entry into the position (start date), or when the employee got promoted into that position.
    As default, ESS displays the position for each of the respective employees search results. We have explored the option Who's Who (ESS): Selection and Output in spro and this is an infoset query submitted to Employee search service resulting the appropriate fields in Portal.
    I am finding difficult in order to display the date of entry into respective positions ie what would be the technical name (field) to be passed to this infoset query.
    Thanks in advance.

    Thnx for your valuable inputs pooja.
    As suggested, I have tried to create a query in standard Infoset HR_XX_PA_ESS. However, it doesn't allow me to do it. Even I have tried with ABAP client with all of the developer rights.
    I have created a Z-copy of that standard infoset, then it allowed me to create query field in that Z-infoset. But, how can I refer this customized query from this Z-Infoset to Who's who selection output screen (PZ01C).
    Please share your experiences.
    Regards,
    Anil Kumar

  • Missing variables in Infoset Query.

    Hi All,
    0P_KEYD2 is a variable for characterstic "Posting Date" in the  query which fires on ODS 0FIAR_O03.I have created an Infoset on ODS 0FIAR_O03 and 0CUST_SALES(Master Data)and created a query on this infoset. But I am unable to see variable 0P_KEYD2 for Posting Date in the Infoset Query.
    (There are some other variables too which are not visible in Infoset Query, these include - custom "Z..." variables & BC variables, with SAP exit and with User entry, etc)
    Could anyone suggest how to access this same variable for query on infoset as in ODS query?
    I tried having an new Infoset with just the ODS 0FIAR_O03, but here again these variables are missing for this characterstic (and possibly other variables for other characterstic), while if I try to build the query on the above ODS directly I get the variables!
    Version: We are on BW 3.5
    Thanks,
    Melwyn Joseph
    Message was edited by: Melwyn Joseph
    Message was edited by: Melwyn Joseph

    Hi,
    I'd put this query in SDN quite some time back..but didn't get any response then.
    As Raymond said above, that is what I'd done in my case. The original variables are SAP exit (u can view their code in the standard SAP FM's). Here the code refers to other variables/objects with their specific tech names (or something similar..don't remember it now). In infoset, as we dont get the original tech. names of the objects in the query ...these SAP exit codes will not work for these variables.
    The solution is to create your own custom variables & populate it in Customer Exit. U can get the logic from the SAP exit code...its not that difficult to understand.
    cheers,
    -Me

  • Infoset Query Performance

    MSSQL Server 2000
    BW 3.1C
    R/3 6.20
    BW 3.0B Frontend
    I created an infoset with 2 huge tables (one holding approx. 10 mil records w/ 20+ attribs, and the other holding approx. 3 mil records w/ 30+ attribs).  I didnt include ALL attributes in the infoset, maybe just 15 total on both of the tables.  They do have a common field to join, one is the key field of one table, and the other is the attribute of the other.  They are both info objects with master data.
    The join is an inner join in which the tables have a 1 to many relationship.
    I created indeces individually for each table.  But when I run a query that SHOULD use the indeces, it still takes a very long time to run (approx. 5-10 mins, per navigation).  When viewing the Run Schedule for this query, it does show that it scans for clustered indeces for the (many table) and regular indeces for the (one table).  But
    Any suggestions on how I could have this query run faster?

    To whom are interested in the Infoset topic.
    As of Release 2.0B, the InfoSet Query is available in BW as a tool for special requests from the area of the master data reporting. A new InfoProvider, also known as an InfoSet, was introduced into BW for Release 3.0A.
    The OSS Note 486789 provides recommendations about using InfoSets in different BW releases and explains in more details the difference among SAP Query, InfoSet Query, InfoSet (Basis), InfoSet (BW).
    Hope this can be useful for all of you, guys.
    Bye,
    Roberto

Maybe you are looking for