KNMT table — Customer Material Info Record Table

Each row in KNMT represents an agreement between one customer and one material, scoped to a specific sales organization and distribution channel, that overrides certain defaults from the material master or customer master when that customer orders that material. The most commonly used piece of data is the customer's own material number (their part number, not SAP's), which prints on order confirmations and delivery documents so the customer recognizes what they ordered. The table also carries delivery tolerance percentages and partial delivery limits specific to that customer-material pair. It does not drive pricing, does not drive availability, and does not exist for every material a customer buys — absence of a row is normal and simply means standard defaults apply.

KNMT is client-dependent; always restrict on MANDT implicitly through the standard client context. The full key is KUNNR, MATNR, VKORG, VTWEG, so a lookup with only KUNNR or only MATNR returns every sales area combination for that customer or material, which is rarely what is needed. For a single-order investigation, select on KUNNR and MATNR together first, then narrow to VKORG and VTWEG if multiple rows come back. The table is small relative to transactional tables like VBAP, so a scan by KUNNR alone is usually fine, but a scan by MATNR alone across all customers can return an unhelpfully long list on a widely-sold material.

Symptom: the delivery note or order confirmation shows the wrong customer part number, or the customer complains their part number is missing entirely. Select KNMT with KUNNR equal to the sold-to, MATNR equal to the material in question, and VKORG/VTWEG matching the sales area of the order. Compare KDMAT against what the customer actually expects. If no row exists, the order used the SAP material number by default, which is expected behavior, not a data error.

KNMT continues to exist as a transparent table in S/4HANA and its structure has not been restructured the way partner or condition tables were. The maintenance transactions used in ECC for customer-material info records remain available, and a Fiori app for managing these records exists on newer S/4HANA releases, though the exact app identifier should be confirmed against the specific release rather than assumed. There is no known compatibility view that fully replaces direct table access for reporting purposes.

Data quality on KNMT belongs to the SD master data or customer service team that maintains customer-facing agreements, since the customer's own part number and tolerance overrides are commercial terms, not system configuration. Order-to-cash functional consultants get pulled in only when the wrong value is flowing into an order or delivery document and the root cause needs tracing back to this table versus the material or customer master.

KNA1 and KNVV provide the general and sales-area customer master data that KNMT sits alongside. VBAP is where the customer material number surfaces at the order line item once picked up from KNMT. Maintenance of customer-material info records is typically done through dedicated customer-material master transactions or the corresponding Fiori app, kept separate from general customer master maintenance transactions.