topic Pooled table M_VMVAD obsolete in Application Development and Automation Discussions

Pooled table M_VMVAD obsolete

Former Member — Mon, 17 Aug 2009 14:07:13 GMT

Hello,

After an upgrade from 4.6B to ECC6.0, the table M_VMVAD has become obsolete. SAP suggests that the view V_VMVAD be used instead. However, in our custom program we are updating the records in table M_VMVAD and so we cannot use the view V_VMVAD instead, since it is only possible to read a view which has more than one table (View V_VMVAD has two tables VBUK and VBAK in the join condition)

Any ideas how we can adapt our custom program to this change?

form abc using gt_caos like vbak.

tables: M_VMVAD.

delete from M_VMVAD

where vbeln = gt_caos-vbeln.

endform.

Thanks in advance.

Regards,

Reena

Re: Pooled table M_VMVAD obsolete

Former Member — Mon, 17 Aug 2009 14:37:51 GMT

Hello,

I didn't get your question exactly. what you actually did with the table M_VMVAD?

Obviously you can query a view without any hitches.This view is nothing but a subordinate of VBAK table with condition to filter and display only Blocked agreements.

If i understood correctly, your question is - you need to delete entries from View V_VMVAD .But for deletion, you cannot do it in the view.You can do it in base VBAK table so the changes will get reflected in this view V_VMVAD.

Cheers

Kothand

Re: Pooled table M_VMVAD obsolete

ThomasZloch — Mon, 17 Aug 2009 14:47:55 GMT

M_VMVAD sounds like a matchcode table for object "VMVA" and ID "D". This has probably been replaced by a search help in 6.0, as matchcodes are obsolete.

Maybe the whole process is obsolete anyway, check in that direction.

Never delete entries in VBAK or VBUK or any SAP standard table directly via an ABAP program.

Thomas