SAP Reference

MK02

Change S/4HANA status: Replaced

Change Vendor (Purchasing)

Module: MM · Materials Management S/4HANA replacement: BP
Notes

Vendor master maintenance is consolidated into the Business Partner transaction (BP) via Customer/Vendor Integration (CVI) in S/4HANA.

What the badges mean
S/4HANA status: Active
Active and unchanged in S/4HANA.
S/4HANA status: Deprecated
Still readable today, but no longer SAP's strategic path — plan around it.
S/4HANA status: Replaced
Replaced by a new persistence in S/4HANA; the classic name may still answer reads (see read mechanism).
S/4HANA status: Migrating to IBP
Planning scope is moving from APO toward IBP.
S/4HANA status: Active (StRM) · Replaced (EWM)
Path-dependent: active with SAP Stock Room Management, replaced where EWM is the warehouse path.
S/4HANA status: Replaced · Compat View
Compatibility view: the classic table name is redirected to a view over the new persistence — see how the physical model moved.
S/4HANA status: Active · Proxy View
Proxy view: reads route through NSDM proxy/CDS views — see how the physical model moved.
master
Data class: what the table holds — master data, transaction documents, org structure, config, or texts (one row per language — see the quirks guide).
In field listings, K marks a primary-key field, and linked type codes in the Type column jump to the matching quirks-guide section.

Boilerplate SQL

Databricks SQL

Starting point for querying the tables behind this transaction. Set your Unity Catalog location and filter values below — they’re substituted into the SQL and the copy button.

Query parameters

5 parameters not filled: <catalog>, <schema>, <MANDT>, <LIFNR>, <BUKRS>

-- ============================================================
-- T-Code : MK02 Change Vendor (Purchasing)
-- Purpose: Change vendor master from a purchasing perspective
-- Grain  : One row per vendor / company code (one if LFB1 not joined)
-- Tables : LFA1, LFB1, T001
-- Notes  : LFA1 is client-level (general data). LFB1 adds company-code-specific accounting data. Outer join to LFB1 so client-only vendors still appear.
-- ============================================================
SELECT
  -- Keys
  v.MANDT   AS "Client",
  v.LIFNR   AS "Vendor",
  fb.BUKRS  AS "Company Code",

  -- Descriptive text
  v.NAME1   AS "Vendor Name",
  v.NAME2   AS "Vendor Name 2",

  -- Dates
  v.ERDAT   AS "Created On",
  v.UPDAT   AS "Changed On",

  -- Status / indicators
  v.LOEVM   AS "Central Deletion Flag",
  v.SPERR   AS "Central Posting Block",
  fb.LOEVM  AS "Deletion Flag (Co.Code)",
  fb.SPERR  AS "Posting Block (Co.Code)",

  -- Org fields
  v.ORT01   AS "City",
  v.PSTLZ   AS "Postal Code",
  v.LAND1   AS "Country",
  v.REGIO   AS "Region",
  v.TELF1   AS "Telephone",
  v.STCEG   AS "VAT Registration Number",
  cc.BUTXT  AS "Company Code Name",

  -- Master data enrichment
  v.KTOKK   AS "Vendor Account Group",
  fb.AKONT  AS "Reconciliation Account",
  fb.ZTERM  AS "Terms of Payment",
  fb.ZWELS  AS "Payment Methods",
  fb.ZAHLS  AS "Payment Block"
FROM <catalog>.<schema>.lfa1 v
LEFT JOIN <catalog>.<schema>.lfb1 fb
  ON  fb.MANDT = v.MANDT
  AND fb.LIFNR = v.LIFNR
LEFT JOIN <catalog>.<schema>.t001 cc
  ON  cc.MANDT = fb.MANDT
  AND cc.BUKRS = fb.BUKRS
WHERE
  v.MANDT = '<MANDT>'
  AND v.LIFNR = '<LIFNR>'
  -- AND fb.BUKRS = '<BUKRS>'
  -- AND v.LOEVM <> 'X'
ORDER BY v.LIFNR, fb.BUKRS;

Tables Used by This Transaction

R read · W write · R/W read + write

More Materials Management t-codes