Query CKF & RKF

Hi ...
I have created a master Query, I noticed that I need to have Calculated Key Figure and Restricted Key Figure, from another query .... how can I copy all the CKF and RKF from that query to my query which I have created is there a way ...
TQ
Nathan

Hi Murali ...
What happen's if my Info Provider is Multi Cube ..... can I get tht from another InfoProvider ?
If can .... can show me thes teps .....
TQ
Nathan

Similar Messages

CKF, RKF or Structures locking queries in Development sytem.

Our BW environment is set up to allow "Z" and "Y" queries. When creating a "Z" or "Y" query in the dev environments if a previously transported CKF, RKF or structure is added to the query, it locks after closing. Our QEA and PEA system allows creation of a "Y" query using transported CKF, RKF or structure without the query becoming locked. (The CKF, RKF or structures remained locked). Can anyone tell me how to get the DEA system to behave like the other two systems? Or if there is an OS Note that addresses this issue?
The development system is open and the ELEM type is set to everything changeable.
Thanks for your responses in advance

CKF = Calculated Key figures, RKF = Restricted Key figures. Our "Z" queries are transported queries and "Y" queries are for temporary ad-hoc reports and can be created in the production and quality control systems.
Thanks,
Joe

Transport of changes to quereis and CKFs & RKFs

Hi Gurus,
I have a Multicube and a number of queries that has been transported to HIQ already. I have made a significant changes to these queries in HID, i.e. chges to CKFs, RKFs, including description changes as well as deleting some KFs, and additional KFs.
I have tried to transport to HIQ by collecting these specific queries and all below and putting the multicube in a separate transport with only necessary objects.
I transported the Cube first and then all 25 queries in one transport.
My problem is that in HIQ I have RKFs & CKFs and Queries that I have deleted or renamed in HID. How do I get both enviroments back in sync ?
Thanks for your help.
Laura

Hi,
1) Do I need a separate transport for each query ?
No you can capture multiple queries in one transport
2) Do I include the Multiprovider in one of these transports ? and/or the Cubes in the MultiCube ?
No, there is no need to include multiprovider or cube.
-Mayuri

CKF &RKF'S

hi gud morning gurus
1.wt's differece b/ween calculated & ristricted key figures? wt' the use&where we used these keyfigures?

Hi Arjun,
Calcualted key figure: You can carry out arithmetic, boolean, percent functions on key figures using this.
restricted key figure: You can restrict the values of key figures by restricting it with values of characteristics involved in that query.
RKF's are the (basic)key figs of the infoprovider that are restricted(filtered)by one or more Charcterstic Selections.
links:
http://help.sap.com/saphelp_nw04/helpdata/en/61/d0b143aa26b849b4e79a859ea1d7d1/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/b4/730276938a504cacc56b44fd3578e3/frameset.htm
***pls assign points,if info is useful**
Regards
CSM Reddy
Message was edited by: REDDY CSM

Need help Designing a Query -with RKFs and CKF or alternate

Hi,
Trying to create a query off a HR Headcount IC - to display number of top performing employees (based on appraisal attribute) by region and by function. The format is as follows:
Created 3 RKF's in column structure where
1RKF is KF "Employee Numbers" for characteristics restrictions of date range1, appraisal rating=1,2, employee status =active etc.
2RKF is KF "Employee Numbers" for characteristics restrictions of date range1, appraisal rating=#, employee status =active etc.
3RKF is KF "Employee Numbers" for characteristics restrictions of date range2, appraisal rating=1,2, employee status =active etc.
1CKF is Boolean result of (1RKF OR (2RKF AND 3RKF)
Was able to display correctly all top performing employees in the following format. When "Employee" was selected to row.
Top Performer (CKF)
Employee 1----
1
Employee 2----
1
Employee 3----
1
Employee 4----
1
Employee 5----
1
Employee 6----
1
Employee 7----
1
When tried to display the same by Region by Function or even by only Region (Row Char) it doesnt work. Data is non-sensical.
# of Top performers
Region 1 -
FunctionA----
5
Region 1 -
FunctionB----
2
Region 1 -
FunctionC----
3
Region 2 -
FunctionA----
4
Region 2 -
FunctionB----
0
Region 2 -
FunctionC----
7
Region 2 -
FunctionD----
5
Understand that the Boolean CKF is not working correctly. What am I doing wrong ? Please advice fix or alternates.
Thanks.

Hi Pradeep,
not possible to use ranking since Appraisal rating is a characterstics not a key figure value. Any other suggestions..
Thanks
Arun

SAP BI CKF,RKF descrptions are not reflecting in the universe

Dear Gurus,
I have couple of questions
1.I have created a BI quey with 2 calculated keyfigures and 2 Restricted keyfigures. When i am creating a universe on top of the BI query, Desrptions for Calculated and Restricted keyfigures are not reflecting in the universe, Rather the universe is showing UID(unique ID)'s of the CKF and RKF.
To get the descriptions into the universe, Do i need to do any settings?
2. In one of the documents I have read that we have to create one universe for one language if i want to see the report in Multiple languages. if it is so,
Do i need to create universe in each and every language or is there any option that i can create the universe in one language and replicate into the required languages?
Please help.
Thanks and Regards
Jagadeesh Ambati

Hello Jagadeesh,
I recommend to post this query to the [Integration Kits - SAP|BusinessObjects Integration Kits; forum.
This forum is dedicated to topics related to the BusinessObjects Integration Kit for SAP.
It is monitored by qualified technicians and you will get a faster response there.
Also, all SAP Kit queries remain in one place and thus can be easily searched in one place.
Thanks a lot,
Falk

Report or Function Moule to delete a BEX Report ?

Hi,
is there a program, report or function module to delet a report ?
Thank You
Best Wishes
Martin

Hi martin ,
U can able to delete the query from BEx query designer or from BI.
IN sap Bex query designer, just by opening the query menu -->delete query .
the other way to delete the query is BY using the table RSZDELETE . with that u can able to delete the bex query, CKF, RKF etc..
plz follow the below link for detail
http://dev.diditho.net/2010/07/05/sap-bw-copy-delete-query-and-workbook/
Thanx
Edited by: Ravichandra.bi on Aug 22, 2011 8:14 PM
Edited by: Ravichandra.bi on Aug 22, 2011 8:19 PM

Copy global CKFs and RKFs

Dear all,
has anyone got an idea if/how one can copy a global CKF or global RKF to be used as basis for a new global CKF/RKF? If a RKF has many many restrictions it would make life much easier
Thanks in advance!
Jeanette
Message was edited by: Jeanette Weissmann

Hi Srini,
thanks for your reply. Unfortunately I could not find a responding "paste" option within the global area. I'd be very grateful if you could let me know where to find it.
Greetings,
Jeanette

Using previous results in a query

Hi
Please can someone assist.
I have a bex query - 1 structure only in my columns
I have my data in rows broken down by calendar year.
What I need to be able to do is to use the result in calendar year 2008 and sum it in calendar year 2009.
Calendar month
Calendar Year
Remaiining
Date of Hire
Quota number
Carry Over
Deduction
MAY
2009
21.960
2000/05/15
21.960
0.000
21.960
2010
30.000
2000/05/15
30.000
0.000
30.000
2011
42.260
2000/05/15
42.260
0.000
42.260
2012
39.240
2000/05/15
33.240
6.000
27.240
2013
50.000
2000/05/15
25.000
25.000
0.000
JUL
2008
39.780
2000/05/15
39.780
0.000
39.780
DEC
2007
43.700
2000/05/15
43.700
0.000
43.700
Result
266.940
2000/05/15
235.940
31.000
204.940
My last column needs to be Entitlement which should be the carry over of 2012 + carry over of 2013 = 31 - which should be my entitlement for 2013.
Not sure if that makes any sense.
Please see images attached.
Is there a way to do this with no ABAP, as I am not able to write the customer exit.
Thank you

You may try with Cell definitions concept by introducing a "Calyear structure" in rows and define 2013 cell accordingly. Rest all cells other than in Entitle ment KF take the definitions of their respective CKFs/RKFs. Leave all cells blank other than 2013 in Entitlement KF.
Remove Calyear infoobject which is there currently in rows pane and then create a structure in place of it. Every year, you will need to enhance the Calyear structure and make the cell definitions accordingly as per your business requirement.
Please have a look at my blog to get a brief idea on what I am saying.
How to achieve Slab Wise or Bucket Wise and Age Wise requirements in BEx
Message was edited by: SumaN ChakravarthY K
Message was edited by: SumaN ChakravarthY K

Unable to Transport Querys Object (ELEM) of type 'Query' is not available in version 'A'

Hi,
We need to transport some querys from production BW 7.3.1SP7 to synch with Dev. I know, I know but had no choice but to created querys in PBW due to no data in DEV...
In RSA1, we collect query and get errors for every object (ckf,rkf, vars etc) and when changing dsiplay from hiearchy to list, there are no objects included under the query element.
Opened the system in SCC4 for automatic recording of changes and changes to repository and cross clinet customization allowed and changed the client role to Test.
Tried opening and resaving the query in query designer.
Query is active in table RSRREPDIR
Checked SCN and OSS have yet to find a solution
http://scn.sap.com/thread/1758171
http://scn.sap.com/thread/1623756
Here are the error details
Object '4T3M5JI7050ENPG6G336XWYNK' (ELEM) of type 'Query' is not available in version 'A'
Message no. RSO252
Diagnosis
You wanted to generate an object with the name '4T3M5JI7050ENPG6G336XWYNK' (in transport request ELEM) of type 'Query' (TLOGO). This is, however, not available in the BW Repository database. It does not exist in the requested version A. If the version is 'D' then it is possible that an error arose during the delivery or installation. If the version is 'A' then the Object was either not created or not activated.
System Response
The object was not taken into account in the next stage of processing.
Thank you so much for your time!
Lee Lewis

This is an SAP BUG which is corrected by this note:
> 1762785 - Object '!XYZ...' (ELEM) of type Query is not available.
> 1816332 - Object 'XYZ...' (ELEM) cannot be collected (RSO296)
Lee Lewis

Creating Query in Production with Calculated key figures

Hi BW Experts,
Can u pls let me know that in case of Production System when we are allowing users to create reports with Adhoc Web Query Designer and using CKF + RKF
(Calculated key Figure) which is already transported to Production in a specific Package, Is Production system will allow to save report?
Pls sugges how to solve this problem ..to give permission for users to create reports in production server with CKF RKF?
Thanks in advance

rsa1 -> transport conection -> object changeability button -> Set query elements as everything changeable.
If you want to refine this you have to do by authorizations.

Query Saving takes long time and giving error

Hi Gurus,
I am creating one query that have lot of calculations (CKF & RKF).
When I am trying to save this query it is taking long time and it is giving error like RFC_ERROR_SYSTEM_FAILURE, Query Designer must be restarted, further work not possible.
Please give me the solution for this.
Thanks,
RChowdary

Hi Chowdary,
Check the following note: 316470.
https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=316470
The note details are:
Symptom
There are no authorizations to change roles. Consequently, the system displays no roles when you save workbooks in the BEx Analyzer. In the BEx browser, you cannot move or change workbooks, documents, folders and so on.
Other terms
BW 2.0B, 2.0A, 20A, 20B, frontend, error 172, Business Explorer,
RFC_ERROR_SYSTEM_FAILURE, NOT_AUTHORIZED, S_USER_TCD, RAISE_EXCEPTION,
LPRGN_STRUCTUREU04, SAPLPRGN_STRUCTURE, PRGN_STRU_SAVE_NODES
Reason and Prerequisites
The authorizations below are not assigned to the user.
Solution
Assign authorization for roles
To assign authorizations for a role, execute the following steps:
1. Start Transaction Role maintenance (PFCG)
2. Select a role
3. Choose the "Change" switch
4. Choose tab title "Authorizations"
5. Choose the "Change authorization data" switch
6. Choose "+ Manually" switch
7. Enter "S_USER_AGR" as "Authorization object"
8. Expand "Basis: Administration"/"Authorization: Role check""
9. From "Activity" select "Create or generate" and others like "Display" or "Change"
10. Under "Role Name", enter all roles that are supposed to be shown or changed. Enter "*" for all roles.
11. You can re-enter authorization object "S_USER_AGR" for other activities.
Assign authorization for transactions
If a user is granted the authorization for changing a role, he/she should also be granted the authorization for all transactions contained in the role. Add these transaction codes to authorization object S_USER_TCD.
1. Start the role maintenance transaction (PFCG).
2. Select a role.
3. Click on "Change".
4. Choose the "Authorizations" tab.
5. Click on "Change authorization data".
6. Click on "+ manually".
7. Specify "S_USER_TCD" as "Authorization object".
8. Expand "Basis - Administration"/"Authorizations: Transactions in Roles".
9. Under "Transaction", choose at least "RRMX" (for BW reports), "SAP_BW_TEMPLATE" (for BW Web Templates), "SAP_BW_QUERY" (for BW Queries and/or "SAP_BW_CRYSTAL" (for Crystal reports) or "*". Values with "SAP_BW_..." are not transactions, they are special node types (see transaction code NODE_TYPE_DEFINITION).
Using the SAP System Trace (Transaction ST01), you can identify the transaction that causes NOT_AUTHORIZED.
Prevent user assignment
Having the authorization for changing roles, the user is not only able to change the menu but also to assign users. If you want to prevent the latter, the user must loose the authorization for Transactions User Maintenance (SU01) and Role maintenance (PFCG).
Z1>Note
Refer to Note 197601, which provides information on the different display of BEx Browser, BEx Analyzer and Easy Access menu.
Please refer to Note 373979 about authorizations to save workbooks.
Check in the transaction ST22 for more details on the Query designer failure or query log file.
With Regards,
Ravi Kanth.
Edited by: Ravi kanth on Apr 9, 2009 6:02 PM

The logics for ALL calc key figures (CKF) - Table available?

Hello experts,
I am going through a project here to convert a lot of CKF / RKF in BI Queries.
There are 100's of them and what I want to do is to be able to see all the formula's used in one list as opposed to go through each on in query designer which is , as we all know, a big pain to use.
Is there a table in BI (RSZ something?) which will give me a list of all the CKF's in the system and the arthimatic used to calculate them... most of the CKF's im interested are calculated using RKF and is usually simple logic.
If there is an easy way of seing the formula then this will help me lots.
thanks for any ideas
Iksit
(BI7)

Hello Sudheer
2LIS_02_HDR, ITM and SCL do not take data from S011 but directly from transactionnal tables like EBEP, EBKO, EBPO (names quoted from memory).
So you have to look for the key figures from those tables and not the one in S011.
Historically, the three datasource were built to replace 2LIS_02_S011 but the calculations to rebuild the keyfigures were delivered in BW in an old BCT that made the conversions. The logic and modeling have changed completely.
If you really need to transfer S011 to BW without remodelling the data, you may want to use a generic extractor based on S011 (provided you have a delta key available).
Otherwise, in SBIW, Options for datasource specific to the application, Logistics, purchasing, you have two customizing transactions. you have to define branch and process key to load data into BW. But that will not have any effect to LBWE.
Hope this helps.
Regards
Fabrice

Query Changes: Variable not collected in Transport

Hi Experts,
Intiatlly some one created a query and it was transported to BWQ from BWD.
Due to some changes, I needed to rework on the query. For that I did the following:
a. In the Administrator Transport Workbench, I collected the query
b. CLicked on the Transport checkbox
c. Then assigned a new BEX Transport request.
d. I then made changes in the query plus added a variable in the query.
e. I checked my query and it was working fine in BWD.
Now when I transport this query to BWQ, the transport fails and says
"Error when acitvating element 4DKMNO0UMEXIN0FHM6RYXXJ3F"
"Element 4E5X3H4IQ5BEDSZY1I6GW4P2J" is missing in version M"
I think the transport is missing the variable I created. So why is this not collected?
Secondly since this transport request was released will I have to recollect the query and variable. If so how?
Thanks,
Hundia

I raised an OSS Message.
The reply from SAP was:
"We have analyzed the situation with the inconsistent queries.
1. The error message
'Unable ot detect element type for Element Recreated Formula:
DBJFSQOSAL3WPK8LSCNUWNAJ"' is raise as a result of incorrect repair
procedure most likely perfomed by the program ANALYZE_MISSING_ELEMENTS.
This is very old report which allowes repair, but unfortunately this
repair is not correct. Therefore we do not recommend you to use it
in similar cases.
The element DBJFSQOSAL3WPK8LSCNUWNAJ recreated by the program as a
local formula must have type Calculated Key Figure. This info can be
obtained just by analysis of the corresponding structure members which
has to represent this CKF in the query...
2. Missing element and INCONSISTENCY. This is logically related to
the first case. I have perfomed extended anylysis and the situation is
the following.
Affected query YTEMP_ZSCNNM04_01 (4B75NN07LN3TJVDW9VX8OUACR) contains
one unresolved reference to 4B773WHW1GK5WZAPK5CZHZSH7. This missing
element can be a local structure member (FLM or SEL) or a reusable
object like calculated or restricted KF
Affected query ZORQSP_ZSPNNM021_NN_05 (4DUV3IK29VBJESNEWX20PBXM3) also
contains one unresolved reference. This is pretty similar to the case
above. The missing element is CKF. This can be found from the definitionof the related element.
Affected query YY_FT_TEST has 3 unresolved references. Here the case
is a bit different. According to my analysis the missing elements are
just such global part of a query like Filter and Sheet. This more less
means the entire definition of this query is not available.
Possible solution.
As far as I see, all missing elements are local for the BWD system.
This means that most likely we can not use transports from the other
system. By just to use this option aswell, please check if some of thesemissing can be found in the other systems
4B773WHW1GK5WZAPK5CZHZSH7
4BO650QIIZZ51VCNLZXSC4MP7
4BO652NN9NEIPI7P2IIUUMB57
4BPGWZK405TZ1061K1FSQCT0R
4DVE6TT3PU9YJ6RQ4ETM2MDIJ
and
4DBJFSQOSAL3WPK8LSCNUWNAJ
If you find something, it is necessary to transport them to the BWD
system. This will solve some issues.
But probably you will not find them. Therefore the alternative way will
be to replaces the missing objects in the definition of the affected
queries by some other availabe objects. This is to be done manually.
For example mising CKF can be replaced by a constant value and then
in Query Designer replaced once again by any avaialbe CKF.
Such technique can help te achieve technical consistency of the queries
ZORQSP_ZSPNNM021_NN_04, YTEMP_ZSCNNM04_01 and ZORQSP_ZSPNNM021_NN_05.
Situaiton with the YY_FT_TEST is more critical. There are no chances
to repair this one. The only option will be to delete it using the
transaction RSZDELETE.
Please tell me how would you like to process. In principle, this case
is not really critical as the missing elements are just locally affect
queries and not used by reusable query components like CKFs/RKFs which
might be shared between many other queries also affecting them.

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.

Query CKF & RKF

Similar Messages

Maybe you are looking for