SAP Note 23718 - Generation of an incorrect matchcode

Symptom:

After an information structure generation, the required matchcode is not created on the selection screen of the respective standard analysis. Instead, a different matchcode is generated. For example, in some cases, the matchcode for quotations is processed instead of the matchcode for orders, if the sales order number is a characteristic of the information structure.

Other terms

Matchcode, info structure, F4, input help, search help, standard analysis

Reason and Prerequisites

The matchcode object is not always unique, a dialog to choose the required matchcode object is not supported.

Solution
You can force the required matchcode object by the following modification in the module for determining the matchcode object. Please note that this matchcode object then becomes effective for all information structure fields with this check table (in the above example VBAK). That is, in the example, the matchcode is also processed for orders, if quotations are meant.
Insert an entry in the include LV12BU02 in the CASE query:
CONDENSE TAB_FELD NO-GAPS.
CASE TAB_FELD.
WHEN 'XXXXYYYYY'. "<------ new
MATCHCODE_FOUND = 'X'. "<------ new
MCD_MATCHCODE = 'ZZZZ'. "<------ new
WHEN 'MARAMATNR'.
MATCHCODE_FOUND = 'X'.
MCD_MATCHCODE = 'MAT1'.
WHEN 'KNA1KUNNR'.
MATCHCODE_FOUND = 'X'.
MCD_MATCHCODE = 'DEBI'.
WHEN 'MCHACHARG'.
MATCHCODE_FOUND = 'X'.
MCD_MATCHCODE = 'MCH1'.
WHEN 'MCH1CHARG'.
MATCHCODE_FOUND = 'X'.
MCD_MATCHCODE = 'MCH1'.
WHEN 'LFA1LIFNR'.
MATCHCODE_FOUND = 'X'.
MCD_MATCHCODE = 'KRED'.
WHEN OTHERS.
* MC-Datei finden
SELECT * FROM DD27S
Where: 'XXXX' is the name of the check table (example: VBAK)
'YYYYY' is the name of the check table field against which the checks are run (example: VBELN)
'ZZZZ' is the name of the matchcode object which should be forced (example: VMVA)
Generate program SAPLV12B.
Regenerate the standard analyses and planning screens using the report RMCSISGE (or RMCSISGN).