---
description: It offers the exhaustive list of various tables on FI module, the list consists of topics like Master Data, Accounting documents, Payment run
title: "SAP FI Important TABLES: Must Know!"
image: https://www.guru99.com/images/sap-fi-important-tables.png
---

[Skip to content](#main)

**⚡ Smart Summary**

SAP FI tables store the master data, accounting documents, and configuration that drive Financial Accounting, organized into master, transaction, and customizing groups that S/4HANA now consolidates into the Universal Journal table ACDOCA.

- 🔘 **Master data:** Tables such as SKA1, KNA1, and LFA1 hold general ledger, customer, and vendor master records.
- 📄 **Transaction data:** BKPF stores document headers while BSEG stores the accounting line items behind every posting.
- 🗂️ **Secondary indexes:** BSID, BSIK, and BSIS track open items, and BSAD, BSAK, and BSAS track cleared items.
- ⚙️ **Customizing:** Configuration tables like T001, T003, and T004 define company codes, document types, and charts of accounts.
- 🔎 **Data access:** Transactions SE16, SE16N, and SE16H display the contents of any table without writing code.
- 🤖 **S/4HANA:** The Universal Journal table ACDOCA replaces many index tables and feeds real-time, AI-assisted reporting.

Read More

![SAP FI important tables grouped by master data, transaction, and customizing](https://www.guru99.com/images/sap-fi-important-tables.png)

Financial Accounting in SAP stores every balance, document, and configuration setting inside database tables, so knowing the important tables in the SAP FI module helps you read data with SE16, build reports, and trace postings from end to end. This reference groups the key [SAP FI](https://www.guru99.com/sap-fi-tutorial.html) tables by purpose — master data, transaction data, payment runs, and customizing — and explains how they fit together in both SAP ERP and SAP S/4HANA.

## SAP FI Master Data Tables

Master data tables hold the relatively static records that postings refer to, such as the chart of accounts, customers, and vendors. These tables are shared across many transactions, so their contents change far less often than the daily accounting documents that point to them.

### General Ledger (G/L) Account Tables

General ledger master data is split between chart-of-accounts level and company-code level, which lets one chart of accounts serve several company codes.

| Code | Description |
| --- | --- |
| SKA1 | G/L accounts (chart of accounts) |
| SKAT | G/L accounts (chart of accounts: description) |
| SKB1 | G/L accounts (company code) |

### Customer Master Tables

Customer master data supports [accounts receivable](https://www.guru99.com/accounts-receivable-in-sap-fi.html). The general data in KNA1 is shared across the client, while KNB1 stores the company-code-specific view such as the reconciliation account and dunning procedure.

| Code | Description |
| --- | --- |
| KNA1 | Customer master (general data) |
| KNB1 | Customer master (company code) |
| KNVV | Customer sales data |
| KNBK | Bank details |
| KNVH | Customer hierarchy |
| KNVP | Customer partner functions |
| KNVS | Shipment data for customer |
| KNVK | Contact persons |
| KNVI | Customer master tax indicator |

### Vendor Master Tables

Vendor master data supports [accounts payable](https://www.guru99.com/accounts-payable-in-sap-fi.html) and mirrors the customer structure. LFA1 carries the general data, LFB1 the company-code data, and LFB5 the dunning data used by the dunning program. The account group that controls these fields is set when you [create a vendor account group](https://www.guru99.com/how-to-create-a-vendor-account-group.html).

| Code | Description |
| --- | --- |
| LFA1 | Vendor master (general data) |
| LFB1 | Vendor master (company code) |
| LFB5 | Vendor dunning data |
| LFM1 | Purchasing organization data |
| LFM2 | Purchasing data |
| LFBK | Bank details |

### Customer–Material Info and Bank Data Tables

Two smaller master data tables round out this group: KNMT links a customer to a material, and BNKA holds the central bank directory used by customer, vendor, and house bank records.

| Code | Description |
| --- | --- |
| KNMT | Customer–material info record |
| BNKA | Master bank data |

**Don't Miss:**

- [How to Define Retained Earnings Account in SAP](https://www.guru99.com/how-to-create-retained-earnings-account.html)
- [What is Residual Payment in SAP with Example](https://www.guru99.com/how-to-post-incoming-partial-payments-by-residual-method.html)
- [How to Create One Time Vendor FK01 in SAP](https://www.guru99.com/how-to-create-one-time-vendor-master-data.html)
- [How To Create a Vendor Account Group in SAP FICO](https://www.guru99.com/how-to-create-a-vendor-account-group.html)

## SAP FI Transaction Data Tables (Accounting Documents)

Every posting in Financial Accounting creates an accounting document that is stored across a header table and a line item table, supported by a set of secondary index tables that speed up open and cleared item reporting.

BKPF holds one row per document with header details such as document type, posting date, and fiscal year. BSEG holds the line items, so a single BKPF header is linked to several BSEG rows. The secondary index tables then copy selected line items by account type: the BSI\* tables hold open items and the BSA\* tables hold cleared items, split into customer (D), vendor (K), and general ledger (S) versions.

| Code | Description |
| --- | --- |
| BKPF | Accounting document header |
| BSEG | Accounting document segment (line items) |
| BSID | Secondary index for customers (open items) |
| BSIK | Secondary index for vendors (open items) |
| BSIM | Secondary index, documents for material |
| BSIP | Index for vendor validation of double documents |
| BSIS | Secondary index for G/L accounts (open items) |
| BSAD | Index for customers (cleared items) |
| BSAK | Index for vendors (cleared items) |
| BSAS | Index for G/L accounts (cleared items) |

## SAP FI Payment Run Tables

The automatic payment program (transaction F110) writes its results into two tables. REGUH stores the payment (settlement) data per payee, and REGUP stores the individual open items that each payment cleared, which is useful when you reconcile an [outgoing payment](https://www.guru99.com/how-to-map-symbolic-account-to-gl-account.html) or investigate a proposal.

| Code | Description |
| --- | --- |
| REGUH | Settlement data from the payment program |
| REGUP | Processed items from the payment program |

## SAP FI Customizing (Configuration) Tables

Customizing tables store the configuration set in the Implementation Guide (SPRO). They control how documents post and how the company code, fiscal year, and posting periods behave, so consultants often check them to confirm a setting quickly.

### Company Code Configuration Tables

These tables define the organizational and chart-of-accounts settings that anchor every posting to a company code.

| Code | Description |
| --- | --- |
| T004 | Chart of accounts |
| T077S | Account group (G/L accounts) |
| T009 | Fiscal year variants |
| T880 | Global company data |
| T014 | Credit control area |

### FI Document Configuration Tables

Document control tables decide which document types are allowed and which posting periods are open, working together with the posting period variant.

| Code | Description |
| --- | --- |
| T010O | Posting period variant |
| T010P | Posting period variant names |
| T001B | Permitted posting periods |
| T003 | Document types |
| T012 | House banks |

## How to View SAP FI Table Data (SE16, SE16N, SE16H)

Knowing a table name is only useful if you can read its contents. SAP ships a data browser for exactly this, and it needs no ABAP programming.

- **SE16 / SE16N** — the general data browser. Enter the table name, for example BSEG, apply filters on key fields, and run the selection to list matching rows. SE16N is the more flexible successor and lets you filter on any field.
- **SE16H** — an enhanced browser available in SAP S/4HANA that supports joins, grouping, and aggregation directly in the interface, which helps when analyzing large datasets.
- **SE11** — the ABAP Dictionary. Use it to view a table definition (its fields, data types, and keys) rather than its data.

To discover a table name while working, place the cursor on any field, press F1, and choose the Technical Information button. SAP then shows the table and field that store the value, which you can open in SE16N straight away. Access to these transactions is governed by the standard authorization objects in the [SAP GUI](https://www.guru99.com/sap-gui-tutorial.html), so display access is usually restricted in production systems.

## SAP FI Tables in S/4HANA and the Universal Journal (ACDOCA)

SAP S/4HANA simplifies the FI data model around a single line item table called the Universal Journal, ACDOCA. It merges Financial Accounting and Controlling line items into one table, which removes the need to reconcile FI and CO separately.

Because of this, the classic secondary index and totals tables — BSID, BSIK, BSIS, BSAD, BSAK, BSAS, and totals such as GLT0 — are no longer written as separate physical tables. SAP replaces them with CDS compatibility views of the same name that read from ACDOCA and BSEG, so older reports keep working. BKPF still stores the document header and BSEG still exists as an open item registry, but ACDOCA is the source of truth for reporting.

## How SAP FI Tables Are Linked Together

The FI tables connect through a small set of shared key fields, which is what lets you follow a figure from a report back to its source document.

- An accounting document is identified by company code (BUKRS), document number (BELNR), and fiscal year (GJAHR); BKPF and BSEG share this key, so one header joins to its line items.
- Line items in BSEG carry the account number, which links back to master data in SKA1/SKB1 (G/L), KNA1/KNB1 (customer), or LFA1/LFB1 (vendor).
- The secondary index tables (BSID, BSIK, BSIS and the cleared-item BSA\* tables) are derived from the document line items, so they always trace back to the same BKPF and BSEG rows.

Understanding these links makes month-end tasks such as [dunning](https://www.guru99.com/how-to-perform-dunning.html) and open item clearing much easier to audit, because every balance can be traced to the documents behind it.

## FAQs

🔍 How do I find which table stores a specific field in SAP FI?

Place the cursor on the field, press F1, then choose Technical Information. SAP shows the table and field names behind that screen field. You can then open SE11 to view its definition or SE16N to read the stored data.

🆚 What is the difference between the BSID and BSAD tables?

BSID stores open customer line items that are not yet cleared, while BSAD stores cleared customer items after payment. Vendors use BSIK and BSAK, and general ledger accounts use BSIS and BSAS, following the same open-versus-cleared pattern.

🏦 What does the LFB5 table store in SAP?

LFB5 holds vendor dunning data at company-code level, including the last dunning date, the dunning level, and any dunning block. The dunning program reads and updates LFB5 when it selects overdue vendor items and prints dunning notices.

📇 What is the difference between the KNA1 and KNB1 tables?

KNA1 holds general customer master data shared across the client, such as name, address, and tax details. KNB1 holds company-code-specific data like the reconciliation account, payment terms, and dunning procedure for the same customer.

🧮 What is the T001 table used for in SAP FI?

T001 is the company codes table. It stores each company code with its name, currency, chart of accounts, fiscal year variant, and country. Almost every FI configuration and reporting table links back to the company code held in T001.

🔤 What do the letters in SAP FI index table names (BSID, BSIK, BSIS) mean?

The prefix BS marks a bookkeeping secondary index. The final letter names the account type: D for debitor (customer), K for kreditor (vendor), and S for sachkonto (general ledger). The matching BSA tables hold the cleared items.

🤖 How does AI help analyze data in SAP FI tables?

Machine learning scans tables such as BSEG and ACDOCA to flag anomalies, predict cash flow, and detect duplicate or fraudulent postings. SAP Business AI and the Joule copilot surface these insights through natural-language queries over the Universal Journal.

💡 Can GitHub Copilot help query SAP FI tables?

[GitHub Copilot](https://github.com/features/copilot) drafts ABAP, SQL, and CDS view code that reads tables like BKPF and BSEG, which speeds up custom extracts and reports. It does not connect to SAP directly, so test every generated query in a sandbox client first.

#### Summarize this post with:

ChatGPTPerplexityGrokGoogle AI

**Stay Updated on AI** **Get Weekly AI Skills, Trends, Actionable Advice.**

##### Sign up for the newsletter

Subscribe for Free

You have successfully subscribed.  
Please check your inbox.

![AI-Newsletter]() Chosen by over **350,000+** professionals

[Scroll to top](#wrapper)

×

Search for:

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://www.guru99.com/#organization","name":"Guru99","sameAs":["https://www.facebook.com/Guru99Official","https://twitter.com/guru99com"],"logo":{"@type":"ImageObject","@id":"https://www.guru99.com/#logo","url":"https://www.guru99.com/images/guru99-logo-v1-150x59.png","contentUrl":"https://www.guru99.com/images/guru99-logo-v1-150x59.png","caption":"Guru99","inLanguage":"en-US"}},{"@type":"WebSite","@id":"https://www.guru99.com/#website","url":"https://www.guru99.com","name":"Guru99","publisher":{"@id":"https://www.guru99.com/#organization"},"inLanguage":"en-US"},{"@type":"ImageObject","@id":"https://www.guru99.com/images/sap-fi-important-tables.png","url":"https://www.guru99.com/images/sap-fi-important-tables.png","width":"700","height":"250","caption":"SAP FI Important TABLES","inLanguage":"en-US"},{"@type":"BreadcrumbList","@id":"https://www.guru99.com/important-tables-in-fi-module.html#breadcrumb","itemListElement":[{"@type":"ListItem","position":"1","item":{"@id":"https://www.guru99.com","name":"Home"}},{"@type":"ListItem","position":"2","item":{"@id":"https://www.guru99.com/sap-fico-training-tutorials1","name":"SAP FICO"}},{"@type":"ListItem","position":"3","item":{"@id":"https://www.guru99.com/important-tables-in-fi-module.html","name":"SAP FI Important TABLES: Must Know!"}}]},{"@type":"WebPage","@id":"https://www.guru99.com/important-tables-in-fi-module.html#webpage","url":"https://www.guru99.com/important-tables-in-fi-module.html","name":"SAP FI Important TABLES: Must Know!","dateModified":"2026-10-09T11:46:43+05:30","isPartOf":{"@id":"https://www.guru99.com/#website"},"primaryImageOfPage":{"@id":"https://www.guru99.com/images/sap-fi-important-tables.png"},"inLanguage":"en-US","breadcrumb":{"@id":"https://www.guru99.com/important-tables-in-fi-module.html#breadcrumb"}},{"@type":"Person","@id":"https://www.guru99.com/author/editorial","name":"Editorial Team","url":"https://www.guru99.com/author/editorial","image":{"@type":"ImageObject","@id":"https://www.guru99.com/images/favicon-new-logo.png","url":"https://www.guru99.com/images/favicon-new-logo.png","caption":"Editorial Team","inLanguage":"en-US"},"sameAs":["https://www.guru99.com/editorial-team"],"worksFor":{"@id":"https://www.guru99.com/#organization"}},{"articleSection":"SAP FICO","headline":"SAP FI Important TABLES: Must Know!","description":"It offers the exhaustive list of various tables on FI module, the list consists of topics like Master Data, Accounting documents, Payment run","keywords":"sap-fi","speakable":{"@type":"SpeakableSpecification","cssSelector":[".entry-title",".summary"]},"@type":"Article","author":{"@id":"https://www.guru99.com/author/editorial","name":"Editorial Team"},"dateModified":"2026-10-09T11:46:43+05:30","image":{"@id":"https://www.guru99.com/images/sap-fi-important-tables.png"},"copyrightYear":"2026","name":"SAP FI Important TABLES: Must Know!","subjectOf":[{"@type":"FAQPage","mainEntity":[{"@type":"Question","name":"How do I find which table stores a specific field in SAP FI?","acceptedAnswer":{"@type":"Answer","text":"Place the cursor on the field, press F1, then choose Technical Information. SAP shows the table and field names behind that screen field. You can then open SE11 to view its definition or SE16N to read the stored data."}},{"@type":"Question","name":"What is the difference between the BSID and BSAD tables?","acceptedAnswer":{"@type":"Answer","text":"BSID stores open customer line items that are not yet cleared, while BSAD stores cleared customer items after payment. Vendors use BSIK and BSAK, and general ledger accounts use BSIS and BSAS, following the same open-versus-cleared pattern."}},{"@type":"Question","name":"What does the LFB5 table store in SAP?","acceptedAnswer":{"@type":"Answer","text":"LFB5 holds vendor dunning data at company-code level, including the last dunning date, the dunning level, and any dunning block. The dunning program reads and updates LFB5 when it selects overdue vendor items and prints dunning notices."}},{"@type":"Question","name":"What is the difference between the KNA1 and KNB1 tables?","acceptedAnswer":{"@type":"Answer","text":"KNA1 holds general customer master data shared across the client, such as name, address, and tax details. KNB1 holds company-code-specific data like the reconciliation account, payment terms, and dunning procedure for the same customer."}},{"@type":"Question","name":"What is the T001 table used for in SAP FI?","acceptedAnswer":{"@type":"Answer","text":"T001 is the company codes table. It stores each company code with its name, currency, chart of accounts, fiscal year variant, and country. Almost every FI configuration and reporting table links back to the company code held in T001."}},{"@type":"Question","name":"What do the letters in SAP FI index table names (BSID, BSIK, BSIS) mean?","acceptedAnswer":{"@type":"Answer","text":"The prefix BS marks a bookkeeping secondary index. The final letter names the account type: D for debitor (customer), K for kreditor (vendor), and S for sachkonto (general ledger). The matching BSA tables hold the cleared items."}},{"@type":"Question","name":"How does AI help analyze data in SAP FI tables?","acceptedAnswer":{"@type":"Answer","text":"Machine learning scans tables such as BSEG and ACDOCA to flag anomalies, predict cash flow, and detect duplicate or fraudulent postings. SAP Business AI and the Joule copilot surface these insights through natural-language queries over the Universal Journal."}},{"@type":"Question","name":"Can GitHub Copilot help query SAP FI tables?","acceptedAnswer":{"@type":"Answer","text":"GitHub Copilot drafts ABAP, SQL, and CDS view code that reads tables like BKPF and BSEG, which speeds up custom extracts and reports. It does not connect to SAP directly, so test every generated query in a sandbox client first."}}]}],"@id":"https://www.guru99.com/important-tables-in-fi-module.html#schema-1148073","isPartOf":{"@id":"https://www.guru99.com/important-tables-in-fi-module.html#webpage"},"publisher":{"@id":"https://www.guru99.com/#organization"},"inLanguage":"en-US","mainEntityOfPage":{"@id":"https://www.guru99.com/important-tables-in-fi-module.html#webpage"}}]}
```