database tables – SAP EWM Help

What Are Table Delivery Classes in SAP?

DPM125 — Sat, 02 Aug 2025 12:05:05 +0000

Table Delivery Classes define how a table is delivered by SAP, and how data in that table is handled during client copies, upgrades, and transports. Every table in SAP must have a delivery class, and it’s set in SE11 under the Attributes tab.

Why Is Delivery Class Important?

It determines:

Whether data in the table is customizing, master data, or transactional
If and how the data is transported between systems
Whether the data is client-dependent or client-independent
How the table behaves during client copy or SAP upgrades.

Delivery Class	Description
A – Application Table (Master & Transaction Data)	Client-dependent; used for storing application data like customers, sales, etc. Data is typically not transported.
C – Customizing Table (Client-dependent)	Holds configuration data; client-dependent; transportable via customizing request.
E – Customizing Table (Client-independent)	Like C, but client-independent. Must be handled carefully as changes affect all clients.
L – SAP Table for storing temporary data	Temporary/volatile data; no transport or client copy. Example: log or buffer tables.
G – Customizing Table (with text table)	Used with a corresponding text table; data is often language-dependent.
S – System Table	Stores system data; client-independent; changes are rare and usually done by SAP only.
W – Repository Table	Stores data about repository objects (e.g., table definitions); technical SAP use only.

Examples:

KNA1 (Customer Master) → Delivery Class A
T001 (Company Codes) → Delivery Class C
TADIR (Repository Info) → Delivery Class W
T000 (Client Table) → Delivery Class S

Cluster vs. Pooled vs. Transparent

DPM125 — Sat, 02 Aug 2025 11:36:44 +0000

Feature	Transparent Table	Pooled Table	Cluster Table
Physical Mapping	1:1	Many:1	Many:1
Data Compression	No	No	Yes (compressed)
Used For	All-purpose	Customizing data	Related business data
Supported in HANA?	✅ Yes	❌ No	❌ No

Note:

Pooled and Cluster tables are no longer supported in SAP HANA and S/4HANA.
SAP recommends using transparent tables for performance and compatibility with modern databases.

What are pooled tables in SAP?

DPM125 — Sat, 02 Aug 2025 11:29:15 +0000

In SAP, pooled tables are a type of database table used to store data from multiple internal tables (called logical tables) within a single physical table in the database. Pooled tables help in reducing the number of database objects and are primarily used for storing control data (like customizing settings or system-specific settings) rather than transactional data.

Example:
Suppose there are logical tables ZTABLE1, ZTABLE2, and ZTABLE3 — all are pooled tables.These are all stored together inside a single physical table, say POOLTAB.

When you access ZTABLE1 from within SAP, the system filters and retrieves only those records in POOLTAB that belong to ZTABLE1.