How To Fix MC236 - Aún no existe ning.índice apropiado para ID matchcode &-& (-> txt.expl.)

SAP Error Message - Details

• Message type: E = Error

• Message class: MC - Aggregate: views, matchcodes, lock objects

• Message number: 236

• Message text: Aún no existe ning.índice apropiado para ID matchcode &-& (-> txt.expl.)

¿Qué causa este problema?

When activating a transparent matchcode ID (update type = 'I'), there
is a check for a likely database index for this matchcode ID. Such a
database index is generally necessary in order to support the matchcode
search for a typical selection for this matchcode. The absence of such
a database index could cause considerable performance problems during
matchcode selection.
The system assumes that the first field in the matchcode definition
(for client-specific matchcodes the first field after the client field)
is the relevant search field for this matchcode, i.e. that the end user
will limit this field in the matchcode search by entering a selection
value. A likely database index is therefore an index which contains the
relevant matchcode search field (possibly following a client field).

Respuesta del sistema

The system has now found that there is no likely database index for a
transparent matchcode ID.

¿Cómo arreglar este error?

If the matchcode view on the database (possibly taking a selection
condition into consideration) contains less than 1000 data records, it
is not necessary to create an index.
If there are considerably more than 1000 records in the matchcode view
on the database, you should create an index. This index should begin
with the fields to be searched for with equality (client, language, or
all the fields for which the 'Get Parameter' flag is set, i.e. the flag
GP of the Maintain Matchcode ID (Fields) screen). This is especially
true if they are used in the primary index. This is important in order
to ensure that the created secondary index is better than the primary
index from the point of view of the database optimizer).
The index thus has the following structure:
Client field if the table is client-specific
Fields for which the 'Get Parameter' flag is set, should any exist
Field used in the search
This index structure, however, does not always ensure that the index
created is also used by the subordinate DBMS for data selection (this
depends on the DBMS optimizer used). You can check this as follows:
Open a second session and select <LS>System -> Utilities -> SQL Trace
</>. Press the pushbutton <LS>Trace on</>. Make a search entry in the
first session and send it. Then press the pushbutton <LS>Trace off</>
in the second session and press the pushbutton <LS>List trace</>.
Search for statements in which the matchcode view M_<MC object name>
<Matchcode ID> is used and display further information about it with
the function <LS>Explain one SQL Request</>. You will find out here
which index was used.

Extracto de mensaje de error del sistema SAP. Copyright SAP SE.