# Customer and Material Price Conditions with Validity Dates Report

> A custom ALV report that lists customer-specific price conditions in one list with their validity dates, the difference to the list price and the records that are about to expire. Before the yearly price update you see which customer price ends when.

- Type: Report, Custom development, ALV report
- Module: SD
- Estimated effort: M (3–5 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/customer-material-price-conditions-validity-report/


## Why is the standard not enough?

VK13 shows condition records for one condition type and key combination; it does not compare all customer prices with the list price, does not flag records that expire or have no successor and does not produce a clean comparison table for Excel. Yearly price negotiations and contract renewals need a report that makes this comparison.

### Closest standard alternatives

- VK13: Shows condition records for one condition type and key; does not compare them with the list price or flag expiring records.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| A305 | Customer/material price condition key and validity dates (driving table) | Read | - | ECC + S/4 |
| KONP | Condition amount, currency, pricing unit and deletion flag | Read | KONP-KNUMH = A305-KNUMH | ECC + S/4 |
| KONH | Creator and date of the condition record | Read | KONH-KNUMH = A305-KNUMH | ECC + S/4 |
| A304 | Material-level list price for comparison | Read | A304-KAPPL = A305-KAPPL AND A304-KSCHL = A305-KSCHL AND A304-VKORG = A305-VKORG AND A304-VTWEG = A305-VTWEG AND A304-MATNR = A305-MATNR | ECC + S/4 |
| KNA1 | Customer name | Read | KNA1-KUNNR = A305-KUNNR | ECC + S/4 |
| MAKT | Material description | Read | MAKT-MATNR = A305-MATNR AND MAKT-SPRAS = SY-LANGU | ECC + S/4 |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_KSCHL | Condition type | Range / multiple | A305-KSCHL | Yes |
| S_VKORG | Sales organization | Range / multiple | A305-VKORG | Yes |
| S_VTWEG | Distribution channel | Range / multiple | A305-VTWEG | No |
| S_KUNNR | Customer | Range / multiple | A305-KUNNR | No |
| S_MATNR | Material | Range / multiple | A305-MATNR | No |
| P_KEYDT | Key date (blank = all records) | Single value | - | No |
| P_DAYS | Days ahead for expiring records | Single value | - | No |
| P_NODEL | Exclude records marked for deletion | Checkbox | - | No |

## Output columns

| Column | Source |
|---|---|
| Condition type | A305-KSCHL |
| Customer | A305-KUNNR |
| Customer name | KNA1-NAME1 |
| Material | A305-MATNR |
| Material description | MAKT-MAKTX |
| Customer price | KONP-KBETR |
| Currency | KONP-KONWA |
| Pricing unit | KONP-KPEIN |
| Unit | KONP-KMEIN |
| Valid from | A305-DATAB |
| Valid to | A305-DATBI |
| List price | Calculated: KONP-KBETR of the A304 record valid on the same date |
| Difference to list % | Calculated: (Customer price − list price) ÷ list price × 100 |
| Status | Calculated: Valid, expiring (no successor), expired, above list |
| Created by | KONH-ERNAM |

## How does the report work?

1. The customer/material condition table A305 is read for the selected condition types (KSCHL, e.g. PR00), sales organization and distribution channel; the application is V. If a key date is given, only records valid on that day (DATAB ≤ date ≤ DATBI) are taken.
2. The amount, currency, pricing unit and unit of measure of each record come from KONP, the creator and creation date from KONH; items marked for deletion (LOEVM_KO) can be excluded.
3. For the same material the material-level list price is read from A304 and KONP for the same date; the difference between the customer price and the list price is calculated as a percentage.
4. Prices whose end date falls within the day count in the parameter and that have no later record for the same key are flagged "expiring, no successor". Customer prices higher than the list price are flagged separately.
5. The customer name is added from KNA1 and the material description from MAKT. Company-specific condition tables can be added to the report with the same structure.

## Authorization objects

- V_KONH_VKS: Condition record authorization by condition type
- V_KONH_VKO: Condition authorization by sales organization

## Frequently asked questions

### We use other condition tables besides A305; does the report show them too?

Yes. The tables of the access sequence are identified at installation and each one is mapped to the same output structure; each extra table adds a small amount of effort.

### How are scale prices shown?

The main list shows the amount of the first scale level. If scale details are needed, a second list reached from the line can be added.

### Does this report change on S/4HANA?

No. Sales condition records are still stored in KONH, KONP and the A tables on S/4HANA; the report works the same way.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=sd-customer-price-conditions-validity
