Skip to content
IT Canvass
SAP tables · Lesson

LFA1

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.

  • LFM1, vendor purchasing data.
  • LFB1, vendor company-code data.
  • BUT000, Business Partner general data.
  • ADRC, addresses.

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.

Want to learn this properly?

Our live, instructor-led SAP Training covers this hands-on, with real projects and a certification path.

Check your understanding

  1. Which statement is true of LFA1?

    • A. As a database, SAP HANA is a full, ACID-compliant relational database with standard SQL plus advanced…
    • B. These CDS examples show Core Data Services views, the modern SAP modeling layer, with joins, associations…
    • C. View its structure in SE11 and its data (with authorization) in SE16N.
    Show answer

    C. View its structure in SE11 and its data (with authorization) in SE16N.

    Covered in the “Working with it” section of this lesson.

  2. Which of these also applies to LFA1?

    • A. LIFNR, vendor number (key).
    • B. Treating one-line definitions as complete.
    • C. Thinking of ERP as separate apps, its value is the integration.
    Show answer

    A. LIFNR, vendor number (key).

    Covered in the “Key fields” section of this lesson.

  3. Which part of the Learn SAP curriculum covers LFA1?

    • A. SAP projects
    • B. SAP tables
    • C. SAP best practices
    Show answer

    B. SAP tables

    This lesson sits in the SAP tables section of the Learn SAP course.

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.
CallWhatsAppEnquire