SAP Vendor Master Report: Vendor Master Purchasing 360

What this report answers

PostNow.ai's Vendor Master Purchasing 360 (MM-02) lays the general, purchasing-org and company-code views of each vendor side by side. It is the extract for master data reviews, audits and pre-migration cleansing:

• Which vendors are centrally blocked for posting or flagged for deletion, and which have a payment block in a company code?
• Do the payment terms in purchasing, which default into the PO, match the company-code terms used for FI postings without a PO?
• Which vendors are set up for GR-based invoice verification, or allow automatic PO creation?
• Which vendors have no VAT registration number, an unexpected account group, or a reconciliation account that does not fit their type?

Columns cover vendor number, name, city, country, VAT number, account group, central block and deletion flag from the general data; purchasing org, order currency, payment terms, Incoterms, GR-based invoice verification and automatic PO from purchasing; company code, reconciliation account, payment terms, payment methods and payment block from the company code; plus purchasing org, company and country names.

XK03, MK03 and FK03: the SAP standard way, and where it stops

PostNow.ai replaces the one-vendor-at-a-time route. XK03 displays a vendor centrally, MK03 the purchasing view and FK03 the accounting view. S_ALR_87012086 gives a vendor list and S_ALR_87012089 shows changes to vendors; XK04 shows a vendor's changes centrally, and the change documents behind them sit in CDHDR and CDPOS under object class KRED. Blocking is XK05 (central) or MK05 (purchasing).

On S/4HANA, vendor maintenance moved to the Business Partner: XK, MK and FK transactions redirect to BP (the Business Partner Approach simplification item, SAP Note 2265093), and the Fiori app Manage Supplier Master Data offers a lighter screen. None of these puts purchasing-org and company-code settings for hundreds of vendors in one sheet, which is what a terms or block review needs.

SAP tables behind it: LFA1, LFM1 and LFB1

PostNow.ai's MM-02 starts from LFA1 and joins LFM1 and LFB1 on the vendor number, then T024E for purchasing org names, T001 for company names and T005T for country names.

• LFA1, general data. Name, address, country, VAT number STCEG, account group KTOKK, central posting block SPERR, central purchasing block SPERM, central payment block SPERZ and central deletion flag LOEVM.
• LFM1, purchasing org data. Order currency WAERS, payment terms ZTERM, Incoterms INCO1, GR-based invoice verification WEBRE, automatic PO KZAUT, plus a purchasing block SPERM and deletion flag LOEVM at that level. LFM2 goes one level lower, to plant or vendor sub-range.
• LFB1, company code data. Reconciliation account AKONT, payment terms ZTERM, payment methods ZWELS, payment block ZAHLS, posting block SPERR and deletion flag LOEVM.
• On S/4HANA the Business Partner is the leading object, and LFA1 and LFB1 are still filled through customer/vendor integration (CVI), so the extract reads the same tables.

Checks to run on a vendor master extract

1. Rows multiply. A vendor with two purchasing orgs and three company codes comes back as six rows. Count vendors as distinct numbers, and compare terms within each purchasing org and company code pair.
2. Know which block you are looking at. Central Block is LFA1-SPERR, the central posting block. It is not the purchasing block (SPERM) or the central payment block (SPERZ); Payment Block in the extract is the company-code ZAHLS. For a “can we still order from them” review, have a designer add SPERM.
3. Two sets of payment terms. Payment Terms comes from LFM1 and goes into the PO; CoCd Pay Terms comes from LFB1 and applies to invoices posted without a PO. Flag every vendor where they differ and decide which one is right.
4. Deletion flags live at three levels. The delivered Deletion Flag is the central one. A vendor can be flagged in one company code or purchasing org only, through LFB1-LOEVM or LFM1-LOEVM.
5. New and changed vendors. Filter on Created On for vendors added since the last review, then look at the KRED change documents for the ones whose bank or terms changed.

How PostNow.ai runs it

In PostNow.ai you run Vendor Master Purchasing 360 from the Report Library in the Excel add-in and narrow it with SAP value help on vendor, purchasing org, company code, account group, country, central block, deletion flag and created on. The rows land read-only from your own SAP session with organisation and country names in place of codes, so the sheet is ready for a review. Share it to Team Reports and procurement and AP review the same extract. To see the orders placed with a vendor, run Purchase Order 360; for what you still owe them, AP Open Items + Aging. When the review finds terms or blocks to correct, SAP mass change from Excel covers updating existing records, and the XK01 vendor master upload guide covers creating suppliers and extending them to a new company code or purchasing org.