SE16N (General Table Display) is the SAP transaction code most people use to look at the contents of a database table without writing any code. Functional consultants, key users, ABAP developers and auditors use it every day to check master data, accounting documents, configuration and interface records. This guide explains how to use the SE16N tcode step by step, how to filter and save variants, why it sometimes does not return every record, what happened to &SAP_EDIT, and when SE16 or SE16H is the better choice.
What is SE16N in SAP?
SE16N is a data browser that shows the contents of ABAP Dictionary tables and views in an ALV grid. Compared with the classic SE16 Data Browser, it lets you enter several values per field on a single screen, choose which columns to output, add descriptions from the text table and save your selection as a variant. It is available in SAP ECC and in SAP S/4HANA (on-premise and private cloud).
Not sure which table holds the data you need? See our SAP tables list by module and the SAP transaction codes list.
How to display a table with SE16N step by step
- Enter /nSE16N in the command field and press Enter.
- In the Table field enter the technical name (for example
BKPF, accounting document header) and press Enter. SE16N loads every field of the table into the selection criteria grid. - If the table has a text table (for example
SKA1withSKAT), SE16N proposes it in the Text table field; tick the checkbox to show descriptions next to the codes. - Check Maximum no. of hits. The default is 500, so you will only see the first 500 records even if more exist. Clear it or raise it when you need the full result.
- Enter your filters in the from/to value columns. The multiple selection button on each row lets you paste a list of values from Excel, exclude values or use
*patterns. - Untick the Output column for fields you do not need: the list becomes easier to read and the query runs faster.
- Click Number of entries to count matching records before displaying them (very useful for large tables such as
BSEGorACDOCA). - Click Execute (F8). The result opens in an ALV grid where you can sort, filter, total, change the layout and export to a spreadsheet.
Example: accounting documents for one company code and period
| Field (BKPF) | Description | Example value |
|---|---|---|
| BUKRS | Company code | 1000 |
| GJAHR | Fiscal year | 2026 |
| MONAT | Posting period | 09 |
| BLART | Document type | SA, KR (multiple selection) |
| USNAM | User who posted | Optional |
These filters return the September 2026 document headers of company code 1000. To see the line items, query BSEG (ECC) or ACDOCA (S/4HANA) with the same company code, fiscal year and document number.
SE16N tips that save time
- Variants: save your filters and output columns as a variant to repeat the same query every month in one click.
- ALV layouts: save column order, sorting and subtotals as a user layout.
- Technical names: switch between field descriptions and technical field names when you document a query or talk to a developer.
- Exclusions: in the multiple selection dialog, the exclude tabs let you remove values (for example, every document type except AB).
- From ABAP: function module
SE16N_INTERFACEruns the same logic from a program.
Most common tables to check with SE16N in finance
| Table | Content | Note |
|---|---|---|
| BKPF | Accounting document header | ECC and S/4HANA |
| BSEG | Accounting document line items | In S/4HANA the main source is ACDOCA |
| ACDOCA | Universal Journal | S/4HANA only |
| SKA1 / SKB1 / SKAT | G/L accounts (chart, company code, texts) | G/L master data |
| LFA1 / KNA1 | Vendors / customers (general data) | Created via Business Partner in S/4HANA |
| T001 | Company codes | Configuration |
| BNKA | Bank master data | Bank keys |
| T012 / T012K | House banks and accounts | Treasury |
| TCURR | Exchange rates | Rate types M, B, G… |
In S/4HANA, old index tables such as BSID, BSAD, BSIK, BSAK, BSIS and BSAS are replaced by compatibility views: SE16N still displays them, but the data is read from the Universal Journal. More background in What is SAP FI.
SE16 vs SE16N vs SE16H: which one to use
| Feature | SE16 | SE16N | SE16H |
|---|---|---|---|
| Selection screen | Generated per table | Single grid with all fields | Same as SE16N |
| Several values per field | Yes (multiple selection) | Yes, easier | Yes |
| Text table | No | Yes | Yes |
| Group, count and sum | No | Only in the ALV result | Yes, in the database |
| Table joins | No | No | Yes, including outer joins |
| Typical use | Quick look | Daily queries with filters | Analysis and joins |
If you need to count records by a field or join two tables without coding, use SE16H. We cover it in Use SAP transaction SE16H instead of SE16 and SE16N; its functions are described in SAP Note 1636416.
Can you edit table entries with SE16N? &SAP_EDIT and alternatives
For years, typing &SAP_EDIT in the SE16N command field switched on a mode that allowed direct changes to any table. SAP deactivated it for security reasons with SAP Note 1420281 (“CO-OM tools: SE16N: Deactivating &SAP_EDIT”). The correct options today are:
- Configuration tables and custom Z tables with a maintenance view: SM30 or SM31 (or the matching IMG activity). For your own tables you can generate a maintenance dialog as shown in Create SAP custom table.
- Business data (documents, master data): the business transaction or Fiori app (FB02, BP…), which validates the data and writes change documents.
- Never change standard tables directly in production: it breaks consistency between tables and leaves no trace in the business object’s change history.
If maintenance from SE16N has been enabled for any table in your system, changes are logged in tables SE16N_CD_KEY (header) and SE16N_CD_DATA (data) and can be reviewed with report RKSE16N_CD_DISPLAY in SA38. It is one of the first things auditors check.
SE16N authorizations
| Object | Field | Value for display |
|---|---|---|
| S_TCODE | TCD | SE16N |
| S_TABU_DIS | DICBERCLS (authorization group) and ACTVT | Table’s group, activity 03 |
| S_TABU_NAM | TABLE and ACTVT | Table name, activity 03 |
If SE16N refuses access to a table, run SU53 immediately afterwards to see which authorization check failed and send it to your security team. Many companies restrict SE16N in production for sensitive tables (payroll, bank data, personal data) because of GDPR.
Common SE16N problems
- Missing records: almost always the maximum number of hits (500 by default). Clear or raise it.
- A value that exists is not found: check leading zeros and conversion routines (customer or material numbers) and upper/lower case in text fields.
- Slow query or timeout: filter on key or indexed fields (company code, fiscal year, document number), output fewer columns or use Number of entries first.
- Unexpected signs on amounts: in BSEG the sign depends on the debit/credit indicator (SHKZG); in ACDOCA amounts are already signed.
SE16N FAQ
What does SE16N stand for?
It is the transaction code for “General Table Display”, the enhanced version of the SE16 Data Browser.
Is SE16N available in SAP S/4HANA?
Yes. In S/4HANA on-premise and private cloud it works as in ECC. S/4HANA Cloud Public Edition has no SAP GUI access, so you work with Fiori apps and CDS views instead.
How do I export SE16N results to Excel?
Use the export (spreadsheet) button in the ALV result. If the file is incomplete, check the maximum number of hits first.
What is the difference between SE16N and SE16H?
SE16H adds grouping, counting, totals and table joins executed in the database. SE16N is enough for filtered queries on a single table.
Can I see who changed a table through SE16N?
Yes, if the change was made in SE16N: run report RKSE16N_CD_DISPLAY, which reads tables SE16N_CD_KEY and SE16N_CD_DATA.
