Table for stroring description of Calc. & Resrticted key figures

Hi,
Can anyone please tell me in which table the description of characterstics, calculted and restricted key figure's is stored as i have to do the language translation.
Thanks !

Hai,
Go to se11..
and here u give the belove tcodes...
  RSZELTDIR?-Directory of the reporting component elements
  RSZELTTXT?-Texts of reporting component elements
  RSZELTXREF?-Directory of query element references
  RSRREPDIR?-Directory of all reports (Query GENUNIID)
  RSZCOMPDIR?-Directory of reporting components
Thankz & Regards,
Prakasu

Similar Messages

  • Table for role description

    Hello All
    I can't find the right table for role description.
    Can someone tell me the table name showing role description ?
    Thanks &
    Regards
    CB

    I've finally find it, it's AGR_TEXTS

  • Filtering a Query result for a specific value of a key figure

    Hi folks,
    I want to filter a query for a specific value of a key figure. The report should display all customer who has an account balance greater than EUR 500'000.
    Can I only implement this kind of filter via a condition in Query-Designer? If I run that query on an InfoCube with non-cumulative key figures over all our customers (> 400'000) I have problems with the consumption of the memory. If I restrict the amount of the customers to 50'000 - 60'000 then it works. It seems that the query reads all customer records in an internal table before applying the condition.
    Is there another way to deal with? Any help appreciated.
    Kind regards
    Hansjörg Luzi
    Graubündner Kantonalbank
    CH-7002 Chur

    You could try to implement an alternative solution: define a new Characteristc with discrete values (in the following example I suppose to have intervals of 10)
    KF -> CHAR
    115 -> 110 (110 <= KF < 120)
      5 ->   0 (  0 <= KF <  10)
    83 ->  80 ( 80 <= KF <  90)
    Then you can use these dicrete values to filter ...
    I know that it's not so "flexible" (discetization must be predefined), but query response time is quicker and you can use Aggregates ...
    Hope it helps
    GFV

  • Dictionary table for class description in tcode il03

    Hi,
    Please let me know the dictionary table where  class description is getting stored while using the transaction il03 and while i tried i came to know that it is not in  the table swor..
    Regards,
    Nikhil...

    Check IFLOTX
    Nag

  • Need help for report Variable to restrict the key figure value...

    Hai gurus,
    Now i have data in the cube as follows...
    Reuisition     HR INTW date     LM INTW DATE     TEL INTW DATE     HR Count     LM Count     TEL Count
    a1              01.01.2010     02.01.2010             01.04.2010                 1                1                 1
    a2              02.02.2010     03.02.2010             02.02.2010                 1                1               1
    a3              03.03.2010     04.03.2010             03.03.2010                 1                1               1
    when i execute the report it shd ask the prompts with Date interval as in the below...
    HR INTW date
    LM INTW DATE
    TEL INTW DATE
    if i dont give any interval in the variable prompt it should display all the recors as follows
    Reuisition     HR Count     LM Count     TEL Count
    a1               1                  1               1
    a2               1                  1                     1
    a3               1                   1             1
    If i give LM INTW DATE interval as    01.01.2010 to 31.02.2010
    then it should display all the other counts as in the output_1 , but for LM count for a3 it should show 0.
    Reuisition     HR Count     LM Count     TEL Count
    a1               1                  1               1
    a2               1                  1                     1
    a3               1                 0                  1
    that means wherever i restrict the data depending on the variable that only that interval key figure value shd be in the report..
    for this scenario, which variable i need to use... and how i need to restict the KFig value in the report...
    Right now i am getting like this but it is restricting the records,,, where it should not restrict the records...in the report..
    Please guide me for the same...
    If any concerns about the scenario please let me know...
    Regards,
    VJ

    hi chowdary ,
    could you tell me the var. creation in detail and  with which reference object i need to create ...
    whether i need to take LM_DATE / 0DATE while creating variable...
    and i kept this variables it in filter section, based on the LM_DATE Object.
    i have tried both.. y'day when i take 0DATE it giving me some results...
    But at the same time it is restricting the records..
    i think it could be a problem with var.. properties?
    need more inputs pls.
    Regards,
    VJ

  • Table for the descriptions of the custom programs.

    Hello,
    Can anyone please tell me the table name in which I could find the descriptions of the custom programs which we create in SAP?
    Thanks and Regards,
    Amit.

    By mistake asked twice

  • Table for these descriptions   category 1, category 2, 3 ,4

    Hi all,
        in complheader view  category1 category 2 , 3, 4 are there. where the data of these fields will be stored, in which table.  Becuase i need to display in smartform.
    please suggest.
    ram

    They will be in table
    These data are brought from Category Modeler and they are stored in CRMC_ERMS_CAT*  Tables and specifically the Labels are stored in CRMC_ERMS_CAT_CD

  • Description of key figure for multi language support issue.

    Hi Experts,
    Have a good day ahead!!
    Custom key figure description multi for the language support issue
    The key figure is created in English  language and description also in English.
    When I have logged in to English language and checked the report in Bex ,description of key figure is available.
    But when I log in to other language(German, Spanish Portuguese and etc) environment the description in Bex rport of key figure is showing blank
    In rsa1 in both English and other(German, Spanish Portuguese and etc)  environments key figure description is okay and correctly displaying.
    Please post me your inputs on the same.
    Thanks in advance!!
    Regards
    Priya.

    Hi Prasanth,
    This are the key figures XPRECIO: Transactional Price and XPRECLIST: Price list, its maintained in RSA1 tcode at info object level .
    These two KF descriptions are maintained in English, its working fine when I login into SAP Bex analyzer with English language and its not showing the description for the languages (German, Spanish, Portuguese and etc).
    Its need to be displayed in when login into SAP Bex analyzer with language German, Spanish, Portuguese and etc.
    Regards
    Priya

  • Table for description of field name.

    Hi,
    Want to know is there any single table which stores all the Technical field names used in SAP Vs Description of these fields...?
    Like WERKS = PLANT.
    This doubt has come because there is table "TSTC" for" T. codes". Similarly, there may be table for field description as well, is my opinion.
    Thanks & Regards,
    Siva

    Hi
    From the field you need to indentify the domain in se11, then you can goto se16, table name is DD01T
    DOMNAME = domain name
    DDLANGUAGE = language
    you can Identify the text
    For table short texts you can refer table - DD02T
    Thanks !
    E.Avudaiappan

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

  • Global calculated key figures and their descriptions

    Hi, I currently have a strange problem concerning calculated key figures.
    We have several global calculated key figures which are used in approx. 100 querys. These key figures have a custom description ( not the same as the underlying keyfig info object).
    When we use the calc. key figures in querys we let them take the description from the global key figure (the box 'use Standard text' is checked). When we execute the query, the description of the calculated does not show. As soon as we uncheck the box 'use Standard text' (and thus use 'local' -query level- descriptions) the description does show. Offcourse this is not a solution but merely a workaround, we want the key fig to take its description from the global key figure.
    The problem as described above only occures on one of the two development environments. The environment on which the problem occures has support package skw70018(nwv st 16), the environment on which the problem <u>doesn't</u> occure has support package skw70013.

    Execute the content at Infoprovider level as below
    Div Team A B C
    A X 2 1 6 9
    A Y 4 2 9 15
    Result Row 6 3 15
    If you get same desired result in Infoprovider .. it should come in Report ... Run the report in RSRT (Without cache)
    How you built the MP based on single cube or 2 ? Display content in MP for above critieria ... to cross check the report
    check the idenfication ... is marked to which cube ?

  • System table for Additional Data - Basic data text (MM03)

    Hi
    How can I get the system table for stroring data in MM03 in "Additional Data" the "basic data text" ?
    Thanks in advance.

    Hi,
    CALL FUNCTION 'READ_TEXT'
             EXPORTING
                CLIENT                  = SY-MANDT
                ID                      = 'Z610'
                LANGUAGE                = SY-LANGU
                NAME                    = V_TDNAME
                OBJECT                  = 'VBBK'
                ARCHIVE_HANDLE          = 0
             IMPORTING
                HEADER                  = I_TEXT_HEAD
             TABLES
                LINES                   = I_TEXT_LINE
             EXCEPTIONS
                ID                      = 1
                LANGUAGE                = 2
                NAME                    = 3
                NOT_FOUND               = 4
                OBJECT                  = 5
                REFERENCE_CHECK         = 6
                WRONG_ACCESS_TO_ARCHIVE = 7
                OTHERS                  = 8.
    Regards,
    Bharani

  • Problem with Overwrite for Key Figures in ODS

    A bit of a long explanation, but the problem is not so complicated...
    We have an ODS containing contract line items.  Each line item has a key figure "Total Contract Target" that is marked with update type "overwrite".  We have modified the extractor that delivers data for this ODS so that the key figure is set to a value from the contract header.  Since we don't want the key figure to be duplicated if there are multiple line items on the contract, the user exit for the extractor modifies only the first line item delivered.
    For example, overall contract target value = 100.  Contract has 3 line items.  Contract target value for line item 1 is 100.  Target value for line item 2 and 3 is 0.
    This all works fine for initial loads, but there is a problem with the business content extractor for deltas.  Whenever a single change is made, it delivers three sets of  records.  Continuing the example, we would receive 9 records for the contract (3 sets of 3 line items).  Each of the three sets contains the same records.  Only the first set has the correct contract target value.  Since the ODS key figure is set to overwrite, our method of setting the total contract value in the first record doesn't work, because the extractor delivers duplicates so the duplicates overwrite the total with a 0.
    Would setting the key figure for total contract value to update type "additive" solve this? (I'm concerned that additions would be made if there were only a change to characteristics and not the key figure).  Thanks for your assistance.

    Since we ought to post solutions to problems we discover for people who search this forum...
    Solved this by modifying the customer exit for the extractor to set the key figure for the first contract line item encountered AND for all subsequent records with the same contract number / contract line item.  Since the key figure in the ODS is set to overwrite, this makes sure that the last record written doesn't overwrite the key figure with 0.

  • Query Designer: diferent selection for same key figure

    Hi,
    I have some queries that compare many key figures (Total sales, margins,...) between different periods for the same plant or between different plant for the same period or between different periods and plants. For do that I have 2 key figures for each concept (Total sales 1, Total sales 2, Margin 1, Margin 2,....) And two selection variable for each characteristic (plant 1, plant 2, period 1, period 2).
    So I put a selection for "1 characteristics" for each "1 key figures" and a selection for "2 characteristics"  for each "2 key figures". Simple but laborious.
    My customer, than want to maintain queries himself, ask me for a more "smart" way to do that. Can anybody help me?

    Hi,
    What i can suggest you is to make three new columns and respectively name then small team medium tam and big team.
    For first column wirte a condiiton like (SPOC < 10 ) * 1
    Second column condition (SPOC >10 AND SPOC < 30 )*1
    Third column condition (SPOC >30 )*1
    Make use of boolean operators to make these conditions.
    SO whenever your conditions satisfies it will give 1 there in there respective columns and for rest it will be blank.
    If your requirement is different then please sample output of your report.
    Hope it helps.
    Regards,
    AL

  • Archive/Truncate stage table for interface

    Hi All,
    We use quite a few of staging tables for the interface. We need to figure out a way to archive it and then truncate it from time to time. Of course it will be dependent on the volume and frequency of the data into the staging table.
    Could anyone share thoughts, process to get this executed please.
    Thanks for your time!

    A lot of interfaces (such as Items, categories) have a parameter that tells Oracle to delete the data if the record was imported successfully. You should make use of that parameter.
    If the interface does not have such a parameter, then you should write custom scripts that fire after the interface and deletes successful data.
    For errors however, the picture could get complicated.
    A lot depends on how your interface was designed, what kind of error reporting is in place , how you trigger correction and reprocessing of the errors.
    The safest way is to let the source system resend the data but that is not always possible.
    The second alternate is to use Oracle screens (such as Sales Order Corrections) or develop custom ones to let users fix what was wrong and resubmit.
    If all fails, you should let users delete the errored record.
    If you have any regulatory or audit constraints, then you may want to backup successful as well as error records into another table. But that should not be the first choice. A lot of times, the knee-jerk requirement from users is that the data must be stored even if nobody will ever look at it. At that point, it not data - it is junk in your database.
    Hope this helps
    Sandeep Gandhi
    Omkar Technologies Inc.
    Independent Techno-functional Consultant

Maybe you are looking for

  • Why does Windows think my Treo 700p is a Treo 680?

    I have gone through a long , frustrating fruitless attempt to get my Palm Treo 700p to connect to my new Windows Vista computer.  here are the steps I have gone through... Palm not connected to computer yet 1. run "PalmDesktopWIN62" 2. select english

  • Wrong index being chosen-start routine slow

    Hi, We are uploading 6Million odd records using lookup and aggregation in the start routine of update rules from an ODS into an infocube. One such lookup is on the source ODS itself and takes the longest. The WHERE clause of the SELECT exactly matche

  • Events created in iphone don't sync

    Events created in my iphone4 calendar do not sync with ipad or ical on my MacBook Air. However, events created in both ipad and ical show up on iphone. I have double checked - my prefered calendar is HOME for all devices. Thank you.

  • Accept recursive queeries from these networks only?

    What is the correct terminology to identify your network in dns section accept recursive queeries from these networks only? if i put in my domain name it seems to stop all service to my NAT

  • Generating RSS Feeds using files with extension .xml

    Bonjour! Apologies if this is not the correct forum - please redirect me if necessary. I am trying to create an .xml file to upload to my server allowing me to generate rss feeds on my web site. If i understand correctly (I am a beginner webmaster) f