What is the name the part under the kepboard on mini 5103?

For a Mini 5103, I'm looking to purchase a keyboard and the layer beneath the keyboard, between the motherboard and the keyboard, but I don't know what that part is called. Please let me know what to call it. Thanks!
Mini 5103, Atom N550, 360 hard drive, 2G
This question was solved.
View Solution.

HI,
The layer beneath the keyboard, between the motherboard and the keyboard is called "TOP COVER"
Check this link for ordering parts (this link includes part number and part description)
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=ca&taskId=125&prodSeriesId=...
You can Order from HP directly or you can get them cheaper go to Ebay by searching with the partnumber
Hope this helps,,
**Click the KUDOS star on the left to say 'Thanks'**
Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.
**Click the KUDOS star on the left to say 'Thanks'**
**---'Accept as Solution' ----**if it solves your problem and make it easier for other people to find solutions.

Similar Messages

What is the brand for mini 110-4111ej Hard drive?

What is the brand for mini 110-4111ej Hard drive?
This question was solved.
View Solution.

HP uses different brands to fit the need for the SATA hard disk, so there is no specific brand that I can state. Why don't you use the hard disk test that is present in the BIOS?
Replacement hard disk specifications
****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
2015 Microsoft MVP - Windows Experience Consumer

What's the most recent Mini I can install Leopard On

I need Classic + Rosetta. What is the most recent Mini I can really put Leopard (OS 5.x) on? Not that it shipps with, but will actually install and work. Or can copy onto from a clone which will run?
TIA,
Bill

Three options:
1. Purchase the Late-2005 Mac Mini (PowerMac10,2). This was the last PowerPC Mac Mini that can run the Classic Environment in Tiger; so it does not need Rosetta.
2. Purchase the Mid-2010 Mac Mini (macmini4,1). This model comes with Snow Leopard, which is the last version of OS X to allow Rosetta. Rosetta must be optionally installed. For Word 5.1, see below.
3. Purchase the Mid-2011 Mac Mini (Macmini5.1). This model comes with Lion, but if you follow the work of newfoundglory in this thread, you can downgrade (or dual-partition) this model to Snow Leopard (for Word 5.1, see below):
https://discussions.apple.com/message/17829389#17829389
For the younger folk reading this thread, the OP is among the few remaining purists that loved Microsoft Word 5.1 on the Mac. A little bit of history:
Until the Mac was developed and released, Microsoft was almost exclusively an Operating System and Programming software company (Multiplan being the first and sole applications software exception at that time).
Steve Jobs recruited Bill Gates and Microsoft to set up a programming team to build applications for the Mac, then in development. Out of the effort came Word 1.0 (yes, Word was originally written exclusively for the Mac).
This program was ultimately refined until version 5.1. Then with the release of version 6, Mac users were horrifed as the program had been "window-fied" and it was never as pure a Mac program since...
Now back to our originally program, already in progress:
You can run Word 5.1 on an Intel Mac in a Classic emulator program known as SheepShaver (and its cousin, Chubby Bunny). I use SheepShaver to run Classic Word Perfect, among other Classic apps.
Here is a recent post I made about this Classic emulator:
With the newer Intel Macs, you have to run a Classic emulator such as SheepShaver, which requires you to extract the Mac ROMs from your older Classic Mac and then install Mac OS 9.
A related program is Chubby Bunny, which comes bundled with all of that included.
More information on SheepShaver:
http://www.emaculation.com/doku.php/sheepshaver_mac_os_x_setup
and
http://www.everymac.com/mac-answers/mac-os-9-classic-support-faq/run-macos-9-on- intel-macs.html
and more information about Chubby Bunny:
http://www.macwindows.com/OS9_on_Intel_Mac.html#092408b
and
http://hackthemac.blogspot.co.uk/2008/08/chubby-bunny-old-virtual-machine.html

What does the new mac mini really look like? raised or not?

looking at the images on the mac mini page http://www.apple.com/macmini/ it clearly shows the mini with it's front edge resting on the ground in all the images from the front. the reflections touch. but when you follow the 'Design' link it shows that the new mini is resting on a raised foot, so it floats.
i'm pretty sure the floating version is the real version, but why the inconsistency?

it's not an optical illusion. it's just wrong in the images. i agree with the people who made the illustrations, it looks better when it's flat on the ground and not floating.
http://www.macrumors.com/2010/06/16/mac-mini-mid-2010-teardown-photos/
that gives you a better idea of what the new mac mini looks like from the front in a similar angle to the images on apples site. notice the very large gap between the reflection and the front face of the mini. also notice the large black shadow caused by the mini being raised up on the black circular foot on it's base. There isn't an angle that you you can move the camera to that would eliminate the shadow or distance between the reflection and the case and still see the front face as you do in the images.
it's just an odd inconsistency that misrepresents what the final product looks like.

What's the difference between Mini DisplayPort and Mini DVI?

I've got a two month old unibody MBP. I want to connect it to my TV with an HDMI cable and therefore I need an adapter cable.
I've searched online and found Mini DVI to HMDI cables and they have the same symbol on them as the port on my mac, but the specs for my mac call the port a Mini DisplayPort.
Is Mini DVI and Mini DisplayPort the same thing?

The icon that appears beside the port indicates "video out", not any particular kind of port that can be used for that purpose. Apple has used at least six different ports to provide video out on notebook Macs in the last several years: S-Video, VGA, mini-VGA, DVI (and dual-link DVI), mini-DVI, and mini-Displayport. I believe the same icon appears beside all of them, but the ports and plugs don't look alike.

What does full name on Part number?

Dear all,
Does any one know the full name of part number as below?
1- WS-C3650-48FS
what is full name WS, FS?
2- WS-C3650-48TQ
what is full name TQ?
3- WS-C2960X-48FPD-L
what is full name X , FPD-L
do you have link to show on this ?
Best Regards,
Rechard

There is not a publicly published complete and explicit definition of the letters Cisco uses in their product nomenclature. the best one can do is look at either the product data sheet or Cisco Commerce Workspace (partner / reseller only) and see what the product description is.
For instance, WS-C3650FS (-E or -L) is "Cisco Catalyst 3650 48 Port Full PoE 4x1G Uplink IP Services" (with Enhanced or Lanbase license), WS-C3650-48TQ is "Cisco Catalyst 3650 48 Port Data 4x10G Uplink IP Services" and WS-C2960X-48FPD-L is "Catalyst 2960-X 48 GigE PoE 740W, 2 x 10G SFP+, LAN Base".
WS generally is a prefix on part numbers for all Wire Speed switch products. (Though that breaks down a bit on some of the smaller Catalyst models.) I've also seen it refer to "Workgroup Switch" class products.
FS means is is a switch with fiber user ports.
X distinguishes the newer 2960 models from the original 2960 series.
FPD-L mean it has Full PoE+ and comes with Lanbase software feature license.
Generally the letters at the end refer to the uplink type and license level.
Also please see this earlier discussion:
https://supportforums.cisco.com/thread/2135341

What are the best ipad mini cases

Does any one have any recomendations foran ipad mini cases?

MikeNMN wrote:
I agree with the earlier post, you gotta go with the Otterbox Case. I purchased this case for my IPad Mini. It is a perfect fit and does not add much weight at all. It is great protection and a necessity to have this for the IPAD Mini. The stand is nice for both upright and side display of the iPad Mini on my desk.
http://www.amazon.com/gp/product/B009WU5XUG
I'm what you consider a gadget junkie always trying out new products and since the introduction to tablets (iPad's) I've been searching for that perfect case as well. I've owned the clamcase (keys broke three months from purchase date and yes, just after the warranty expired), hard shell, soft shell, leather cases, and the Otterbox Defender case for the iPad2. The previous edition I was not as impressed with. The silicon was a bit loose and felt too bulky but it did do it's job twice, when I dropped it on concrete. I just purchased the iPad Mini and shopping for a case, a young man sold me this otter box that was his display. This case rocks!!! The silicon wraps tightly around the plastic case which feels like one entire piece. It does add to the weight of the mini but definitely better than the larger version, not to mention, the peace of mind knowing it's protected. Also, the rubber port covers for the plug, earphones actually stay in place when pushed in.
A brief word about some of the AMAZING features of this case... The screen protector is built in to the top part of the case, and although I had trepidation about that initially, my fears were allayed; the screen sits on the screen directly and there is no space between the screen and the protector. The removable cover doubles as a stand in several positions, and feels like Cole Hamels could throw a fastball at it and it would still protect the screen. Also, you can use it on the front or the back so if you're throwing your mini in a backpack or luggage, you can do it without fear.
Obviously there's not too much to say about this case that hasn't already been said. It's tough, it's stylish and it's functional. But that should be no surprise... OtterBox is renowned for their cases by now. All I can recommend is this: to those who are wondering whether it is worth the money, imagine what it will be like to take your iPad mini out of the OtterBox in a year and have it look exactly the same as the day you bought it. No scratches, no scuffs, cracks.
It's just an amazing case, well worth money for the peace of mind it brings.

What is the difference between Mini DVI to VGA adapter and Mini DisplayPort to VGA Adapter?

My macbook is MacBook4,1. early 2008

The port itself is shaped different.....
.....here is a link to read through on the technical differences of the 2 ports....
http://en.wikipedia.org/wiki/Mini_DisplayPort
......your MacBook has the Mini-DVI port........the VGA end of the adapter is the same on both...

What about the cheaper mac mini?

Sorry for not aksing this in my other thread. But in the 1.83 Mac Mini The Disc Dive in let you burn cds and DVDs? Dvds is nota big deal but i assume it has a CD drive.
Am I correct?

Yes, the 1.83 model has a 'combo' drive that reads and writes CDs and CD-RW, but only reads, not writes, DVDs.

What is the name of the small part that comes lose when you are removing the two battery screws on the left side of the battery, the small part is under the top screw when removing the iPhone 4s battery?

What is the name of the small part that comes lose when you are removing the two battery screws on the left side of the battery, the small part is under the top screw when removing the iPhone 4s battery?

It's the part that means you've voided your warranty and the right to get an out-of-warranty replacement from Apple.

Can you change multiple titles under "names" removing part of the title, but leaving some unaltered?

I have just uploaded severa audio books into itunes, all the information howerv is listed under the "names" Heading. so under names it goes "name of book - name of chapter." And severaly of the books and talks have 50+ chapters. Is there a way to batch them together and delete multiple "name of book" parts, but leaving the name of the chapter. Doing this manually could take hours, and be potentially disasterious if I mislable or miss some chapters. Thank you
~Stay Hungry
Stay Foolish

Check Dougscripts. There may be one for removing a defined text from a tag.

What is the schema name for service part planning module

Hi Experts,
i need the following info
1. what is the schema name for SPP module
say for example we call ASCP as MSC, in similar passion what is the name given to SPP.
2. I have searched for the table details in etrm site ( in R12.1.1 ) but it is not available, can anyone help me out to get the table details in SPP ?
Thanks for your valuable time.
Bye
Babu

Thanks Bob for your clarification.
Do you have any idea, which are all the table that got linked with SPP in the MSC schema ?
If we have any separate link in metalink, pls share that link.
Thanks again for your valuable time.
Babu Ji

What is the domain name setting under internet tcp/ip?

In the airport utility > Internet > TCP/IP panel, what is the 'Domain Name' field used for?

The Domain Name setting would be that of your ISP. For example, I have Cox as my ISP. My Domain Name setting is: cox.net
This field is not mandatory and is used to establish the appropriate domain that your Public IP address is located to assist DNS in directing requests.

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.

What are the field names for below mentioned

Hello Friends
What are the fields names for below tables
in EKKO
Purchase Document Date
Net Value of the purchase document.
In EKPO
Item Description
From which place We bought it. (It means in Sales Items there we can know from which plant we sold the goods, like in EKPO, there is any field like this)
Please let we are defining the report to find out the stock availability for perticular storage location using select Options plant, company code, material no.
How many tables involve her to build this report. and also field names, they come under which table.
Please send me this information ASAP. PLz Plz Plz..........
Regards
Praveen

You can check the fields of these tables via SE11
Purchase Document Date - EKKO-BEDAT
Item Description - EKPO-TXZ01
Net price per item - EKPO-NETPR.
Regards,
Rich Heilman

What is the name the part under the kepboard on mini 5103?

Similar Messages

Maybe you are looking for