Skip to content
IT Canvass
SAP tables · Lesson

KNA1

Quick answer

KNA1 remains the general customer table, but in S/4HANA you maintain customers as Business Partners (BUT000 and related), which update KNA1/KNVV/KNB1 behind the scenes.

Key takeaways

  • KUNNR, customer number (key).
  • NAME1, name; ORT01, city; LAND1, country.
  • KNVV, customer sales data.
  • Watch out: Reading tables directly instead of using CDS/reports where appropriate.

What it stores

It stores general customer master data, the client-level attributes of a customer common across sales areas and company codes. (In S/4HANA, customers are Business Partners, with KNA1 updated via CVI.)

Key fields

  • KUNNR, customer number (key).
  • NAME1, name; ORT01, city; LAND1, country.
  • KTOKD, account group.
  • STCEG, VAT registration number.

Keys and relationships

KUNNR is the key. KNA1 holds general data; sales-area data is in KNVV, and company-code (accounting) data in KNB1. In S/4HANA these are maintained via the Business Partner and kept in sync by Customer-Vendor Integration.

  • KNVV, customer sales data.
  • KNB1, customer company-code data.
  • BUT000, Business Partner general data.
  • ADRC, addresses.

Working with it

KNA1 remains the general customer table, but in S/4HANA you maintain customers as Business Partners (BUT000 and related), which update KNA1/KNVV/KNB1 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 KNA1?

    • A. View its structure in SE11 and its data (with authorization) in SE16N.
    • B. An IDoc (Intermediate Document) is SAP’s standard structured document format for exchanging business data…
    • C. The SAP GUI is the classic desktop interface for navigating SAP.
    Show answer

    A. 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 KNA1?

    • A. Over-granting backend authorizations.
    • B. Ignoring annotations that unlock OData/analytics.
    • C. KTOKD, account group.
    Show answer

    C. KTOKD, account group.

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

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

    • A. SAP interview questions
    • B. SAP tables
    • C. SAP Fiori
    Show answer

    B. SAP tables

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

Frequently asked questions

What does KNA1 stand for in SAP?

KNA1 is a key SAP table in SD/FI. It stores general customer master data, the client-level attributes of a customer common across sales areas and company codes. (In S/4HANA, customers are Business Partners, with KNA1 updated via CVI.)

Which fields matter most in KNA1?

KNA1 remains the general customer table, but in S/4HANA you maintain customers as Business Partners (BUT000 and related), which update KNA1/KNVV/KNB1 behind the scenes.

What else is worth knowing about KNA1?

KUNNR, customer number (key). NAME1, name; ORT01, city; LAND1, country. KTOKD, account group.

What tends to go wrong with KNA1?

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