SLD definition - a query??

Hi
Normally creating Master SLD in Dev and syncing it to the QA , Prod landscapes looks more common approach towards SLD definition and transport mgmt.One suggestion that has come to my notice is to restrict Dev SLD to Systems used in Dev and QA, while in QA we define a separate SLD with Test and Production instances, and we define Transport paths linking Dev to QA  and QA to Prod.Will this be a good approach to maintaining transports..Are there cons from this approach!! Let me know on your views from your experience.

Hi Sriram,
I would adviced that you use one SLD for all your Dev, QA and test servers and one seperate SLD for production server.
a blog on the same lines
/people/sap.india5/blog/2005/11/09/xi-software-logistics-ii-overview
Best regards,
Naresh

Similar Messages

  • Cell Definition in Query Designer

    Hi,,
    Can anyone will tell me the real time use of cell definition option in query designer.
    Thanks and Regards.
    Anjali

    Anjali,
    You can use cell definitions when you want to overwrite the value of a particular cell.
    For this you need to have an identification of where the cell intersection takes place. So for defining cell definitions its mandatory to have two structures in the report.
    Now coming to the scenario,
    You have GL accounts in the rows structure and the key figures amount, deductions and some others.
    Rows-----Amount--
    Deductions
    1001--20000--
    100
    1002--15456--
    4363
    1007--64334--
    252
    1005--36643--
    34
    1111--43436--
    343
    This is what the report displays for a particular year the user enters e.g 2007.
    But for a GL account 1005 the user wants to display the amount for the last fours years.
    The out put for amount for the GL account 1005 displays only 2007. The requirement is that it should display the summed up values of 2007,2006,2005,2004.
    To get this out put we go for cell definitions and in the intersection of the 1005 GL account and amount we define a cell definition. Based upon the requirement we define the cell definition...
    Hope this helps you.......

  • Cell definition in Query Design within Bex Analyzer

    Hello,
    I would like to use special cell definition to visualizing the difference row definition between 2 columns (last year and actual year). With "Cell Definition" function in Query Design within Bex Analyzer there's a option to select a new restricted key figure for a related cell. But as a result I just can see a star (*) against a result number in that field. Do you have an idea, how can I solve this problem?
    Thanks and Regards,
    Nuran

    Hi again Dirk,
    there's not a unit problem. We use 2 different restricted key figure definition for a same row. The first restricted (or can be decribed as calculated key figure) key figure must be used in the first column to represent the value of the last year. And at the same row with usage of same text (for example: cost of goods sold)the second restricted key figure should be used to show the value of actual year (B2:costs in euro). The problem is the key figure definitions are totaly different; they're using different account groups etc. Cause of, I wanted to use cell definition function. In the first value field (B1) should be shown first key figure but I just get star (*) and a wrong value in the formula field of excel (between the toolbars and the result area).
    Thanks for your reply.
    Nuran

  • Cell definitions with Query formulas

    I have a query with cell definitions used.
    My problem is when I use a formula in one of the original query columns, it ignores the cell definitions and considers the orignal columns definitons.
    My understanding is that cell definitions overwrite the original query column defintion by default.
    The only way I can think of it, is that I should do all my formulas in the cell definitoins editr for all affected cells (one by one).
    Anyone had a similar problem.
    your help is appreciated.
    Thanx in advance

    I'm not sure if i understood correctly, you have the a formula defined in query columns let's suppose ab, and for the same formula intersection in the cell defnition you have another formula bc.
    But the query is returnign the result of a*b ? Am i correct in understanding ? If this is right, then why do you have calculations in both the places....

  • SLD Business Service Query

    Hi,
    i would like to query the system landscape directory to get some attributes from the business service. Any ideas?

    Finally i found the solution in the function group LCRACCESS
    How can i assign 10 points to me?

  • Problem faced in condition definition in Query output

    Hi Gurus,
    I have a scenario where i have flat file input with Regcode, Weekno, Vehicleno as characteristics. Mileage, idletime as Keyfigures. I have created a report where i need to display the regcode as rows and mileage, idletime as columns.
    But the condition is that value of mileage should be between 0 and 7999 of the  each vehicles for the seperate weeks. I have specified this under condition by selecting the characteristics vehicle no and weekno.and  mileage between 0 to 7999.
    But the problem i am facing is the report gives the summed values of all the vehicles which does not fall between 0 and 7999.
    How to go about ...Guide me...
    Very Urgent...
    Thanks in Advance..
    Regards
    Mano

    Mano,
    Are you saying that it is displaying correct rows but the total is for all values?  If so, select your key figure and look into the Properties section. Change the 'Calculate Results As' to summation.
    Regards
    Gill

  • BEx Query Cell Definition (If ..then...else with AND)

    Hello Experts,
    I am struggling with a requirement which I need to define in the Cell definitions in Query designer. I have tried going through the numerous posts regarding this if..then...else in SCN but were of no help to me.
    My requirement is as follows:
    if expression1 then result1, else if (expression2 AND expression3) then result2, else (expression4 AND expression5) then result3
    I tried to define this in the cell as below:
    <expression1> * result1 + (<expression2> AND <expression3> ) * result2 + (<expression4> AND <expression5>) * result3
    but somehow it does not work.
    Any pointers of how to achieve this?
    Thanks.

    Hi,
    If you are getting 'X' then this may be related with the dimensions you use in comparing variables. Try the whole formula such as
    (nodim(var_1) > nodim(var_2) * nodim(kyf_1)
    "then try seperating the if else statements into different cells" : for example try adding a formula for
    each item in your formula (one for buchungsperiode, one for buchungsperiode ein gabe etc. I mean you can find the formula vaiable or key figure that causes 'X' in the results by seperating the formula into the items of the formula.
    Regards
    Yasemin...

  • What is "key date" in the query definition

    Hello,
    What is "key date" in the definition of query. Where does it come in picture and I see that it has value varaible?
    Can someone explain?
    Thanks

    Hi K M,
    This date is relevant for the time dependant master data if you are using it in your query.
    http://help.sap.com/saphelp_nw04/helpdata/en/1e/99ea3bd7896f58e10000000a11402f/content.htm
    You can use a variable in the key date and then the master data suuplied to the query (like nav attr) will be as per the date you have specified.
    Hope this helps...

  • Error in query execution after upgrade

    Hi Gurus,
    013 An exception with the type CX_SY_CREATE_OBJECT_ERROR occurred, but was
    neither handled locally, nor declared in a RAISING
           Message no. RS_EXCEPTION000
        013 The object could not be created: The class \CLASS=CL_IM_RS_BCT_PA
    does not exist
           Message no. RS_EXCEPTION000
        013 The definition of query Y_XP_SALES_QUERY2 (InfoCube Y_XP_SAL) was
    savX
        013 Query Y_XP_SALES_QUERY2 (InfoCube Y_XP_SAL) was saved.
        013 The query was successfully generated.
    any suggestions are appreciated
    Thanks
    Praveen

    We upgrade the system from BW 3.1 to 3.5 NW
    I run t-code rsrt1
    I select 0FIA_DS11/ZASSETST1 query and I try to execute, It is working fine
    I select 0FIA_DS11/ZASSETST1 query and I try to Generate report, I am getting following error
    An exception with the type CX_SY_CREATE_OBJECT_ERROR occurred, but was neither handled locally, nor declared in a RAISING
    Message no. RS_EXCEPTION000
    The object could not be created: The class \CLASS=CL_IM_RS_BCT_PA does not exist.
    Message no. RS_EXCEPTION000

  • Substr in external table definition

    Hi Guys,
    I have an external table where I am loading a txt file. The issue being, in the txt file I have a column with a variable length. This column houses the application/website link that is not of a fixed length. My external table field width is 100, but the txt file value is more than that. Now, I want to only insert this field for the 100 characters.
    I tried using substr as shown in the example below, but it fails. Any idea what could be the alternative or if I am doing it right?
    Here's my external table properties (access parameters) and I am trying to use 'substr' on field4
    records delimited BY NEWLINE
    badfile BAD_DIR:'email_events%a_%p.bad'
    LOGFILE LOG_DIR:'email_events%a_%p.log'
    fields terminated by '\t'
    missing field values are null
    event_type,
    cm_timestamp,
    issue_id,
    cm_uid,
    field1,
    field2,
    field3,
    field4 "substr(:field4,1,100)",
    field5,
    field6,
    field7,
    field8,
    field9,
    field10,
    field11,
    field12,
    field13,
    field14
    )

    Just set your external table definition to query the full thing and then when you come to insert that data to a real table from the external table you can apply the substr in that query.

  • Query Designer writeing formula takes very long time

    Experts,
    When i try to write a formula. The query designer is taking very long time to navigate.
    One formula is taking 20 mins to write.
    1. I have upgraded my laptop memory to 2 GB of Ram
    2. I am on 7.10 SP4 Patch 1. Had the same issue with the previous versions.
    Please suggest a resolution.
    The QD has tested my patence. I am sure no body wants to create a query for 2 days. There has to be a problem somewhere causing this.
    Thank you.

    Vinod,
    Save the query and then exit BW sessions, also restart your system.
    It might be a problem with main memory of your laptop or BW server load.
    But 20mins is too long for any kind of definition in query designer.
    Please check these things, perhaps it helps.
    Thanks,

  • Query taking longtime to run

    Hi Gurus,
    We have created a query on a InfoCube and when I run it in query designer its taking long time to get the results and final report.
    How can I optimize the performance ? Please let me know what would be the measures for optimizing query performance.
    Thanks in advance,
    sudhakar.

    Hi,
    Query performance can be tuned once you have an idea of its potential usage pattern.
    Starting from query properties (Read mode - very important setting, and cache settings) to drill down pattern, everything matters.
    On DB level (your data model - Cube/Aggregate/Indices) can impact the query performance. Some help can be had by using turning on DB statistics.
    On OLAP level - your olap level processing (conditions/exceptions/virtualKF/Char/Variable processing/Global cache etc) adds to the performance overhead and you can finetune these to improve query performance.
    On GUI level - Definition of query (too much data will load the network) may impact the performance. In addition (this is from Teched session I attended), Excel has more overhead on GUI level as compared to http, and so at times, using a wb based report may perform better than excel based queries.
    In addition, you can think of pre-calculated web templates to provide faster reports to users (if drill-down is not required). Also, some other techniques (eg if a report is executed many times and is resource intensive, you can schedule this report once after the data refresh and keep its global cache on, so this report is available in the main memory and every subsequent execution will fetch it from OLAP itself and will be much faster).
    In addition to RSRT, ST05 (sql trace), SE30 (runtime analysis) and system statistics (ST03) may help you in identifying performance issues with a report.
    Also check this thread:
    Query BW tahckes too much time to runn
    Regards
    Lavanya

  • Need help understanding how to resolve this XMLP Report Definition error

    Getting error on only 1 database but is of course is the one for an important deal. Going to Reporting Tools>XML Publisher>Report Definition and querying for Report Name HRS_INT_LET we get errors.
    File associated with template definition is not found in the database. (235,77)
    File object associated with template defintiion is not found in the database, therefore the report and/or template definition is not valid.  Please check consistency of objects.
    Next error message:
    Error in PeopleCode ScrollSelect processing. (2,213) PSXPRPTDEFN_WRK.FUNCLIB.FieldFormula  Name:LoadTemplateDefn  PCPC:37323  Statement:542
    Called from:PSXPRPTDEFN_WRK.FUNCLIB.FieldFormula  Name:LoadReportDefn  Statement:601
    Called from:PSXPRPTDEFN_WRK.FUNCLIB.FieldFormula  Name:SelectReportDefn  Statement:740
    Called from:PSXPRPTDEFN.GBL.PostBuild  Statement:36
    A SQL error occurred during processing of the PeopleCode ScrollSelect (or ScrollSelectNew, RowScrollSelect, RowScrollSelectNew) built-in function.
    This error may have been described by a preceding message.
    Examine the error messages and the PeopleCode program containing the ScrollSelect call to determine the cause of the error.
    Edited by: user702257 on Feb 3, 2010 8:24 AM

    Hey did anyone reply or have a similar problem.. ??
    but with 3 Error Messages, the first one is:
    1st Error:
    SQL error.stmt#:651 Error Position:2010 Return:904 - ORA-00904: "CUSTMERNAME":invalid identifier
    2nd Error:
    SELECT T1, T2, ETC........
    3rd Error:
    Error in PeopleCode ScrollSelect processing. (2,213) At INV.TRANS.FieldChange trans_qry PCPC:1719 Statement: 67
    A SQL error ocurred during processing of the PeopleCode ScrollSelect (or ScrollSelectNew, RowScrollSelect, RowScrollSelectNow) built-in function.
    This error may have been described by preceding message.
    Examine the error message and the PeopleCode program containing the ScrollSelect call to determine the cause of the error.
    does any one know or had this error in particular?
    Thanks
    George

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

  • Unable to suppress query information messages

    Hello,
    Often when we run a query in the web we keep getting these 3 info messages:
    "The definition of query <query_name> was saved"
    "Query <query_name> was saved"
    "The query was succesfully generated"
    I would like to suppress these messages.
    I have already disabled all the possible system messages in the Web template this query is in. Where else can I check?

    Hi Roy Cohen,
    Have u suppress all the messages in RSRT?, If u supress it wont come. If u change anything in the content also first time after changing it will show some messages in green status but next time if u run it wont come again.
    Make sure that all the messages are supressed (check mark is there).
    Assign Points if useful.........
    Best Regards,
    SG

Maybe you are looking for