Hi MoazzaM:
Thanks for your input. I agree, I don't think a ztable will be necessary. KNMT should work fine as long as a new zfield could be added -- like KNVV-KVRG1 for example which would be assigned to a group of customers sharing the same C-M Info Record set.
Two advantages:
One, when a new customer joins the club, their KNVV-KVGR1 could be assigned so that magically the entire C-M Info Record set would apply to their orders.
Secondly, there are frequently changes to be made to Info Records shared by all customers in the group. Now the change can be made once, as opposed to currently, where it is necessary to manually run WIN Shuttle to update each KUNNR via VD52.
The trick here would be to get KNMT to accept an assignment of KVGR1/MATNR as opposed to KUNNR/MATNR. Can the table functionality be thusly easily changed? Or is it easier to simply create it fresh as a ztable?