Infoset Query Restriction

Is there a way to restrict master data within an infoset query? I only want master data for a certain sales organization in the infoset query because this is joined to a cube. The cube does not contain sales org. If I could only have the infoset query display the one sale org master data this join would work.

Hi,
the join function in infoset can't provide you restriction by value.
Alternatively try to filter the infoset on the query level.
Hope helps.

Similar Messages

  • SAP Infoset Query Reporting Set Restriction by Org. Structure

    Dear Experts,
    I am giving some new users a demo on using Infoset Query on an IDES server.
    I am using the user group Personnel Administration (PA) and the HRDATA infoset.
    As per my understanding, I should be able to restrict the reporting set according to organizational structure as the infoset is based on logical database PNP. However I am only seeing "No. of hits" in the restrict by drop-down (as can also be seen in the screenshot).
    What am I missing to be able to see the restrict by option of "Persons along organizational structure"?
    All assistance in this regard is really appreciated.
    Regards,
    Talha

    Dear Azury,
    Thankyou for your response.
    Your solution is perfectly sound for fulfilling the purpose.
    However, because I am conducting a demo, I thought a reporting set restriction on the main screen would be more appealing, than an additional selection screen.
    In a demo screenshot I have seen that the restrict by option "Persons along organizational structure", is listed right under "No. of hits" like in my screen shot. Can you shed some light on that. I am attaching the demo screenshot I am talking about for reference as well
    Thanks,
    Talha

  • Infoset/query : how to fix a selection field value?

    I am writing queries with SQ01 and designing Infosets with SQ02.
    I have to restrict the results of a query to a specific plant.
    This can be done by adding the plant field in the selection screen of the query and by asking the users to fill always the same fixed  plant number when the query is started. Another solution is to filter the output.
    Isnt it possible to simplify this by forcing the plant number in the initialization of the Infoset values without display of this field in the selection screen? This value has to be initialized before the table containing the Plant field is joined to the other tables?

    Open SQ01 transaction,give your query name, click on infoset query button.
    On the right side of the screen you can define default values for those fields.
    If you want to disable the same field in selection creteria then open your infoset in SQ02
    transaction and click change, click on extras buttonin appllication tool bar,on right hand side
    in code tab you can add your logic.

  • Infoset query: Runtime Errors  TSV_TNEW_PAGE_ALLOC_FAILED

    Hi
    I have searched the forum and could not find suitable solution for my problem.
    We have an infoset query whose data source is an ABAP program and this is within our BW system only. Earlier it used to run perfectly fine. Recently, due to the increasing data, the load for the same is failing because of memory issue with runtime Error  TSV_TNEW_PAGE_ALLOC_FAILED . The dump occurs within 5-7 minutes of the data load. Once, we give some more filter selections in the infopackage, it runs fine.
    Our problem is neither we can increase the memory any further nor we want to give filter selections in the infopackage. Also, once we execute the ABAP program alone, it runs fine.
    Any help to solve this problem is appreciated.
    Cheers
    Chanda

    Hi,
    There are 3 ways to avoid this kind of problem:
    1) Reduce the data set - if it is possible to process this in smaller
    chunks then please do. This is an infoset query - please be more restrictive in your selections
    - please refer to note 354657.
    When you work with infosets that use tables or joins then it is
    possible to read packages (from Rel. 6.10 on). When you work with
    infosets that use logical databases or data retrieval programs than
    it is not possible to read packaged - by technical restrictions.
    That means that the query is executed completely taking all restrictions
    into account and the result is stored internally.
    2) Re-allocate some of the unused shared memories to program memory.
    A prime candidate for this is Roll and Page "In Memory" values.
    Alternative memory management via PHYSMEMSIZE generally overallocates
    roll and page memory. Please reduce the amounts allocated to the "in
    memory" part (see ST02) using the parameters below, for instance:
    rdisp/ROLL_MAXFS....Total amt of ROLL (Filesystem+SHM); in 8KB blocks
    rdisp/ROLL_SHM......Shared memory element of Roll; in 8KB blocks
    rdisp/PG_MAXFS......Total amt of Page (Filesystem+SHM); in 8KB blocks
    rdisp/PG_SHM........Shared memory element of Roll; in 8KB blocks
    =>Filsystem amt = MAXFS - SHM
    60MB or so each in memory should be sufficient.
    This should allow an extra 260Mb or so for process memory.
    Bear in mind however that Roll_SHM MUST be greater than 10% of
    Roll_MAXFS.
    This will not affect alternative memory management operation in any way.
    3) Reduce the em/global_area_MB from 128 to 64MB.
    These measures should give you ~320MB additionally per work process.
    To get even more - if there is a 64 bit machine in the landscape then
    redirect the load there.
    I would like for you to review the SAP Note 712664. Although
    the Notes 20527, 369726 and 166551 specifically refers to this
    and has helped resolve multiple performance problems.
    I hope it can help you.
    Fran.

  • 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

  • Infoset query BI 7.0

    Hi All BW gurus ,
    i want a clear picture how to create an infoset query and when to go for infoset and infoset query in GENERIC Extaction . anyone pls send the screen shots how to create and extract data to bw side from  infoset query  ,
    my email is [email protected],
    100% points will be assined to the gurus
    regards
    Sherwin

    <b>Look at</b>
    http://help.sap.com/saphelp_erp2004/helpdata/en/92/43ec39d0383f09e10000000a11402f/frameset.htm
    Re: Infoset
    https://www.sdn.sap.com:443/irj/sdn/thread?threadid=199410&messageid=2217326
    https://www.sdn.sap.com:443/irj/sdn/thread?threadid=189150&messageid=2113030

  • Infoset query of vendor payments at the cost distribution level

    We would like an infoset query of vendor payments at the cost distribution level of the document.  The issue seems to be joining vendor to the document cost distribution lines. 
    1.) BSAK + BSIK can be combined with an infoset data structure but only contain the vendor line of a document;  the cost distribution lines are not in the tables. 
    2.) BSIS + BSAS can be combined with an infoset data structure but lack vendor data and joins (to a vendor source) are not an option with data structures.  Vendor data added with an additional field is too slow to be a primary selection field. 
    3.) Logical data base KDF in an infoset returns only the vendor line of a document, not the cost distribution lines. 
    4.) Logical data base BRM in an infoset can have vendor from BSAK/BSIK attached by an additional field but performance is too slow to be useful.  Joins are not an option in a logical data base infoset.
    5.) Complete data is lacking when table joins between document cost distribution tables and vendor data tables are possible, (SPL actual line item table & BSIP or FMIFIIT & FMIFIHD).  BSIP lacks AB documents (reversals).  FM tables lack general ledger only documents. 
    6.) BSAK and BSIK together have complete vendor data but joins of both to a basis table do not work well.  Left outer joins are too slow, inner joins won’t work since the tables have mutually exclusive data. 
    It would be ideal to have vendor in BKPF, like FMIFIHD has, but it isn't a field.
    Does anyone know of any other options?  I have seen the helpful thread on How to Read BSEG Efficiently

    Hi,
    This is SAP Business one reporting and printing forum. Please find correct forum and repost above discussion to get quick response.
    Please close this thread here with helpful answer.
    Thanks & Regards,
    Nagarajan

  • Infoset query of vendor payments at the cost distribution level of the document

    We would like an infoset query of vendor payments at the cost distribution level of the document.  The issue seems to be joining vendor to the document cost distribution lines. 
    1.) BSAK + BSIK can be combined with an infoset data structure but only contain the vendor line of a document;  the cost distribution lines are not in the tables. 
    2.) BSIS + BSAS can be combined with an infoset data structure but lack vendor data and joins (to a vendor source) are not an option with data structures.  Vendor data added with an additional field is too slow to be a primary selection field. 
    3.) Logical data base KDF in an infoset returns only the vendor line of a document, not the cost distribution lines. 
    4.) Logical data base BRM in an infoset can have vendor from BSAK/BSIK attached by an additional field but performance is too slow to be useful.  Joins are not an option in a logical data base infoset.
    5.) Complete data is lacking when table joins between document cost distribution tables and vendor data tables are possible, (SPL actual line item table & BSIP or FMIFIHD & FMIFIIT).  BSIP lacks AB documents (reversals).  FM tables lack general ledger only documents. 
    6.) BSAK and BSIK together have complete vendor data but joins of both to a basis table are not an option.  Left outer joins are too slow, inner joins won’t work since the tables have mutually exclusive data. 
    Does anyone know of any other options?

    Hi,
    This is SAP Business one reporting and printing forum. Please find correct forum and repost above discussion to get quick response.
    Please close this thread here with helpful answer.
    Thanks & Regards,
    Nagarajan

  • Crystal report from SAP infoset query

    Hi All,
    I am facing a problem in a crystal report which is based on Infoset query. When I run the report after passing the parameters it gives me an error "Database error occured" "Parameter field value does not exists" "RFC Closed"
    But if I run the same Infoset query from SQ01 I am able to run it with same paramenter and it returns many records.
    To be very precise I am running the best practice crystal report "Cost Analysis - Planned vs. Actual Order Costs" which is based on infoset query CO_OM_CA_20_Q1.
    It throws me error that "Controlling Area does not exists".
    Did anyone faced similar problem?
    Best Regards,
    Chetan

    Hi,
    log into your SAP ERP system using the SAP GUI and choose in the SAP Menu the following path:
    SAP Menu -> Accounting -> Controlling -> Cost Cetner Controlling ->Environment->Set Controlling Area.
    Set the desired controlling area for your user there (DO NOT FORGET TO CLICK ON THE DISKETTE ICON) and try again.
    Regards,
    Stratos

  • 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

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

    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

    Please re-post if this is still an issue to the Business Objects Integration Kits - SAP Forum or purchase a case and have a dedicated support engineer work with you directly

  • How to delete Infoset Query in R/3

    Hi  Gurus,
    I created a Infoset using SQ02 in R/3 and generated the query. Now I need to delete that Infoset query. Please advice me how to delete infoset query from the functional group in R/3.
    Thanks
    Liza

    Hi,
    In SQ01 ,press shift+F7 then find your user group. then from infoset query tab ,select ur infoset.
    and try to delete , I think, it should work.
    Regards
    CSM Reddy

  • Issue while extracting data using Gen DS of Type Infoset Query

    Hi All,
    We have a Generic Data source created using the Infoset query. I get some data discrepency when i am extracting the data with the same DS. The data for the Field Amount in the R3 and the PSA  is different. When i try to check the same using the RSA3 T-Code i am unable to execute the Gen DS in R3 production where as its working fine in R3 Dev, and i am able to execute the other DS in the R3 production using the RSA3 T-code.
    My concerns ::--
    1. if the DS is working fine in R3 Dev in RSA3 the y i am facing the problem in Production.
    2. Y i am getting the different data in R3 and PSA since PSA shuld be the replicate of R3?
    3. How can i resolve this problem.??
    Thanks in Advance
    Regards

    Thanks venkat,
    I am having the authorization to execute the query in R3 production, As  i am able to execute the other DS in RSA3 . But not able to execute this DS i had also checked it is active n working fine when loading the Data.
    There is only one routine ie to transfer rule  from lower to upper of a char value.
    As der r routines in Update Rule but i have to get the same data in PSA which is der in R3.
    The Routine of Update Rules will be executed when loading the data to the Targets right so the data may b vary in Data targets but y i am getting different data in PSA .
    Pls thru some light.
    Regards

  • Runtime error while executing infoset query

    Dear Experts,
    When we execute infoset query we get following dump :"
    " An SQL error occurred when accessing a table."
    Database error text........: "ORA-25153: Temporary Tablespace is Empty"
    Internal call code.........: "[RSQL/FTCH/EBAN ]"
    Please check the entries in the system log (Transaction SM21).
    You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:
    "DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC
    "/1BCDWB/SAPLIQG000000000015" or "/1BCDWB/LIQG000000000015U02"
    "/1BCDWB/IQG000000000015EXTR"
    can any one hve idea about the above error.
    With Best  Regards,
    Jaspal

    Hi Jaspal
    Looks like a BASIS issue.
    Check with BASIS, they need to regularly monitor the tablespace and file system, at OS level
    Regards
    Madhan D

  • InfoSet Query: Syntax Error while generating the program.

    Dear All,
    I have a Query in CRM system which contains an Infoset based on LDB.
    The InfoSet Query throws up a Syntax error while generating the program.
    So, we are not able to change the Infoset using the Infoset Query through SQ01.
    The error is as follows:-
    Syntax error in program "AQZZ==/SAPQUERY/CRM_ACTMON1 ".
    Error in the ABAP Application Program
    The current ABAP program "CL_QUERY_OUTPUT_DEFINITION====CP" had to be
    terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "AQZZ==/SAPQUERY/CRM_ACTMON1 "
    in include "AQZZ==/SAPQUERY/CRM_ACTMON1 " in
    line 28:
    ""CRMT_REPORT_LOCATORLIST" must be a flat structure. You cannot use int"
    "ernal tables, strings, references, or structures as components. -"
    Please help me arrive at an solution, so that we are able to change the Infoset through the InfoSet Query.
    Awaiting your reply as soon as possible.
    Thanks and Regards,
    Pankaj.

    There is an error in your query, specifically in the definition of CRMT_REPORT_LOCATORLIST. In the short dump (transaction ST22) you will see more details and the exact location of an error if you just scroll down.
    I can't tell more because this problem is specific to your system, to which I have no access. Read the whole dump and look at all the objects mentioned there.

Maybe you are looking for