Sort index and Matching Rules

[former_member189669]

Hi,

In a matching rule, a look up field 'Country' is used. Field Country will look up values from Country lookup table [Flat table].

It is known that Sort index has to be enabled for a field that is used in Matching rule.

Please advise which of the below option suits the best to achieve optimal matching performance :

1. Sort index enabled for Countries look up field in Main table.

2. Sort index to be enabled for Country code in countries lookup table. Country code is a DF and main table record (say Vendor) fetches country code for its country field.

3. Enable sort index at both the places - Country code in Countries lookup table and Country (lookup field) in maintable.

Links or readables relavant to this will be of great help.

Thanks.

Vinay

[Former Member · Accepted solution]

You only need to enable the sort index on the Country field on the main table. There won't be any performance advantage to enabling the sort index for the code within the lookup table as matching strategies are restricted to the scope of the table by which they are defined.

However, that is an interesting question! In general I think it's a good practice to limit the number of fields that have a sort index as it can create quite a toll on the import server.

[former_member189669 · Accepted solution]

Hi Harrison,

Noted. Thanks.

Best practice to achieve optimal performance also states that in all the look up tables (includes Qualified), sort index for DF must be set to Normal.

Ref:SAP Note 1258982 ; Read 'Please Note' which states the above .

Please put your thoughts on this.

Reards,

Vinay

[Former Member · Accepted solution]

Yes, this is true. If you think about it, when you build an import map you specify which fields to match on. The server has to match on values from lookup tables so naturally you would want sort indexes built for your primary key.