Disable Query name assignment to documents in BI7

Hi gurus,
When i attach a document to InfoProvider data in query BI 7, the name of the query is assigned to the document.
So i can't find the document in another query with the same axes.
How I can disable the assignment of the query name to assign the document only on axes?
Thanks,
Franck

Ok. i try to explain this detail.
You can have a seperate documentation for Infocube & for  query.
For Infocube : Select the Infocube & then define the documentation as RSA1 -> Go to -> Documents
For Queries : each query will have its own documentation and that can be defined in Query properties
in this way,you can have the Infoprovider documentation independent of the query
Hope this is clear now.
Sreeman

Similar Messages

  • Windows spooler display document name as local document

    I saw the document name with local path at Windows spooler, even if the PDF file came from http or ftp server. I guess, it is depend on the server, because the PDF files which came from one server are displayed the file name with URL as document name, but it came from other server is displayed the file name with local path - C:\Documents and Settings\username\Local Settings\...
    Could someone tell me what is difference between local path and URL path?

    Here is the approach to read document set columns and assign to other webparts:
    for each document set you can find the id when you clicking on the document set or navigating to the welcome page,
    using this id read query string and  the associated item column values and assign to otherwebpart .
    Reference code:
    //page_load for other webpart read the query string of welcome page
    if (Page.Request.QueryString["ID"] != null)
                    ID = Convert.ToInt32(Page.Request.QueryString["ID"]);
                    if (itemID > 0)
                        GetDocumentSetItem(ID , site);
      protected void GetDocumentSetItem(int itemid, SPSite sSiteUrl)
                SPSite site = sSiteUrl;
                SPWeb web = site.OpenWeb();
                SPList list = web.Lists.TryGetList("DocumentlibraryName"); //where documentset content type attached
                SPListItemCollection items = list.GetItems();
                SPListItem item = null;
                if (itemid > 0)
                    item = list.Items.GetItemById(itemID);//getting the current item
       //read the document set item column values and assign it other webpart controls , 
                    txtDocsetidname.Text = Convert.ToString(item["FileLeafRef"]);
                    txtDocsetid.Text = Convert.ToString(item["hiddenfield"]);
    In the welcome page I have placed button to load webpart ,while loading the webpart I am reading the query string assigning the values to otherwebparts.
    G1

  • Delete query names from roles and favorites

    I deleted some of the queries in production using RSZDELETE but didn't delete those objects from roles and favorites. As the delete option is disabled in query dsigner and bex analyzer, I m looking for other ways to delete the query names from roles and favorites folders

    PFCG is surely one of the ways to delete queries assigned to a role. But i doubt you might have access to tat tcode in production.
    If you are looking towards deleting the queries from roles and favorites using Bex analyzer, you need specific authorizations. If you have those authorizations you can surely delete the queries from roles and favorites using Bex analyzer.
    Hope this helps.
    Regards
    Gaurav

  • FMS for copying item group name to marketing document.

    Hi All
    I need a query to copy item group name when a user enters a item code in any marketing document.
    Thanks
    Bongani

    HI
    Try this, FMS(Formatted Search) Query.
    Create 1 UDF in Row Level on Marketing Documents.
    ->> Goto Tools(Top menu).
    ->> User-Defined Fields. -> Manage User Fields.
    ->> Open the Manage User Fields.
    ->> Clcik the Marketing Documents.
    ->> Select the Rows Line.
    ->> Click the Add button in buttom of right.
    ->> Add the UDF(Item Group Name).
    Assign the below FMS in UDF.
    ->> Administrator.
    ->> Reports. -> Query Generator.
    ->> Open the Query Generator and put the below Query and Execute the query then Save as the Query Manager.
    ->> Open the Document and put the BP code in header.
    ->> Select the Item Code in row level and Goto UDF then Click Shift + Alt + F2.
    ->> Select Search by Saved Query and Assign the FMS Query.
    ->> put the Tick mark the Autofresh and Select When Exiting Alert Columns(right side).
    ->> Select Autofresh - Item Code.
    SELECT T1.ItmsGrpNam FROM OITM T0  INNER JOIN OITB T1 ON T0.ItmsGrpCod = T1.ItmsGrpCod WHERE T0.ItemCode =$[$38.1.0]
    Regards,
    Madhan.

  • Assigning a document (in DMS) to a MM Contract

    Hi,
    Does anyone know whether it is possible to assign a document from within DMS to a MM contract? I know it is possible at item level through Item > More Functions > Documents, but cannot find similar functionality at the contract header level.
    Kind Regards,
    Mark

    Hi Mark,
    In MM you can link to material Master , Purchase order item level only. If you want to link to header level it's also possible through
    Z-development. In standard functionality you can't do it.
    I hope this will resolve your query.

  • Table to see pricing procedures assigned to document types

    Hi Folks,
    Greetings for the day,
    How can i see the pricing procedures that are assigned to document types.
    1. Is there a specific table name?
    2. Is there a tcode where we assign pricing procedures to document types.
    For example if there is pricing procedure "abc0000", how can i know what are the different document types that are assignes to this pricing procedure.
    I would like to know the table name or transaction code.
    Thank you in advance.
    Best wishes,
    Sarath

    First of all, you should know where we assign the pricing procedure.  If you come to know this, you would not have opened this thread.  As already suggested, you can see all pricing procedures assigned to the available combination in table T683V. 
    In one way, you can check this.  Execute VBAK table, input all document types with some validity period where you can see the related pricing procedure.  But here, if you have not created any document with a document type, then this table won't show.  So you have to be sure on this.
    G. Lakshmipathi

  • Dynamic change in the query name based on user input

    Hi Gurus,
    In a scenario, country appears as a user input variable.When the user specifies his country, the same query displays <b>Business trends</b>' data pertaining to his own country and rest of the world(international) in two tables.The reports are developed using Web application designer.
    Can the name(description) of the query be changed  so that the user input value for country gets dynamically reflected in the query name like <b>Business trends:Selected country vs International</b>?
    Regards,
    Balaji

    Hi Bala,
      ya this can be done by text variables. create a text variable( replacement path on the country infoobject) by going to the query properties on the description.
    if the user enters country value then it will be displaed on the description of the query .
    assign points if useful .
    regards
    santosh

  • No authorization for the component (query name)!

    Hello all,
    when i am publishing the query in web, the following error message is displayed!
    "No authorization for the component (query name)!"
    i had installed and configured everything here, so the person responsible for authorization is none other than me. what i shud do now? shud i add any other authorization profile to the username created? or still any configuartion is required?
    please let me know!
    Thanks,
    Ravi

    Hi ARK,
    thanks for the info.
    i had assigned SAP_ALL and SAP_NEW profiles to the user.
    let me say clearly that when i am executing the Query in the designer it is working fine,no issues in Bex browser too. but when i want to publish safely exexuted query in web (clicking the button publish the query in web) i am getting the above mentioned error!
    do suggest me what is the authorization profile that is needed to serve my purpose?
    hope this time i am clear!
    Ravi

  • Assignment of documents to hierarchy nodes???

    Hi,
    We are using a NW2004s BI system.  After executing a query (BEx Launcher) and when the "Comments" button is selected, we receive the following error:
    ===========================================================
    Assignment of documents to hierarchy nodes is not supported in current KM repository for BU documents (/bw_document/InfoProviderData).
    Document will be created without assignment for characteristic OPROFIT_CTR.  Migrate documents to a CM repository
    ===========================================================
    Any hints/directions would help me a lot as we are nearing go-live.
    Thanks in advance.
    Best Regards,
    Praveen

    The problem is that the KF is not assigned to the hierarchy. We ran in exactly same problem. We solved it by assigning the hierarchy to the KF of which you want to create the document even though you are not showing the hierarchy.
    By the way, it seems that we are both using documents .. do you know how to change the assignment template of the document. WHere to customise the document settings ?!
    Mikkel Søndergaard

  • Get query name by program name

    Hi experts,
    Someone built a query A, and generated it to program B.
    Now I need update query A, but I only know program B. How to get the query name by program name?
    Many thanks.

    Check the page 14 in [this document>>|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/40bec8da-4cd8-2910-27a9-81f5ce10676c?quicklink=index&overridelayout=true]

  • Query name from Tcode

    Hi
    Is there any way to find the Query Name from the Tcode. The Tcode was assigned to the program which was generated form the query.
    Regards

    Hi,
    Have you check SE93. you can find the following object
    Report type-(D_SREPOVARI-REPORTTYPE)
    User group-who created the query(D_SREPOVARI-REPORT)
    Query name-(D_SREPOVARI-EXTDREPORT)
    Its depend how you are assigning T code for queries. If you have created T code thru SE93 and with Transaction with parameters (parameter transaction) seting , then you can see the above details.
    Kind Regards,
    Dinabandhu.

  • What is the table for query name

    Hi All,
    I need an urgent requirement for removing duplicate technical query names from the production. Since there are few issues with the SAP given program I am customizing the SAP Program. Can any one tell me what is the table where the QUERY NAME and it's technical name can be found?
    Thanks,
    Alex.

    hi Alex,
    try RSRREPDIR, RSZCOMPDIR.
    there is one oss note all the tables.
    Table containing Work Book and query relation
    Query Detailes
    oss 792779
    Symptom
    Report ANALYZE_RSZ_TABLES is designed as a check-tool for detecting and solving different types of inconsistencies in the main query definition database tables.
    The program is recommended for BW system administrators.
    Other terms
    Query definition, query, reusable, component, variable, missing elements, missing records, missing UID, INCONSISTENCY, RSZELTDIR, RSZCOMPDIR, RSZCOMPIC, RSZGLOBV, RSZCALC, RSZSELECT, RSRREPDIR.
    Reason and Prerequisites
    ATTENTION: the described version of the program is delivered with the following Support Packages:
    SP27 for release BW 3.0B
    SP21 for release BW 3.1C
    SP13 for release BW 3.5
    All versions of this report available in systems before those Support Packages are test versions which can be used only for information purposes.
    Check prerequisites
    Checks are possible only for elements in object version 'A' (active) and 'D' (delivered).
    Checks for query elements in 'D' version are possible only in the systems which are set as content.
    Checks description
    Report performs checks in the tables containing the parts of the definitions of queries and query components: RSRREPDIR, RSZCOMPDIR, RSZCOMPIC, RSZGLOBV, RSZELTDIR and RSZELTXREF.
    1. Table RSRREPDIR
    The table RSRREPDIR is a header table of the generated reports. Consistency of query definition in this table allows to select a query in the Open Dialogs of fronted application and to call report generated for this particular query using transaction RSRT.
    The following errors can be found:
    - queries with missing definition;
    - queries with missing GENUNIID;
    - queries with technical names different than in RSZCOMPDIR;
    - non-queries in the table.
    1.1 Queries with missing definition
    The queries are available only in the table RSRREPDIR and not found in the table RSZELTDIR in the corresponding object version. Such queries (in active version) can be accessed only from RSRT transaction. An attempt to execute such query will return the short dump 'Exception condition INCONSISTENCY'. The error also happens during query generation in RSRT or during mass regeneration of the queries using RSR_GEN_DIRECT_ALL_QUERIES report or application menu of transaction RSRT. The inconsistent queries can not be repaired because of missing query definitions. The recommended solution is to delete those records in order to avoid the possible system dumps.
    1.2 Queries with missing GENUNIID
    Queries having empty GENUNIID field in the table RSRREPDIR. Such queries may be available in the frontend and in RSRT transaction. An attempt to execute such query will return the message'GENUNIID not found'. Situation requires additional investigation at SAP. Create an OSS message for BW-BEX-ET-QDEF.
    1.3 Queries with technical names different than in RSZCOMPDIR
    The check outputs the queries which have different technical names in the RSRREPDIR and RSZCOMPDIR tables. Execution of a query using the technical name given in Query Designer and stored in the table RSZCOMPDIR will return the error message 'GENUNIID not found'. The system tries to find the corresponding GENUNIID for the wrong COMPID which does not exist in the system or which belong to another query. The recommended solution is to correct the wrong COMPID in the table RSRREPDIR via corresponding procedure.
    1.4 Non-queries in the table
    The table RSRREPDIR normally contains only reports. Query elements of other types should not exist in this table and can be deleted. In case, when such records exist in the table an attempt to access them in RSRT returns the error message 'GENUNIID not found'. The recommended solution is to delete those records from the table using the corresponding procedure.
    2. Table RSZCOMPIC
    The table RSZCOMPIC contains an InfoProvider assignment for queries and other reusable query components (STR, RKF and CKF).
    The following errors can be found:
    - local elements in RSZCOMPIC;
    - components with inconsistent definition;
    - components based on non-existing InfoProviders;
    - components based on non-active InfoProviders.
    2.1 Local elements in RZSCOMPIC
    The table RSZCOMPIC contains an InfoProvider assignment for the reusable components. The local elements and also variables have no InfoProvider assignment and should not exist in this table. Those elements can be deleted via corresponding procedure.
    2.2 Components with inconsistent definition
    The reusable queries or query components existing in the table RSZCOMPIC, but not found in the table RSZELTDIR. Those reusable components may return 'Exception condition INCONSISTENCY' dump during accessing/execution. The situation may have different outcomes and has to be investigated at SAP. Create an OSS message for BW-BEX-ET-QDEF.
    2.3 Components based on non-existing InfoProviders
    Queries or query components are assigned to the InfoProviders which do not exist anymore in the system. Queries without InfoProvider are not available in Open Dialogs of frontend applications, but can be executed in RSRT. The execution will return the error message'InfoProvider not found'. The recommended solution is to delete the unnecessary components. Deletion of these queries or query components can be done directly from the list using corresponding procedure similar to RSZDELETE transaction.
    2.4 Components based on non-active InfoProviders
    Queries or query components which are assigned to the InfoProviders which do not exist in the system in the active version. Queries without active InfoProvider are not available in Open Dialogs of frontend applications. In case, an affected query is technically consistent, an attempt to execute it in transaction RSRT will return the message 'Activate the XXX InfoCube / InfoProvider again. Message #BRAIN 056'. Quite often this error is combined with other errors like missing GENUNIID in the RSRREPDIR or other inconsistencies. Each case has to be investigated in order to get the current status of this object. If the affected query is useless, it can be deleted from the system using transaction RSZDELETE.
    The check is available only for the query elements in object version 'A' (active).
    3. Table RSZCOMPDIR
    The table RSZCOMPDIR is the directory table containing the main properties of all reusable components.
    The following errors can be found:
    - duplicated technical names (COMPID);
    - components with inconsistent definition;
    - components without InfoProvider assignment;
    - components with missing OWNER.
    3.1 Duplicated technical names (COMPID)
    The check outputs queries or other reusable query components which have duplicated technical names (COMPID).
    The error does not cause any dumps in ABAP or terminations in Query Designer, but may cause several symptoms in different reporting areas:
    different queries are available in BEX Analyzer and RSRT under the same name;
    wrong query is used as Data Source for Web Template (Web Reporting, Reporting Agent, Broadcasting, MDX);
    replacement of variables does not work... etc.
    The recommended solution is to provide a new technical name for the duplicated component using corresponding procedure.
    ATTENTION: in case when there are only 2 components with the duplicated technical name, only one of those 2 components can be renamed using the corresponding procedure.
    The alternative solution for renaming the duplicated technical names is to use the ABAP report RENAME_DUPLICATE_ELEMENTS.
    3.2 Components with inconsistent definition
    Reusable query components which are not found in the element directory table RSZELTDIR are displayed. This situation may cause the short dump 'Exception condition INCONSISTENCY' during accessing the affected component in Query Designer or execution the affected query in RSRT. Further investigations are required at SAP. Create an OSS note for the SAP component BW-BEX-ET-QDEF.
    3.3 Components without InfoProvider assignment
    All reusable query component (except variables) should be assigned to a particular InfoProvider. This assignment is located in the table RSZCOMPIC. When the record is not found in this table, the affected component may become not available in Query Designer in the corresponding InfoProvider. In some cases the error message "Component XXX.. (version A) has no InfoCube assignment". Further investigations are required at SAP. Create an OSS note for the SAP component BW-BEX-ET-QDEF.
    3.4 Components with empty ONWER field
    Reusable components which have empty OWNER field in the table RSZCOMPDIR are accessible by users having $USER setting in the authorization object S_RS_COMP1 (users which are authorized to their own queries or query components). This leads to authorization concept violation.
    For error solution the field OWNER in the RSZCOMPDIR should be filled with any value. Execute the corresponding edit mode in order to fill the empty field with user 'SAP'. This will prevent the potential authorization violation for users with $USER setting and will take no effect on the users without this setting.
    4. Table RSZELTXREF
    The table RSZELTXREF contains all links and dependencies between the query elements within a query or query component.
    The following errors can be found:
    - missing elements (INCONSISTENCY dump);
    - not supported relations between query elements;
    - extended RSZELTXREF check.
    4.1 Missing elements
    Missing elements are those query elements which exist as the dependant objects (field TELTUID) in the table RSZELTXREF, but not available in the element directory table RSZELTDIR in corresponding object version. In case, when such elements are used in any query or other query components (STR, CKF or RKF), this may lead to ABAP short dump with 'Exception condition INCONSISTENCY' error message in query run-time or design-time. Other known symptoms of this error is, that structures, calculated key figures or restricted key figures are not available in an Info Provider in Query Designer during design-time.
    The missing elements which are in use in other queries or query components, can not be automatically repaired or deleted without components where those elements are used. In most cases the manual repair operations directly in the DB tables are required. Create an OSS message for SAP component BW-BEX-ET-QDEF for further investigations and creation of a repair plan.
    The missing elements which are not in use in any query or query components, can be deleted from the system via corresponding delete procedure. This deletion will not affect any existing query or query component.
    ATTENTION: if missing element is variable, it can be repaired in some cases automatically using the corresponding repair procedure. See table RSZGLOBV check 5.1. 'Variables with inconsistent definition' for details.
    4.2 Not supported relations between query elements
    Some relations between query elements which are not supported and can cause dumps in ABAP or terminations in Query Designer (for example link STR <--> VAR). Such cases have to be additionally investigated at SAP. Create an OSS message for SAP component BW-BEX-ET-QDEF.
    4.3 Extended RSZELTXREF check
    The extended RSZELTXREF check outputs 2 situations which, in combination with other conditions in the system, may be responsible for slow performance of all operations which involve select from the table RSZELTXREF and resolving the relations between query elements (query load, query generation, expanding of a variable list for corresponding InfoObject, expanding of a list of reusable components in Query Designer,... etc.):
    - records with empty INFOCUBE field
    - records which are not used in any query or query component
    Records with empty INFOCUBE field
    The current algorithm of resolving of relations between the query elements uses an optimization which allows to reduce the amount of data selected from the table RSZELTXREF during such operations are query load, query generate, expand a list of reusable components (STR, CKF, RKF) and so on. All relations between query elements within one reusable component based on one InfoProvider 'N' are also located within the same InfoProvider. The system has to select only records where the INFOCUBE field contain the same InfoProvider 'N' and in addition to this all other records where the INFOCUBE field is empty. This is necessary, because in all BW releases below 3.x the INFOCUBE field was not in the RSZELTXREF table and all components created before 3.x release have this field empty. Selection of records with empty INFOCUBE is required in order to ensure the consistency of processed query.
    When the number of records with empty INFOCUBE is quite large (50.000 - 1 mln records), any simple operation which require resolving of the relations may take a long time, because those records are always being selected, loaded to Query Designer and processed in the design-time.
    Records which are not used in any query or query component
    The program makes a virtual attempt to reconstruct the table RSZELTXREF via resolving the relations between all reusable components existing in the system. All records which are not used in any query or query components are considered as non-used records. Usually these are fragments of old queries or other components which are not deleted due to former errors in the query delete algorithm.
    The current version of the program contain only information about those 2 issues. See the OSS note 823804 for additional information.
    ATTENTION: the extended RSZELTXREF check is recommended when all critical problems with reusable components are resolved and the system clean-up is done (no useless records in the tables, no useless non-executable queries or other affected query component available).
    Starting from SP28 for BW 30B, SP22 for BW 31C and SP14 for BW 3.5 the Extended RSZELTXREF check detects and fixes the following situations:
    records used in existing queries or query components with empty INFOCUBE field;
    records used in existing queries or query components with wrong INFOCUBE assignment;
    records with or without INFOCUBE assignment which are not used in any query or query component.
    For further check details read the OSS note 859086.
    5. Table RSZGLOBV
    The table RSZGLOBV contains the definitions and technical properties of the variables.
    The following errors can be found:
    - variables with inconsistent definition;
    - variables with missing or incorrect properties;
    5.1 Variables with inconsistent definition. Variable not found in RSZELTDIR/RSZCOMPDIR tables.
    The variable existing in the table RSZGLOBV, but not existing in the tables RSZELTDIR or RSZCOMPDIR have inconsistent definition. These situation may return 2 different error messages. When a variable is missing in RSZELTDIR table (or in both together), an attempt to expand a list of variable under a corresponding InfoProvider or a list of text/formula variables will return a message 'Inconsistency in loading...'. All variables which are created for corresponding InfoProvider, text/formula variable are not available. When a variable is missing in the RSZCOMPDIR table only the error message is 'Missing UID XXXXXX... in RSZCOMPDIR! You may continue to work, but this component is not loaded' in Query Designer.
    In both cases the variables can be repaired via the corresponding procedure provided in the program under the technical name (COMPID) corresponding to the name in VNAM field in the table RSZGLOBV with the text 'REPAIRED BY SAP'.
    As an alternative solution, when the affected variables which are not used in any query or query component can be deleted directly from the RSZGLOBV table. Both solutions will fix the reported symptoms.
    ATTENTION: it is recommended to open a repaired variable in Variable Wizard of Query Designer and to adjust the definition of this variable, when it is necessary.
    ATTENTION: deletion of the affected variables missing in the table RSZCOMPDIR is not possible using transaction RSZDELETE. An attempt to delete such variable will return the error message 'Component not found'.
    5.2 Variables with missing or incorrect properties
    Several errors can be found within this check. The variables of different type have their own sets of properties. Missing or incorrect properties may cause different error message during execution of a query where such variables are in use. In the case of the affect variables with processing type 'replacement' , the replacement may not work because of the problem.
    Each case has to be investigated at SAP. Create an OSS message for SAP component BW-BEX-ET-QDEF.
    6. Table RSZELTDIR
    The table RSZELTDIR is the main directory table containing all query elements available in the system.
    ATTENTION: the RSZELTDIR check may take a long running time depending upon the table size.
    The following errors can be found:
    - local elements not in use;
    - reusable elements not in RSZCOMPDIR table;
    - reusable elements not in RSZCOMPIC table;
    - structure (STR) without structure members;
    - selections or RKF without definition in RSZSELECT table;
    - formulas or CKF without definition in RSZCALC table;
    - variables (VAR) without definition in RSZGLOBV table;
    - queries (REP) without entries in RSRREPDIR table.
    6.1 Local elements not in use
    Local elements (field REUSABLE = false) which are not used as dependant objects in the table RSZELTXREF. These elements are useless and not accessible from Query Designer. Usually these are fragments of the definitions of old queries accumulated in system because of different problems with save/delete procedures which are not accessible by the end users. The recommended solution is to delete those elements using the corresponding delete procedure.
    6.2 Reusable elements not in RSZCOMPDIR table
    Reusable elements (field REUSABLE = true) must have a corresponding entry in the table RSZCOMPDIR which contains the definition and properties of this reusable component. An attempt to load such component in Query Designer may cause the error message 'Missing UID XXXXXX... in RSZCOMPDIR! You may continue to work, but this component is not loaded'. Additional investigations are requires at SAP. Create an OSS message for BW-BEX-ET-QDEF.
    ATTENTION: Deletion of such affected components is also not possible using transaction RSZDELETE. An attempt to delete will return the message 'Component not found'.
    6.3 Reusable elements not in RSZCOMPIC table
    Reusable elements (field REUSABLE = true), except variables (DEFTP = 'VAR'), must have a corresponding entry in the table RSZCOMPIC which contains an InfoProvider assignment for reusable components. When a reusable component has no InfoProvider assignment it may be not available in Query Designer during design-time. Additional investigations are required at SAP. Create an OSS message for BW-BEX-ET-QDEF. In case the affected component is useless, it can be also deleted from the system using transaction RSZDELETE.
    6.4 Structures (STR) without structure members
    Reusable and non-reusable structures (DEFTP = 'STR') should have dependant elements (structure members). When these structure members are not found a query containing this structure returns the error message 'Element structure not correct' during generation or execution in RSRT or BEx analyzer. The program outputs a query technical name where such structures are used or the technical name of an InfoProvider if the affected structure is reusable and not used in any query. In this case it can be accessed from any query created in the same InfoProvider in Query Designer. The solution is to open the affected structure in using the latest available version of Query Designer and to create the required structure members in order to avoid the error message.
    In case, when the affecter structure is local (non-reusable) and is not used in any query, this structure is not accessible by frontend users and can be deleted from the system by corresponding procedure provided in the program.
    6.5 Local selection of RKFs without records in RSZSELECT table
    Local selections and reusable Restricted Key Figure (DEFTP = 'SEL') usually should have the corresponding records in the DB table RSZSELECT. The program outputs all selections found in the system which have no corresponding records in the RSZSELECT table.
    Usually this issue has no impact on the existing queries and produces no error messages. There are 3 possible types of selections within a query:
    Normal selection - this selection represents a characteristic in Row, Columns or Free Characteristics area, Conditions or Exceptions. This situation produces no error messages, but the selection is not taken into account by OLAP.
    Dummy structure member - structure member type selection can be defined using Query Designer. Such structure member produces no selection and can be used only as place holder within a query. This situation produces no error messages during generation/execution of a query containing a structure with those dummy structure members.
    Cell selection - this type of selection is usually used as Cell selection and can be defined using Cell Editor in Query Designer. This situation produces no error messages, but the selection is not taken into account by OLAP.
    If it is necessary, the selection definition can adjusted using the latest available version of Query Designer. The affected local selections can be accessed from the queries presented in the WHERE-USED (INFOCUBE/QUERY). The Restricted Key Figures are available in Query Designer from any query created on the corresponding InfoProvider.
    In case, when a local selection is not used in any query or query components the recommended solution is to delete this selection using the corresponding delete procedure.
    6.6 Local formulas of CKFs without records in RSZCALC table
    Local formulas (DEFTP = 'FML') or Calculated Key Figures (DEFTP = 'CKF') should contain definition of the calculations in the table RSZCALC. When such definition is not found in the table RSZCALC the queries or query components which include those affected objects can not be generated or executed by OLAP. An attempt to generate such query returns the error message 'The (sub) formula XXX... is not available'.
    The definitions of the affected formulas or Calculated Key Figures can be adjusted using the latest available version of Query Designer. The adjustment of a local formula is possible from the corresponding query listed presented in the program. The Calculated Key Figures are available in Query Designer from any query created on the corresponding InfoProvider.
    In case, when a local formula is not used in any query or query components the recommended solution is to delete this formula using the corresponding delete procedure.
    6.7 Variables without records in RSZGLOBV table
    Variables (DEFTP = 'VAR') should exist in the table RSZGLOBV. The table RSZGLOBV contains all processing properties and definition of the variables. Query where such variables are used can not be executed without problems.
    The repair procedure is not possible, because of missing definition. In case, when such variable is not used in any query, the recommended solution is to delete it from the system in order to avoid potential problems. If the affected variable is already used in other queries or query components, create an OSS message for SAP component BW-BEX-ET-QDEF. Further investigations and possible repair plan have to be created at SAP.
    6.8 Queries without records in RSRREPDIR table
    Queries (DEFTP = 'REP') should exist in the table RSRREPDIR. The table RSRREPDIR is a header table of generated reports and also a part of the database view V_REP_JOIN which provides data for the BEx Open/Save Dialogs.
    A query which does not exist in the table RSRREPDIR is not accessible via RSRT transaction (error message 'GENUNIID not found') and not displayed in the Open/Save Dialogs of fronted applications.
    The recommended solution is to delete such queries using the corresponding procedure provided in the program and similar to RSZDELETE.
    In some cases the repair procedure is also possible. The success of the repair procedure depends upon the consistency of the affected query, the existence of a valid InfoProvider for this query and some other factors. For repair attempt create an OSS message for the SAP component BW-BEX-ET-QDEF.
    hope this helps.

  • How can I related Query name with Query elements?

    Hello gurus!
    I am working with BI7, content technical, well I need to find out a solution where I can related Query name with query elements (KYF, CKY, Restricted Key Figures, var, etc)
    In master data 0tctquery, exist the query element, but, I can not related with object are from what query...
    Do you know how I can do it??? some solution???
    Best Regards

    "it is impossible to relate both tables" ???
    hmmm... these are exactly the tables the Query Designer uses to "build" up the query... so trust me, they do relate
    now to get this information in an InfoCube is a totally different thing... how do you expect to report on this if you should get it in an InfoCube? let's take a simple example... assume you have a query (QUERY_1) which looks like:
                                      Sales  Sales
    Sales Org Customer    Qty      Value
    1000         ABC           10 PC  500 €
    1000         DEF             5 PC  250 €
    in your Cube you would get:
    QueryName  QueryElement
    QUERY_1    0SALESORG
    QUERY_1    0CUSTOMER
    QUERY_1    ZSLSQTY
    QUERY_1    ZSLSVAL
    if you have free characteristics, you'll add more lines... same for variables, CKFs, RKFs, conditions, ...
    I guess it would be better to create a little ABAP report using the above tables (oh, you'll be needing a lot more tables if you wish more detail)

  • Find Query Name in Transport Request or In TR what are Queries.

    Dear All,
    I would like to find a Query Name in Transport Request(DEVK.....)  or  Vice-Versa in Transport Request (DEVK........), what are the queries are included.   I created SAP Query using SQ01 and assigned the InfoSet.  The query is succesfully executing and getting the required result but I dont know the Transport Request Number which was created.  In stead of creating New request, I would like to know the existing Transport Request what are the Queries are assigned.
    Regards,
    Ujed.

    Hi
    If you have included the Query in Transport using SAP Query Transport tool, it creates Transport request and makes an entry in the table AQTDB. Check the table entries in the table AQTDB.
    ~~~Ganesh Kumar K.

  • Query name for T-code S_ALR_87013533

    Hi,
    Could anybody help me to find out the query name of the below T-code.
    S_ALR_87013533
    Thank you.
    Regards,
    Kohima.R

    Hi Kohima.R,
    the description for that transaction code is "Plan/Actual/Commitment/Rem.Plan/Assigned" and it can be found under S000 > Information Systems > General Report Selection > Controlling > Projects > Costs > Plan-Based > Hierarchical or under S000 > Information Systems > Project System > Financials > Costs > Plan-Based > Hierarchical.
    It runs extended report "KP  01RPSCO_X                       12KST1C".
    I hope this helps. Kind regards,
    Alvaro

Maybe you are looking for