PR00 is missing in the table PRCC_COND_CT

Hi Experts
I have successful replicated all conditional Objects like DNL_CUST_CNDALL,DNL_CUST_CND,DNL_CUST_PRC from ECC to CRM2007,
when i try to create a Sales Order in crm Condition types are missing ,i can able to see only values with Zero in the condition Tab page for which i have maintained the conditional maitainece gp for PRODUCTCRM inorder to see condition types in CRM product conditions as per Building Block(c03).
so what i was observed is condition types like PR00,K004,K005,K007 are missing in the table PRCC_COND_CT.which are not properly replicated into CRM system for which i have done the initial replication for all conditional objects so many time.
Hence i request you all could you please tell me, is there any way to get all condition types into crm
will it possible to add manually condition types in crm system.
i would appreciate you help
thanking you in advance
Regards
Rao

Hi Bhanu
I have checked in SLG1 there are following errors and warnings
Errors are:Table PRCC_COND_PPD has been posted in the database with errors
Message no. CND_MAP155
Table PRCC_COND_CT has been posted in the database with errors
Message no. CND_MAP155
1 .Error converting field FIELD_TIMESTAMP into /SAPCND/T685 for condition type BGEW.
    Message no. CND_MAP181
Diagnosis
Data records from the tables mentioned are required for converting field contents. These tables show inconsistencies that could have the following causes:
A required entry is not available in one of the tables.
Field contents for table entries are not compatible with each other.
System Response
Only those data records are modified in the table for which consistent table entries exist, and for which conversion of field entry is possible.
Procedure
With the help of OSS Note 314542 and instructions contained therein, analyze causes, and make necessary corrections.
2. Error converting field FIELD_TIMESTAMP into /SAPCND/T685 for condition type BI00.
    Message no. CND_MAP181
Diagnosis
Data records from the tables mentioned are required for converting field contents. These tables show inconsistencies that could have the following causes:
A required entry is not available in one of the tables.
Field contents for table entries are not compatible with each other.
System Response
Only those data records are modified in the table for which consistent table entries exist, and for which conversion of field entry is possible.
Procedure
With the help of OSS Note 314542 and instructions contained therein, analyze causes, and make necessary corrections.
3.Error converting field FIELD_TIMESTAMP into /SAPCND/T685 for condition type PR00.
Message no. CND_MAP181
Diagnosis
Data records from the tables mentioned are required for converting field contents. These tables show inconsistencies that could have the following causes:
A required entry is not available in one of the tables.
Field contents for table entries are not compatible with each other.
System Response
Only those data records are modified in the table for which consistent table entries exist, and for which conversion of field entry is possible.
Procedure
With the help of OSS Note 314542 and instructions contained therein, analyze causes, and make necessary corrections.
ther are follwoing Warnings:
1. Double entry for table PRCC_COND_PPD. For details, see long text.
    Message no. CND_MAP815
Diagnosis
An error occurred during the update. You tried to update a data record with the key KAPPL = CRM and KALSM = 18CBCL in table PRCC_COND_PPD. A data record with the above key already exists in table PRCC_COND_PPD.
System Response
Data records with identical keys conflict with data integrity. The above data record was not updated for this reason.
Procedure
Use SAP Note 0314315 to eliminate the cause of the error.
2. Double entry for table PRCC_COND_CT. For details, see long text.
Message no. CND_MAP812
Diagnosis
An error occurred during the update. You tried to update a data record with the key KAPPL = CRM and KSCHL = 18CL in table PRCC_COND_CT. A data record with the above key already exists in table PRCC_COND_CT.
System Response
Data records with identical keys conflict with data integrity. The above data record was not updated for this reason.
Procedure
Use SAP Note 0314315 to eliminate the cause of the error.
Edited by: padmarao mota on Mar 13, 2009 9:47 PM

Similar Messages

Physical inventory document was missing in the table

Dear all,
My client have done a physical inventory means they have counted and post the difference also.
but i was trying to see the document not showing in the table or mi20 or any other transaction.
after that lot of documents has been created, only particular phy. inventory document was missing.
Please help me resolve this issue.

how do you know that the count was posted if the document is not in the tables?
A document is deleted physically if the document has no counts posted and you delete it in MI02.
The only other legal option to get a document off the tables is with archiving.
In transaction SARA for object MM_INVBEL click the button for Adminstration to see if there was an archiving done.

How to select data missing in the table?


I have a list of strings as follows (not in the table):
'aaaaa'
'bbbbb'
'ccccc'
In the table T1 I have a VARCHAR column x. The data under x are as follows
'aaaaa'
'ccccc'
I want to formulate a query such that it will bring 'bbbbb' since 'bbbbb' is not in the table. Please help!
Thanks.



We get asked this question on a reasonably regular basis.. Apparently people think it's perfectly normal and acceptable to ask a data repository for all the data it doesnt contain. We normally have a conversation that runs:
Tech "So, you want to see all data in the database, that is not in the database?"
User "Yes"
Tech "How do you propose that a database gives you all the information it doesnt have"
User "Oh. Now you put it that way.."
Actually I wish someone would hurry up and invent a data repository that does this, that way if I suddenly took a liking to The Beatles, but didnt have any of their songs in my collection, I could ask the data repository for all the Beatles songs I didnt have and.. bam! I'd have all the Beatles songs! cool
Seriously.. youre asking us to tell you how to make an oracle db tell you what information it doesnt have, but youre refusing to supply a block of data for it to compare against (i.e. so it can know what "Everything" is, in the phrase "Everything it doesn't have".
Do you really see it as possible?
Edited by: charred on Oct 22, 2008 9:45 AM

Entry missing in the table

Hi all,
I am simply entering values in the table every 100ms.
For first 10 mins the entries comes at constant speed i.e 10 values per sec. but after that the values starts decreasing,
though slowly.every 10 mins the no of samples goes down by one.
I have attached a vi, In it a table is given which is not connected to anything, In that i have generated the output.
I think the loop execution time in increasing , can u help me in that?
My only aim is that, to get reading in the table every 100ms exact.
Regards,
Shrek
Solved!
Go to Solution.
Attachments:
Untitled 3.vi ‏92 KB

Hi shrek,
2 points:
1) at the moment you don't get values exactly every 100ms as the attachment shows (simply changed format for timestring)
2) to maintain exact timing you shouldn't build big arrays as you do with your table! The bigger the table the more LabView has to copy from one memory block the the next...
Message Edited by GerdW on 08-24-2009 03:27 PM
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome
Attachments:
Untitled 3.vi ‏92 KB

Date field is missing in the Table maintainance generator

Hi,
A table is created. A date field is there in that table. I tried to create a table maintainance generator for this table using 2 screens. Table maintainance generator is created. But when I go to SM30 , I am unable to see this DATE field in the SM30 , in the first screen. But when I go to maintainance screen , I am able to see this field. This particularly happening with date field.
Could you please help me.
Regards,
Satya

go to se11 and type the table what you want.
utilities, table maintenance generator.
you config the options that you need.
press F6 and go to sm30.
its only this.
Regards

Entry "EUROPE" is missing in the table "TTZDF & TTZDV".

Hello Guys,
I am facing this Dump error in my SAP, could anyone please help me in it, i am writing down the error analysis,
:CONVERT_TSTMP_INCONSISTENT_TAB:
In the existing case, it was tried to make a conversion between the
local date (and time) and the ABAP timestamp (and vice versa). In doing
so, it was detected that the entry "EUROPE" in table "TTZDF & TTZDV" is
missing.
Basically, all entries from table 'TTZZ' for 'ZONERULE' must also appear
in table 'TTZR' and all entries for 'DSTRULE' must also appear in table
'TTZD'. Moreover, all entries for 'DSTRULE' from table 'TTZD' must
appear in table 'TTZDF', and/or table 'TTZDV', except for the case if a
time shift of '00:00:00' is specified in field 'DSTDIFF' for this
'DSTRULE'.
Because of that i am unable to use this client 001
Regards,
Omar

Hello Omar,
You can use report TZCUSTIM with target client 001.
Check the following notes for further information:
198411 - Current data and information about time zones
1260674 - Effectiveness of changes to time zone Customizing
Regards,
Eduardo Rezende

Querying Dates missing in the table

I have columns name, taskname start_date and end_date in my table.
e.g.,
Name Task StartDate EndDate
abc task1 2008-04-01 2008-04-03
abc task2 2008-04-05 2008-04-15
abc task3 2008-04-08 2008-04-18
abc task4 2008-04-21 2008-04-25
abc task5 2008-04-19 2008-04-23
abc task6 2008-04-25 2008-04-30
I need to find out the dates for which there are no tasks planned for the person in the month excluding Saturdays and Sundays.
Is it possible to get the output in a single SQL itself, or else how could it be done in PL/SQL procedure ?

Hi,
You'll need to do an outer join to a table (or subquery) that has all the possible dates. Here's one example from this site:
OUTER JOIN

Entry for condition type missing in table PRCC_COND_CT

Hi guys,
I got this error message in my BDoc.
It ask me to
"Fill the table PRCC_COND_CT bu using a Customizing download, and then restart the rolled back block in the inbound queue."
I am not too sure what is a customizing download.
Can you guys help me out?
Cheers
Lawrence

Hi,
Firstly please apply the note 1003793 and then run the customizing load again and check for errors.
then if you get any errors like
"It is not possible to change client-independent Customizing objects Message no. CND_MAP204 "
Then log into SCC4 transaction and then make the following change
"changes to repository and cross-client customizing allowed" under Cross-Client Object Changes.
Thanks,
Abishek

Some coloumns are missing in the transaction FB50

Hi Experts,
We are finished with the upgrade from 4.6c to ECC6.0.
Here we have an issue with FB50 transaction.
In ECC6.0 the following coloumns are missing in the table control in the initial screen of the transaction FB50,
1) STATUS
2) Tax jurisdictn Code
3) W/O cash disc
We have deactivated the transaction variants also but still we are not getting the above coloumns.
Thanks,
Rakesh.

check for SPRO configurations there are not
cheers
s.janagar

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.

"Missing most detailed table for dimension tables" eror when I run the Global Consistency check

ERRORS:
Business Model DAC Measures:
[nQSError: 15003] Missing most detailed table for dimension tables: [D_DETAILS,D_EXECUTION_PLAN,D_TASK].
[nQSError: 15001] Could not load navigation space for subject area DAC Measures.
I am also attaching my Business Model layer for easy understanding. I have a fact table and several Dimension table. I got this error only after creating the following hierarchies:
Execution Plan -> Tasks -> Details
Start Date Time Hierarchy
End Date Time Hierarchy
Is there a solution for this problem? Thanks in advance!

Yes ! My Task Hierarchy has 3 dimension tables that form a hierarchy :Execution Plan -> Tasks -> Detail
All the 3 levels in the hierarchy are 3 different dimension tables.

Where are my mobile service and database tables? They're missing from the Portal.

I've been using Azure for a couple of months. I just logged in and my mobile service is missing. And while my SQL database is still there, all the tables I created are gone. I received no email about them being removed and there's no log on the site that
indicates anything happened to them. My website also is there and appears to be working fine. I had a lot invested in the tables and mobile service. Can anyone help me figure out what is going on?

Hi
For this
subscription question I suggest you contact
support
team by creating a support ticket at http://www.windowsazure.com/en-us/support/contact/
Beacause only them
have the permission to help you fix your subscription issue.
Thanks.
Please mark post as answered if it helped!

/BIC/FFIN_PS_6 table is missing in the database

Hello All,
We were unable to Delete requests from FIN_PS_6 , as we perform the job it is getting terminated with DBIF_RSQL_TABLE_UNKNOWN message.
Found out that table /BIC/FFIN_PS_6 is missing in the database. Any clues to find how this Table got deleted? logs or traces for this activity.
Thanks & Regards,
Madan

Hi Vani,
/BIC/FFIN_PS_6 seems to be a Fact table. So please activate the corresponding Infocube .
Then try to work on it.
Regards,
James Harold.

Missing tables in the Table tree

I installed SQL developer version 1.5.0.52 and I noticed that some of the tables that should be showed in the tree were missing. Although I can see these tables writing a command :
Select * from user_tables where table_name like 'AQUA%'
Also, I can use these tables in queries and the 'Find DB Object' find them but these tables are not showed in the tree. The owner has more then 600 tables and I didn't notice a problem like this in previous versions of SQL Developer.
Has somebody any idea about?
Thank you

I am also experiencing the same issue, although no tables / views / indexes / triggers are displayed in the object tree for any of my connections.
I am using verison 1.2.1. Will downloading version 1.5.0.52 fix this issue? Thank You

Fields missing in SM30 after adding new fields to the table

Hi ABAPers,
I added a new field & marked another field as primary key in the table. Then I generated the table maintenance view for the table in SE55 and adjusted Database utility SE14.
When i saw the table in SM30. The number of fields in the overview screen of SM30 shows less field then existing in table. i.e in my table i have 10 fields(3 primary). in SM30 it shows only 5 fields(3 primary + 2 normal fields)
In SE51, the overview screen of the table show less fields in the field list..
I want all the fields in the Table maintenance overview screen. Please suggest me a way forward friends..
Note: the system is 4.0B.
Thanks...Suresh Kumar

Hi
You have to re-generate your dialog for SM30 by table maitenance generator.
- From Se11 go to table maitenance generator
- Choose update icon
- Set flags for NEW FIELD
- Go to expert
- Set flag to re-generate dynpro
Message was edited by: max bianchi

PR00 is missing in the table PRCC_COND_CT

Similar Messages

Maybe you are looking for