Solution : https://service.sap.com/sap/support/notes/432010 (SAP Service marketplace login required)
Summary :
This SAP Note addresses issues arising from the selection mechanism in combined use of KNVK and other customer master tables, which causes malfunction due to programmatic design. Specifically, the problem stems from the KUNNR field not being a key field in the KNVK table. As a remedy, a new database view, MASSKNVK, will allow KUNNR to act as an additional key field. The solution outlines steps for creating this view in SAP environments prior to Release 4.6C, and adjustment procedures to support mass maintenance within the system. Key operations include changes in SE11, SE16, and function module adjustments to integrate the new data structure.
Key words :
mass maintance includes database view massknvk, transaction se16 -> table entry -> transport entriesafter, rename parameter' -> select 'rename', create database view massknvk, create database view masskvnk, additional key words mass, select button 'table fields', customer master contact partner, view field table field, database view massknvk
Related Notes :
| 367670 | Customer master KNA1: you cannot change table KNVK |
| 216596 | Include additional fields in mass maintenance |