VD52 — Change Customer-Material Info Record

VD52 maintains an existing customer-material info record, the object that stores customer-specific overrides for a single material sold to a single customer within one sales organization and distribution channel. Typical fields are the customer's own material number (printed on outbound documents), delivery priority, minimum delivery quantity, over- and underdelivery tolerance percentages, partial delivery indicator, and a default plant. The structural fact that explains most confusion: the record key is VKORG plus VTWEG plus KUNNR plus MATNR, not just customer and material. A record maintained for one sales organization or distribution channel is invisible to an order created in another, even for the identical customer and material, and VD52 will simply report that no record exists rather than offer to create one.

Reached for after go-live when a customer requests a permanent exception to standard shipping tolerances, wants their own part number to appear on the order confirmation or invoice, or needs a fixed delivery priority for expedited handling. It sits between customer master maintenance and sales order entry in the process: the customer master (VD01 to VD03) governs whether the customer exists in a sales area at all, and the customer-material info record refines behavior for one specific material within that area. Consultants use VD52 for one-off or low-volume changes; for mass updates across many customer-material combinations, a batch input program, LSMW, or a direct BAPI call is the practical route instead of manually stepping through the transaction record by record.

Pull table KNMT via SE16N filtering on KUNNR, MATNR, VKORG, and VTWEG for the exact combination the complaint references. Confirm a row exists for that precise sales area; if it does not, the order will fall back to material master values and any VD52 change made against a different sales organization or distribution channel is irrelevant to the order in question. If a row exists, compare its tolerance and priority fields directly against what appears on the sales order line to isolate whether the info record or a later override (pricing, shipping point determination) is responsible.

The underlying table KNMT and the maintenance logic are unchanged on S/4HANA; VD52 remains available and behaves the same way as on ECC. A Fiori app covering customer-material info record maintenance may exist in some releases, but its exact identifier is not confirmed here and should be verified against the specific system before being cited to a customer as the standard path.

Functional SD master data ownership, typically the order management or customer master data team. A handover to that owner should include the exact sales organization, distribution channel, customer, and material involved, the KNMT field values before and after, and whether the affected order was created before or after the change, since existing orders do not retroactively pick up new info record values.

VD51 is the create counterpart and the first stop when VD52 reports no record exists. VD01, VD02, and VD03 govern whether the customer is extended to the sales area at all, which is the prerequisite check before assuming the info record itself is faulty. VA21 and similar order-entry-adjacent transactions are where the customer-material info record's values are actually consumed, useful for confirming whether a discrepancy originates in master data or in order processing logic.