SAP Table A305
Customer/material with release status
What Is the SAP A305 Table?
SAP A305 Table is used to store Customer Material Pricing Condition Record references with release status in the Sales and Distribution (SD) module.
In SAP SD, Pricing condition records are maintained to determine customer specific material prices, discounts, and other pricing conditions during sales transactions.
A305 table helps to identify the applicable customer material price based on Sales Organization, Distribution channel, Customer Number, Material Number, Condition Type, Release status and validity period.
Quick overview
| SAP table | A305 |
|---|---|
| Short description | Customer/material with release status |
| Table type | Transparent table |
| Primary key | MANDT (Client), KAPPL (Application), KSCHL (Condition Type), VKORG (Sales Organization), VTWEG (Distribution Channel), KUNNR (Customer number), MATNR (Material Number), KFRST (Release Status), DATBI (Validity end date of the condition record) |
| Client-dependent | Yes |
Important fields explained
| Field | SAP field description | What this field means |
|---|---|---|
KAPPL |
Application | Application area in which the pricing condition is used. |
KSCHL |
Condition Type | Condition type used for pricing. |
VKORG |
Sales Organization | Sales organization for which the customer-material pricing condition record is maintained. |
VTWEG |
Distribution Channel | Distribution channel associated with the customer-material pricing condition record. |
KUNNR |
Customer number | Customer number for which the customer-material pricing condition record is maintained. |
MATNR |
Material Number | Material number for which the customer-specific pricing condition record is maintained. |
KFRST |
Release Status | Release status of the customer-material pricing condition record. |
At a glance
- Module
- Sales and Distribution SD
- Application component
- MASTER DATA SD-MD
- Subcomponent
- CONDITIONS SD-MD-CM
Technical details
- Delivery class
- A (Application table: master and transaction data)
- Data class
- APPL0 (Master Data, Transparent Tables)
- Package
- Application development Conditions (VKON)
Primary key fields
| Field | Description | Data element | Type | Length |
|---|---|---|---|---|
MANDT
|
Client | MANDT | CLNT | 3 |
KAPPL
|
Application | KAPPL | CHAR | 2 |
KSCHL
|
Condition Type | KSCHA | CHAR | 4 |
VKORG
|
Sales Organization | VKORG | CHAR | 4 |
VTWEG
|
Distribution Channel | VTWEG | CHAR | 2 |
KUNNR
|
Customer number | KUNNR_V | CHAR | 10 |
MATNR
|
Material Number | MATNR | CHAR | 40 |
KFRST
|
Release Status | KFRST | CHAR | 1 |
DATBI
|
Validity end date of the condition record | KODATBI | DATS | 8 |
Table fields
12 fields
12 fields
| Field | Description | Data element | Domain | Type | Length | Decimals | Check table |
|---|---|---|---|---|---|---|---|
MANDT
Key
|
Client | MANDT | MANDT | CLNT | 3 | — | T000 |
KAPPL
Key
|
Application | KAPPL | KAPPL | CHAR | 2 | — | T681A |
KSCHL
Key
|
Condition Type | KSCHA | KSCHL | CHAR | 4 | — | T685 |
VKORG
Key
|
Sales Organization | VKORG | VKORG | CHAR | 4 | — | TVKO |
VTWEG
Key
|
Distribution Channel | VTWEG | VTWEG | CHAR | 2 | — | TVTW |
KUNNR
Key
|
Customer number | KUNNR_V | KUNNR | CHAR | 10 | — | KNA1 |
MATNR
Key
|
Material Number | MATNR | MATNR | CHAR | 40 | — | MARA |
KFRST
Key
|
Release Status | KFRST | KFRST | CHAR | 1 | — | |
DATBI
Key
|
Validity end date of the condition record | KODATBI | DATUM | DATS | 8 | — | |
DATAB
|
Validity start date of the condition record | KODATAB | DATUM | DATS | 8 | — | |
KBSTAT
|
Processing status for conditions | KBSTAT | KBSTAT | CHAR | 2 | — | T686E |
KNUMH
|
Number of Condition Record | KNUMH | KNUMH | CHAR | 10 | — |
No fields match the selected filters.
Editorial and verification
- Content editor
- ERPSAP Content Team
- Technical reviewer
- ERPSAP Technical Review Team
- Verified against
- SAP S/4HANA 2023 On-Premise system
- Last updated
- October 11, 2026
The information on this SAP A305 table page is based on the verified SAP S/4HANA 2023 on-premise system identified above. Table definitions, fields, and availability may differ across SAP releases and customer-specific systems.