SAP Note 23810 - Matchcode object VMSK

Symptom:

When the system makes an INSERT in table VBSK, the system log entry occurs because an UPDATE should be carried out for matchcode object VMSK from the database interface.

Cause and prerequisites

The matchcode object VMSK is obsolete and could not be deleted by the transport system. In Release 3.0/3.1, it is used neither in the programs nor in the screens for input help.

Solution

Deactivate the matchcode object by changing all the IDs of the matchcode object to the asynchronous update type 'A'.Proceed as follows:

1. Call the transaction to maintain the Data Dictionary (SE11).

2. Enter VMSK as the object name, select sub-object 'Matchcode object' and choose 'Display'.

3. Select 'Goto--> Matchcode IDs', and select ID A or B on the dialog box.

4. Call the change mode and change the update type from 'S' to 'A'.

5. Activate the matchcode ID at the end of your changes.

6. Execute steps 1-5 for both matchcode IDs A and B.

After the change to asynchronous update, the matchcode tables M_VMSKA and M_VMSKB are only supplied in case of an explicit generation via report SAPMACO.Since however the matchcode tables are not needed anywhere in the R/3 System, you can omit this, this virtually deactivates the matchcode.
To ease the workload of the database, you can also completely delete the contents of the matchcode tables. Use report SAPMACO to do this - with the option 'DEL'.

Note 21046 contains information on the F4 help in Transaction VG02 for field 'Group number'.