MK03 — MK03 — Display Vendor Purchasing Data (ECC; redirects to BP in S/4HANA)

MK03 displays vendor master data limited to the general data view and the purchasing organization view. It shares the same underlying tables as XK03 but deliberately hides the company code (accounting) view, so fields like payment terms, house bank, or reconciliation account are never shown here even if they exist for the vendor. The one fact that explains most confusion: MK03 is not a smaller vendor, it is a smaller window onto the same vendor. A vendor can look completely fine in MK03 and still be unusable for invoice posting because the company code extension is missing or blocked, and MK03 will never surface that.

Reached for whenever a purchasing issue needs vendor confirmation without touching accounting data: checking why a purchase order defaults a wrong incoterm or currency, confirming a vendor is extended to the purchasing organization used on a PO, checking a purchasing block, or verifying the schema group that drives pricing procedure determination. Purchasing consultants without FI authorization use MK03 instead of XK03 for exactly this reason. Fiori equivalents exist for vendor master display in newer stacks, but many P2P teams still default to MK03 because it opens fast and shows only what a purchasing analyst needs, without company code noise.

To confirm a vendor is genuinely extended and open at a given purchasing organization, query LFM1 filtered on the vendor number (LIFNR) and purchasing organization (EKORG), and check the block field for that combination rather than relying on LFA1's central block, which only reflects a global lock. Cross-check LFA1 on the same LIFNR for the central deletion flag and central block flag. If the vendor is missing entirely from LFM1 for the purchasing org in question, that purchasing organization extension was never created, which is a data setup problem, not a MK03 display problem.

SAP's current S/4HANA simplification guidance includes MK03 among the classic vendor transactions redirected to BP. The purchasing-versus-company-code distinction still exists conceptually inside supplier roles, but MK03 should not be described as a separate native S/4HANA vendor-master UI.

Functional MM or procurement master data team owns vendor purchasing data and purchasing organization extensions. FI or vendor accounting team owns anything in the company code view, which is out of scope for MK03. A clean handover states the vendor number, the purchasing organization involved, and whether the issue is a missing extension, a block, or an authorization restriction, with the relevant LFM1 or LFA1 field values attached.

MK01 and MK02 are the create and change counterparts and the natural next stop when MK03 reveals a missing or blocked purchasing organization extension. ME11, ME12, and ME13 cover purchasing info records, which depend on the vendor being properly extended and unblocked at the purchasing organization level that MK03 exposes. Reviewing these together clarifies whether a PO or pricing problem originates in vendor master data or downstream in the info record or contract layer.