Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Index...

Former Member
0 Likes
826

is it recommended that while creating Seconday Index on a table that we shud consider MANDT in it also...

ur views....

8 REPLIES 8
Read only

Former Member
0 Likes
799

Hi Abhishek,

1. No

Primary index takes care of that. (Mandt)

2. The fields which are commonly used

in our SQL queries

for filtering the data :

Such fields are the target

for secondary indexes.

(Such fields may not be a part of the

primary key of that table)

I hope it helps.

Regards,

Amit M.

Message was edited by: Amit Mittal

Read only

abdul_hakim
Active Contributor
0 Likes
799

Hi,

No Not required because when u define a primary key then u should select MANDT as well since u cannot have a key field in between non key field.

Finally it is not at all requried.

Enjoy!!

REgards,

Abdul

Read only

Former Member
0 Likes
799

Abhishek Suppal

No need to consider the MANDT.

Just collect the fields to be in Sec Index and create it.

Thanks

Kam

Read only

Former Member
0 Likes
799

Not required..

try to create secondary index with out considering MANDT.

regards

vijay

Read only

Former Member
0 Likes
799

thanx but if MANDT is consider in some index will it effect some performance.....

Read only

Former Member
0 Likes
799

Hi again,

1. Yes

If MANDT is considered in secondary index again,

it will affect performance a little.

But not to worry about it.

Regards,

Amit M.

Read only

Former Member
0 Likes
799

Hi,

1. Pls award points if any reply(s) are useful.

Regards,

Amit M.

Read only

Peranandam
Contributor
0 Likes
799

its better to keep MANDT field in secondary index. because while accessing table data across client table data will not be sorted if you are not maitained MANDT field in secondary index.