Difference b/w index and key

can you please tell me the difference between the follwing UI elements
1.dropdownbykey and dropdownbyindex
2.radiobutton group by key and radio button group by index
and also tell me in which case which UI need to be used
Thanks
rahul

DropDownByKey
A DropDownByIndex UI element provides the user with a dropdown list box. You cannot select more than one entry from the selection list. The UI element consists of a text field, a button, and a selection list. Any list item already selected is displayed in the text field. When the user chooses the pushbutton, a list of all possible values is displayed.
DropDownByIndex
A DropDownByIndex UI element provides the user with a dropdown list box. You cannot select more than one entry from the selection list. The UI element consists of a text field, a button, and a selection list. Any list item already selected is displayed in the text field. When selecting the button, a list with all possible values is displayed.
http://help.sap.com/saphelp_nw04s/helpdata/en/d9/478041a17e060de10000000a1550b0/frameset.htm
In radiabutton we can have the only one decision.But
checkbox we can have mulitiple options.
based on the usage we choose these controls.
for example,
RadioButton
Gender - o Male o Female
here we can select only one option
for example,
CheckBox
your Interested Games?
o cricket o football o valleyball o hockey
here use may have more than option.
i hope this is enough.
award the point if ans is help full.

Similar Messages

Difference b/w index and unique

Hi,
Difference b/w index and unique?

hi,
The optional additions UNIQUE or NON-UNIQUE determine whether the key is to be unique or non-unique, that is, whether the table can accept duplicate entries. If you do not specify UNIQUE or NON-UNIQUE for the key, the table type is generic in this respect. As such, it can only be used for specifying types. When you specify the table type simultaneously, you must note the following restrictions:
You cannot use the UNIQUE addition for standard tables. The system always generates the NON-UNIQUE addition automatically.
You must always specify the UNIQUE option when you create a hashed table.
INDEX:
An index can be considered a copy of a database table that has been reduced to certain fields. This copy is always in sorted form. Sorting provides faster access to the data records of the table, for example using a binary search. The index also contains a pointer to the corresponding record of the actual table so that the fields not contained in the index can also be read.
The primary index is distinguished from the secondary indexes of a table. The primary index contains the key fields of the table and a pointer to the non-key fields of the table. The primary index is created automatically when the table is created in the database
You can also create further indexes on a table in the ABAP Dictionary. These are called secondary indexes. This is necessary if the table is frequently accessed in a way that does not take advantage of the sorting of the primary index for the access.
Indexes speed up data selection from the database. They consist of selected fields of a table, of which a copy is then made in sorted order. If you specify the index fields correctly in a condition in the WHERE or HAVING clause, the system only searches part of the index (index range scan).
The system automatically creates the primary index. It consists of the primary key fields of the database table. This means that for each combination of fields in the index, there is a maximum of one line in the table. This kind of index is also known as UNIQUE.
If you cannot use the primary index to determine the result set because, for example, none of the primary index fields occur in the WHERE or HAVINGclauses, the system searches through the entire table (full table scan). For this case, you can create secondary indexes, which can restrict the number of table entries searched to form the result set.
You create secondary indexes using the ABAP Dictionary. There you can create its columns and define it as UNIQUE. However, you should not create secondary indexes to cover all possible combinations of fields.
Only create one if you select data by fields that are not contained in another index, and the performance is very poor. Furthermore, you should only create secondary indexes for database tables from which you mainly read, since indexes have to be updated each time the database table is changed. As a rule, secondary indexes should not contain more than four fields, and you should not have more than five indexes for a single database table.
If a table has more than five indexes, you run the risk of the optimizer choosing the wrong one for a particular operation. For this reason, you should avoid indexes with overlapping contents.
Secondary indexes should contain columns that you use frequently in a selection, and that are as highly selective as possible. The fewer table entries that can be selected by a certain column, the higher that columns selectivity. Place the most selective fields at the beginning of the index. Your secondary index should be so selective that each index entry corresponds to, at most, five percent of the table entries. If this is not the case, it is not worth creating the index. You should also avoid creating indexes for fields that are not always filled, where their value is initial for most entries in the table.
If all of the columns in the SELECT clause are contained in the index, the system does not have to search the actual table data after reading from the index. If you have a SELECT clause with very few columns, you can improve performance dramatically by including these columns in a secondary index.
What is the difference between primary index and secondary index?
http://help.sap.com/saphelp_47x200/helpdata/en/cf/21eb2d446011d189700000e8322d00/frameset.htm
A difference is made between Primary & Secondary indexes to a table. the primary index consists of the key fields of the table and a pointer to the non-keys-fields of the table. The Primary index is generated automatically when a table is created and is created in the datebase as the same times as the table. It is also possible to define further indexes to a table in the ABAP/4 dictionary, which are then referred to as Secondary indexes.
Message was edited by:
Roja Velagapudi

Difference bet cube indexes and dso indexes

hi,
1.can any tell me the difference between cube indexes and dso indexes?
if we have aggregates on the cube it improves the performce of the query created on it
2.so why to create indexes on the cube?
for creating indexes on the dso i right click on dso and click create indexes
it is asking two options
1.unique key 2.non unique
4.what is the functionality of these two?
i will assign points if ur answers clear my questions

The BW automatically defines multiple indexes on your cubes, based on the dimensions you have defined. You do not need to create any additional indexes on your Fact tables. It can somtimes be helpful to create a secondary index on dimension tables or master data tables depending on their size and the queries. There is not BW wkbench tool to do this, it usually requires a DBA in most shops.
Secondary indexes on DSO/ODS can help some queries substantially, again, depending on the data and the queries. You can define secondary indexes on DSO/ODS from the BW workbench.
Aggregates are another tool for query performance, by summarizing the data, it can reduce the number of rows that must be read by a query. Again, it dpends on the query and the data as to how much an aggregate helps.

What is difference between sy-index and sy-tabix and where both are using ?

what is difference between sy-index and sy-tabix and where both are using ?

hi nagaraju
sy-tabix is in Internal table, current line index. So it can only be used while looping at the internal table.
sy-index is in Loops, number of current pass. This you can use in other loop statements also (like do-enddo loop, while-endwhile)
SY-INDEX is a counter for following loops: do...enddo, while..endwhile
SY-TABIX is a counter for LOOP...ENDLOOP, READ TABLE...
Here is an example from which you can understand the difference between sy-tabix and sy-index.
Itab is an internal table with the following data in it.
id Name
198 XYZ
475 ABC
545 PQR.
loop at itab where id > 300.
write :/ itab-id, itab-name , sy-tabix, sy-index.
endloop.
My output will be :
475 ABC 2 1
545 PQR 3 2
Sy-tabix is the index of the record in internal table.
sy-index gives the no of times of loop passes.
So, for the first record in the output (475 ABC), 2 is the index of the record in internal table and as it is first time loop pass occured, sy-index value is 1.
Regards,
navjot
award points

Difference between btree index and bitmap index

i knw btree is the default index.but what's are the other difference present.

21 characters and 10 seconds at google:
http://www.akadia.com/services/ora_bitmapped_index.html
http://www.oracle.com/technology/pub/articles/sharma_indexes.html
http://www.dba-oracle.com/art_9i_indexing.htm
Dim

Difference Between Radio Button Group By Index and Key

what is main difference between RadioButtonGroupByIndex and RadioButtonGroupByKey ? And In which situvation we go for RBGBIndex and RBGBKey?

They do not differ from each other when displayed on the screen. However, the data binding model for the two UI elements is compeletely different. Index & Key Binding concepts are very elaborately explained in the following <a href="http://help.sap.com/saphelp_erp2005vp/helpdata/en/d7/f08841e3af1609e10000000a155106/frameset.htm">SAP Help</a>
~Suresh

Error while renaming indexes and keys in the tables

hi gems...good afternoon..
i am using oracle 11gr2 database.
when i am trying to rename the primary key, foreign key, indexes of all the tables as per the standard, then the following error is given...
ORA-00604: error occurred at recursive SQL level 1
ORA-01000: maximum open cursors exceeded
ORA-00604: error occurred at recursive SQL level 1
ORA-01000: maximum open cursors exceeded
ORA-01000: maximum open cursors exceeded
currently the maximum open cursors parameter is set to 300.
please help..thanks in advance

thanks a lot for your help..
there are total 162 records in the v$open_cursor for that user.
among that the open cursor is only 4 and open-recursive cursor is only 6 for that user.
in my session i am executing only the renaming of the constraints and nothing more.
When i have queried the v$open_cursor for cursor_type='OPEN' for all the users, then i got that it has exceeded the value of open_cursors parameter.
So how can i resolve that....

Calculate the difference between Creation date and key date

Hello
I want to calculate the difference between creation date of the document with key date(todays date). How can i do that in the query designer. Also then I want to restrict my key figure on this difference if it is =10..please can someone suggest what can be done
thanks

Hi Grame...
For the days calculation ..
I suggest you to use replacement path ..
I have the reference that you can see the sample. The case of samples is also about day calculation.
http://www.sd-solutions.com/documents/SDS_BW_Replacement%20Path%20Variables.html
Hopefully it can help you a lot.
Regards,
Niel.

What is difference between sy-tabix and sy-index.

SAP Seniors,
Can you please let me know what is difference between sy-index and sy-tabix.
I read the SAP help, it is confusing for me. it looks like both are same from help. please help me.
Thank you
Anitha.

HI,
Here is a brief description of difference between SY_TABIX and SY_INDEX and using them with several conditions.
SY-TABIX
Current line of an internal table. SY-TABIX is set by the statements below, but only for index tables. The field is either not set or is set to 0 for hashed tables.
APPEND sets SY-TABIX to the index of the last line of the table, that is, it contains the overall number of entries in the table.
COLLECT sets SY-TABIX to the index of the existing or inserted line in the table. If the table has the type HASHED TABLE, SY-TABIX is set to 0.
LOOP AT sets SY-TABIX to the index of the current line at the beginning of each loop lass. At the end of the loop, SY-TABIX is reset to the value that it had before entering the loop. It is set to 0 if the table has the type HASHED TABLE.
READ TABLE sets SY-TABIX to the index of the table line read. If you use a binary search, and the system does not find a line, SY-TABIX contains the total number of lines, or one more than the total number of lines. SY-INDEX is undefined if a linear search fails to return an entry.
SEARCH <itab> FOR sets SY-TABIX to the index of the table line in which the search string is found.
SY-INDEX
In a DO or WHILE loop, SY-INDEX contains the number of loop passes including the current pass.
Hope this helps.
Thank you,
Pavan.

Difference B/WUser and Key user

Hi all,
What is the Difference B/W User and Key user?
Thanks in Advance
Krish...

Hi
Key users have some knowledge regarding the SAP module they use.
So this is why, they can be the interface between SAP expert or SAP developper, and the users.
SAP user are kind of "end-user" and, in genaral, they don't have a computing/ERP view of the system.
Erwan

Regarding sy-index and sy-tabix

Hi,
What is the major difference between sy-index and sy-tabix ,
can you give me one good example with code..
Regards,
Reddy.

Hi,
SY-TABIX - Current line of an internal table. SY-TABIX is set by the statements below, but only for index tables. The field is either not set or is set to 0 for hashed tables.
APPEND sets SY-TABIX to the index of the last line of the table, that is, it contains the overall number of entries in the table.
COLLECT sets SY-TABIX to the index of the existing or inserted line in the table. If the table has the type HASHED TABLE, SY-TABIX is set to 0.
LOOP AT sets SY-TABIX to the index of the current line at the beginning of each loop lass. At the end of the loop, SY-TABIX is reset to the value that it had before entering the loop. It is set to 0 if the table has the type HASHED TABLE.
READ TABLE sets SY-TABIX to the index of the table line read. If you use a binary search, and the system does not find a line, SY-TABIX contains the total number of lines, or one more than the total number of lines. SY-INDEX is undefined if a linear search fails to return an entry.
SEARCH FOR sets SY-TABIX to the index of the table line in which the search string is found.
SY_INDEX - In a DO or WHILE loop, SY-INDEX contains the number of loop passes including the current pass.
sy-tabix is the tab index - the index of the record in the internal table you are accessing,
sy-index is the loop counter.
If you use a condition in LOOP the sy-index will go from 1 to n, but sy-tabix will refer to the line in the internal table.
Hope this helps u.
Thanks,
Ruthra

Difference Between Unique Index vs Unique Constraint

Can you tell me
what is the Difference Between Unique Index vs Unique Constraint.
and
Difference Between Unique Index and bitmap index.
Edited by: Nilesh Hole,Pune, India on Aug 22, 2009 10:33 AM

Nilesh Hole,Pune, India wrote:
Can you tell me
what is the Difference Between Unique Index vs Unique Constraint.http://www.jlcomp.demon.co.uk/faq/uk_idx_con.html
and
Difference Between Unique Index and bitmap index.The documentation is your friend:
http://download.oracle.com/docs/cd/B28359_01/server.111/b28318/schema.htm#CNCPT1157
http://download.oracle.com/docs/cd/B19306_01/server.102/b14220/schema.htm#sthref1008
Regards,
Rob.

Trust store and key store

What is the fundamental difference between trust store and key store ?

what this means to an end user ?I have no idea, but what it means to me is that JBoss don't understand the difference between them any more than you did when you asked the question.
A keystore is a high-security item that needs to be kept under lock and key as it contains credentials sufficient to identify that peer legally, and I mean in a courtroom in a dispute over millions of dollars. A truststore on the other hand is a collection of public certificates whose security requirement is to prevent people adding untrustworthy certificates to it. A completely different matter. In any large organization, the personnel with the authority over the keystore would never be the same as the personnel with authority over the truststore. Putting both in the same file compromises the security of both. It makes no sense whatsoever.

Any relation between indexes and high cardinality.............

HI,
what is difference b/w index and high cardinality?
and also difference b/w index and line item dimension?
Thanks

Hi,
High Cardinality:
Please Refer this link, especially the post from PB:
line item dimension and high cardinality?
Line Item Dimension:
Please go through this link from SAP help for line item dimension
http://help.sap.com/saphelp_nw04/helpdata/en/a7/d50f395fc8cb7fe10000000a11402f/content.htm
Also in this thread the topic has been discussed
Re: Line Item Dimension
BI Index:
There are two types of indexes in BW on Oracle, bitmap and b-tree
Bitmap indexes are created by default on each dimension column of a fact table
Setting the high cardinality flag for dimension usually affects query performance if the dimension is used in a query.
You can change the bitmap index on the fact table dimension column to a b-tree index by setting the high cardinality flag. For this purpose it is not necessary
to delete the data from the InfoCube
Refer:
Re: Bitmap vs BTree
How to create B-Tree and Bitmap index in SAP
Re: Cardinality
Line Item Dimesnion
Hope it helps...
Cheers,
Habeeb

Difference between primary eindex and secondary index?

hi experts
pls answer me
difference between primary eindex and secondary index?
rewads apply.
thanks.
naresh.

hi,
check this link.
http://help.sap.com/saphelp_47x200/helpdata/en/cf/21eb2d446011d189700000e8322d00/frameset.htm
A difference is made between Primary & Secondary indexes to a table. the primary index consists of the key fields of the table and a pointer to the non-keys-fields of the table. The Primary index is generated automatically when a table is created and is created in the datebase as the same times as the table. It is also possible to define further indexes to a table in the ABAP/4 dictionary, which are then referred to as Secondary indexes.
Always it is not mandatory that an index should have all the key fields of a table. To see the index of a table
goto SE11->specify table name->click on the indexes... button on the application toolbar.
Based on your requirement you can you any of those index fields in the where clause of your query. Always its a better practice to use the index fields in the order specified. While selecting the records from a table it is always better to select the fields in the same order as specified in the table.

Difference b/w index and key

Similar Messages

Maybe you are looking for