Customer and Material Price Conditions with Validity Dates Report
Short answer: 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.
- Estimated effort
- M · 3–5 working days
- System
- ECC and S/4HANA
- Tables
- 6
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
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.
Who uses it? Pricing teams, sales managers, account managers and sales controllers.
Closest standard alternatives
- VK13 Display Condition. Shows condition records for one condition type and key; does not compare them with the list price or flag expiring records.
Tables used
The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.
| Table | Role | Join | System |
|---|---|---|---|
| A305Condition Table: Customer/Material with Release Status | Customer/material price condition key and validity dates (driving table) | — | ECC + S/4 |
| KONPConditions (Item) | Condition amount, currency, pricing unit and deletion flag | KONP-KNUMH = A305-KNUMH | ECC + S/4 |
| KONHConditions (Header) | Creator and date of the condition record | KONH-KNUMH = A305-KNUMH | ECC + S/4 |
| A304Condition Table: Material with Release Status | Material-level list price for comparison | 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 |
| KNA1Customer Master (General Section) | Customer name | KNA1-KUNNR = A305-KUNNR | ECC + S/4 |
| MAKTMaterial Descriptions | Material description | MAKT-MATNR = A305-MATNR AND MAKT-SPRAS = SY-LANGU | ECC + S/4 |
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_KSCHL | Condition type | Range / multiple | A305-KSCHL | Yes | PR00 |
| S_VKORG | Sales organization | Range / multiple | A305-VKORG | Yes | 1000 |
| S_VTWEG | Distribution channel | Range / multiple | A305-VTWEG | No | 10 |
| S_KUNNR | Customer | Range / multiple | A305-KUNNR | No | 200100 |
| S_MATNR | Material | Range / multiple | A305-MATNR | No | FG-5001 |
| P_KEYDT | Key date (blank = all records) | Single value | — | No | 17.11.2026 |
| P_DAYS | Days ahead for expiring records | Single value | — | No | 45 |
| P_NODEL | Exclude records marked for deletion | Checkbox | — | No | X |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | Condition type | A305-KSCHL |
| 2 | Customer | A305-KUNNR |
| 3 | Customer name | KNA1-NAME1 |
| 4 | Material | A305-MATNR |
| 5 | Material description | MAKT-MAKTX |
| 6 | Customer price | KONP-KBETR |
| 7 | Currency | KONP-KONWA |
| 8 | Pricing unit | KONP-KPEIN |
| 9 | Unit | KONP-KMEIN |
| 10 | Valid from | A305-DATAB |
| 11 | Valid to | A305-DATBI |
| 12 | List price | Calculated KONP-KBETR of the A304 record valid on the same date |
| 13 | Difference to list % | Calculated (Customer price − list price) ÷ list price × 100 |
| 14 | Status | Calculated Valid, expiring (no successor), expired, above list |
| 15 | Created by | KONH-ERNAM |
Sample output
| Condition type | Customer | Customer name | Material | Material description | Customer price | Currency | Pricing unit | Unit | Valid from | Valid to | List price | Difference to list % | Status | Created by |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| PR00 | 200100 | Marmara Gıda | FG-5001 | Packed product A | 295 | TRY | 1 | PC | 01/01/2026 | 12/31/2026 | 320 | -7.80 | Expiring, no successor | FIYAT01 |
| PR00 | 200245 | Karadeniz Market | FG-5001 | Packed product A | 305 | TRY | 1 | PC | 07/01/2026 | 06/30/2027 | 320 | -4.70 | Valid | FIYAT02 |
| PR00 | 200388 | Toros Yapı Market | FG-6100 | Garden set | 1,240 | TRY | 1 | SET | 03/01/2026 | 02/28/2027 | 1,200 | 3.30 | Above list | FIYAT01 |
| PR00 | 300410 | Ege Tekstil Dış Ticaret | FG-5002 | Packed product B | 6.40 | EUR | 1 | PC | 11/01/2025 | 10/31/2026 | 7.10 | -9.90 | Expired | FIYAT03 |
How does the report work?
- 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.
- 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.
- 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.
- 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.
- 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.
Performance notes
Read the condition tables with the KAPPL + KSCHL + VKORG + VTWEG key. Read KONP in bulk with the list of KNUMH. On systems with many customer prices, run it in the background and take the Excel output.
Features
- ALV list (sort, filter, subtotals)
- User-specific layout variants
- Double-click drill-down to the document Double-clicking a line opens the record in VK13.
- Export to Excel
- Runs as a background job
- Send the result by email Prices ending within the next 45 days can be sent to account managers every Monday.
Authorization objects
- V_KONH_VKSCondition record authorization by condition type
- V_KONH_VKOCondition 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.
Packages that include this solution
Pricing and Billing Accuracy Pack
A five-component pack that catches pricing and billing errors from loading the price list to posting the invoice: mass price condition upload from …
Related reports
Sales Order Gross Margin Report by Item
A custom ALV report that compares the net value of every sales order item with the cost determined in pricing and shows the gross profit and margin …
Mass Sales Order Creation from Excel Program
A custom program that creates sales orders in bulk from the rows of an order file sent by the customer. It groups rows into orders by customer PO …
Let us build this report for your system
Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.