SAP 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.)
LFA1 is the general vendor table, keyed on LIFNR, holding client-level supplier data such as NAME1, ORT01, LAND1, the KTOKK account group and the STCEG VAT number. Purchasing-organisation data sits in LFM1 and company-code data in LFB1. In S/4HANA you maintain vendors as Business Partners in the supplier role, and CVI keeps LFA1, LFM1 and LFB1 in step.
- LIFNR, vendor number (key).
- NAME1, name; ORT01, city; LAND1, country.
- LFM1, vendor purchasing data.
- Watch out: LFA1 is general data, and purchasing organisation data lives in LFM1; both are needed to order.
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.