SD Report Custom development ALV report

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.

TableRoleJoinSystem
A305Condition Table: Customer/Material with Release StatusCustomer/material price condition key and validity dates (driving table)—ECC + S/4
KONPConditions (Item)Condition amount, currency, pricing unit and deletion flagKONP-KNUMH = A305-KNUMHECC + S/4
KONHConditions (Header)Creator and date of the condition recordKONH-KNUMH = A305-KNUMHECC + S/4
A304Condition Table: Material with Release StatusMaterial-level list price for comparisonA304-KAPPL = A305-KAPPL AND A304-KSCHL = A305-KSCHL AND A304-VKORG = A305-VKORG AND A304-VTWEG = A305-VTWEG AND A304-MATNR = A305-MATNRECC + S/4
KNA1Customer Master (General Section)Customer nameKNA1-KUNNR = A305-KUNNRECC + S/4
MAKTMaterial DescriptionsMaterial descriptionMAKT-MATNR = A305-MATNR AND MAKT-SPRAS = SY-LANGUECC + S/4

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
S_KSCHLCondition typeRange / multipleA305-KSCHLYesPR00
S_VKORGSales organizationRange / multipleA305-VKORGYes1000
S_VTWEGDistribution channelRange / multipleA305-VTWEGNo10
S_KUNNRCustomerRange / multipleA305-KUNNRNo200100
S_MATNRMaterialRange / multipleA305-MATNRNoFG-5001
P_KEYDTKey date (blank = all records)Single value—No17.11.2026
P_DAYSDays ahead for expiring recordsSingle value—No45
P_NODELExclude records marked for deletionCheckbox—NoX

Output columns

#ColumnSource
1Condition typeA305-KSCHL
2CustomerA305-KUNNR
3Customer nameKNA1-NAME1
4MaterialA305-MATNR
5Material descriptionMAKT-MAKTX
6Customer priceKONP-KBETR
7CurrencyKONP-KONWA
8Pricing unitKONP-KPEIN
9UnitKONP-KMEIN
10Valid fromA305-DATAB
11Valid toA305-DATBI
12List priceCalculated KONP-KBETR of the A304 record valid on the same date
13Difference to list %Calculated (Customer price − list price) ÷ list price × 100
14StatusCalculated Valid, expiring (no successor), expired, above list
15Created byKONH-ERNAM

Sample output

Condition typeCustomerCustomer nameMaterialMaterial descriptionCustomer priceCurrencyPricing unitUnitValid fromValid toList priceDifference to list %StatusCreated by
PR00200100Marmara GıdaFG-5001Packed product A295TRY1PC01/01/202612/31/2026320-7.80Expiring, no successorFIYAT01
PR00200245Karadeniz MarketFG-5001Packed product A305TRY1PC07/01/202606/30/2027320-4.70ValidFIYAT02
PR00200388Toros Yapı MarketFG-6100Garden set1,240TRY1SET03/01/202602/28/20271,2003.30Above listFIYAT01
PR00300410Ege Tekstil Dış TicaretFG-5002Packed product B6.40EUR1PC11/01/202510/31/20267.10-9.90ExpiredFIYAT03
A view built with fictional sample data; not real system data.

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.

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

SD Package Custom

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 …

5 components · v1.0

Related reports

SD Report Custom ALV report

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 …

VBAK · VBAP · KNA1 · KONV

SD Program Custom Mass upload

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 …

VBAK · VBAP · VBEP · VBKD

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.

Related report: Customer and Material Price Conditions with Validity Dates Report