Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Replacement for table M_VMVMD (nonexistent) in ECC6

Hi !

I'm doing an Upgrade of 4.6c to ECC6, but the Function Pool SAPLZPLPLN2_V55K

required the table M_VMVMD, which is nonexistent in ECC6.

Please, I need to know what is the replacemente for this table (M_VMVMD) in ECC6.

Thank you very much.

Very grateful.

Fabio Rodriguez

Former Member


This table is now obsolete. You can find more explanation in SAP note

1093055, as well our explanation below for the situation you found in

your new ECC6.0:

As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), this function is no

longer available. The previous tables for the matchcode pools for

deliveries will be replaced by new transparent tables and views. The

transparent tables are automatically updated during normal delivery


The following relationship exists between matchcode tables and the new

tables or views:

Matchcode Tab. New Object Type Contents

Outbound Deliveries

M_VMVLA SHP_IDX_GDSI Table Outbound deliveries: Not posted for GI

M_VMVLB SHP_IDX_PICK Table Outbound deliveries: Not picked

M_VMVLC SHP_IDX_GDSI Table Outbound deliveries: Not posted for GI

M_VMVLD SHP_IDX_CREDTable Outbound deliveries: After credit checks

M_VMVLI SHP_IDX_EXOB Table Outbound deliveries: External identification

Inbound Deliveries

M_VMVMA SHP_IDX_EXIB Table Inbound deliveries: Initiating document

M_VMVMB SHP_VIEW_TRAI View Inbound deliveries: Shipment identification

M_VMVMC SHP_VIEW_BOLN View Inbound deliveries: Tracking number

M_VMVMD SHP_IDX_EXIB Table Inbound deliveries: External identification

M_VMVME SHP_IDX_GDRC Table Inbound deliveries: Not posted for GR

M_VMVMF SHP_IDX_PUTATable Inbound deliveries: Not putaway Rough GR

M_VMVG SHP_IDX_ROGR Table Rough goods receipts for vendor

The matchcode objects VMVL (outbound deliveries), VMVM (inbound

deliveries), and VMVG (rough goods receipts) are deleted after the data

transfer during the upgrade, along with the corresponding objects

(matchcode IDs, matchcode tables). You should therefore check your

programs to see if any of these objects are used, and should replace

these according to the above procedure. Because the new tables and views

contain at least the same fields as the previous tables, for programs,

you normally only need to adjust the SELECT links to matchcode tables

and the data definition of the target table or target structure for

these links.

Since you change some search helps, any modifications to the matchcode

objects are lost during the upgrade.

Effects on System Administration

You can use the RLE_SHP_IDX_TABLE_MAINTAIN report to analyze the data

status in the index tables, and to correct it where necessary.



0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question