IT CanvassTalk to an advisor
SAP tables · LessonBy , SAP Trainer, 10 yrs · Published · SAP S/4HANA 2023 · all levels

LFA1

LFA1 is a key SAP table in MM/FI. It stores general vendor (supplier) master data, the client-level attributes of a vendor common across purchasing organizations and company codes. (In S/4HANA, vendors are Business Partners, with LFA1 updated via CVI.)

Quick answer

LFA1 remains the general vendor table, but in S/4HANA you maintain vendors as Business Partners (supplier role), which update LFA1/LFM1/LFB1 behind the scenes.

Key takeaways
  • LIFNR, vendor number (key).
  • NAME1, name; ORT01, city; LAND1, country.
  • LFM1, vendor purchasing data.
  • Watch out: Reading tables directly instead of using CDS/reports where appropriate.

What it stores

It stores general vendor (supplier) master data, the client-level attributes of a vendor common across purchasing organizations and company codes. (In S/4HANA, vendors are Business Partners, with LFA1 updated via CVI.)

Key fields

  • LIFNR, vendor number (key).
  • NAME1, name; ORT01, city; LAND1, country.
  • KTOKK, account group.
  • STCEG, VAT registration number.

Keys and relationships

LIFNR is the key. LFA1 holds general data; purchasing-org data is in LFM1, and company-code (accounting) data in LFB1. In S/4HANA these are maintained via the Business Partner and kept in sync by CVI.

Working with it

LFA1 remains the general vendor table, but in S/4HANA you maintain vendors as Business Partners (supplier role), which update LFA1/LFM1/LFB1 behind the scenes. View its structure in SE11 and its data (with authorization) in SE16N.

Common pitfalls

  • Reading tables directly instead of using CDS/reports where appropriate.
  • Ignoring header/item relationships.
  • Performance: querying large tables without indexed selection.

Practice challenge

+0 XPStreak ×0
Question 1 of 3
Which statement is true of LFA1?

Frequently asked questions

What does LFA1 stand for in SAP?
LFA1 is a key SAP table in MM/FI. It stores general vendor (supplier) master data, the client-level attributes of a vendor common across purchasing organizations and company codes. (In S/4HANA, vendors are Business Partners, with LFA1 updated via CVI.)
Which fields matter most in LFA1?
LFA1 remains the general vendor table, but in S/4HANA you maintain vendors as Business Partners (supplier role), which update LFA1/LFM1/LFB1 behind the scenes.
What is the practical takeaway on LFA1?
LIFNR, vendor number (key). NAME1, name; ORT01, city; LAND1, country. KTOKK, account group.
What tends to go wrong with LFA1?
Reading tables directly instead of using CDS/reports where appropriate. Ignoring header/item relationships. Performance: querying large tables without indexed selection.
Already working on SAP and stuck on a live ticket?Get an expert SAP developer on screen-share to finish your daily tasks with you. Deliver on time, protect your reputation and your job. Monthly support only, no task-wise plans.Task assigned · no idea where to startStill stuck · your job on the lineExpert joins your screenDelivered on timeExplore On Job Support