Mass Sales Price Condition Upload from Excel Program
Short answer: A custom program that creates sales price condition records per customer/material or per material, with validity dates, in bulk from Excel or CSV rows. Before saving, it reads the current price and shows the change in percent, runs every check in test mode and lists the result of each row.
- Estimated effort
- M · 4–6 working days
- System
- ECC and S/4HANA
- Tables
- 7
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
VK11 enters or copies condition records one by one; it does not read a file. VK12 changes existing records only by a common percentage or amount and cannot load a different price per row. For the yearly price list update, thousands of customer/material prices are entered manually or through fragile recordings. The custom program loads the price list from the file as it is and shows the difference to the old price before saving.
Who uses it? Pricing teams, sales operations and SD consultants.
Closest standard alternatives
Tables used
The tables the program reads and updates. ECC and S/4HANA differences are marked separately.
| Table | Role | Access | System |
|---|---|---|---|
| T685Condition Types | Condition type check (sales application) | Read | ECC + S/4 |
| KNVVCustomer Master Sales Data | Check that the customer exists in the sales area | Read | ECC + S/4 |
| MVKESales Data for Material | Check that the material exists in the sales organization and distribution channel | Read | ECC + S/4 |
| A305Condition Table: Customer/Material with Release Status | Customer/material condition table: the old record is read, the new key and validity are written | Read / write | ECC + S/4 |
| A004Condition Table: Material | Material condition table (when price per material is selected) | Read / write | ECC + S/4 |
| KONHConditions (Header) | Condition record header | Write | ECC + S/4 |
| KONPConditions (Item) | Condition amount, currency, price unit and unit of measure | Read / write | ECC + S/4 |
BAPIs and functions used
- RV_CONDITION_COPYPrepare Condition Records (Copy). Prepares the condition record with key, validity and amount for each row
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| P_FILE | Price list file (XLSX or CSV) | Single value | — | Yes | C:\temp\fiyat-listesi-2027.xlsx |
| P_KSCHL | Condition type | Single value | A305-KSCHL | Yes | PR00 |
| R_A305 | Customer/material price (A305) | Radio button | — | No | X |
| R_A004 | Material price (A004) | Radio button | — | No | — |
| P_TEST | Test mode (check without saving) | Checkbox | — | No | X |
Input file columns
The columns of the upload template and the SAP fields they are written to. Columns with an asterisk are mandatory.
| # | Column | Target field | Required |
|---|---|---|---|
| 1 | Sales organization | A305-VKORG | Yes |
| 2 | Distribution channel | A305-VTWEG | Yes |
| 3 | Customer (mandatory for A305) | A305-KUNNR | No |
| 4 | Material | A305-MATNR | Yes |
| 5 | Amount | KONP-KBETR | Yes |
| 6 | Currency | KONP-KONWA | Yes |
| 7 | Price unit | KONP-KPEIN | No |
| 8 | Unit of measure | KONP-KMEIN | No |
| 9 | Valid from | A305-DATAB | Yes |
| 10 | Valid to | A305-DATBI | Yes |
Sample upload file
| 1 | Sales organization * | Distribution channel * | Customer (mandatory for A305) | Material * | Amount * | Currency * | Price unit | Unit of measure | Valid from * | Valid to * |
|---|---|---|---|---|---|---|---|---|---|---|
| 2 | 1000 | 10 | 200100 | FG-1001 | 44.20 | TRY | 1 | CS | 12/01/2026 | 06/30/2027 |
| 3 | 1000 | 10 | 200245 | FG-1120 | 64.50 | TRY | 1 | CS | 12/01/2026 | 06/30/2027 |
| 4 | 1000 | 10 | FG-2050 | 57 | TRY | 1 | PC | 12/01/2026 | 12/31/9999 |
Result list columns
| # | Column | Source |
|---|---|---|
| 1 | Row | Calculated Row number in the file |
| 2 | Customer | A305-KUNNR |
| 3 | Material | A305-MATNR |
| 4 | Condition record | KONH-KNUMH |
| 5 | Old price | Calculated KONP-KBETR of the record valid today |
| 6 | New price | KONP-KBETR |
| 7 | Change % | Calculated (New price − old price) ÷ old price × 100 |
| 8 | Status | Calculated Created, test OK or error |
| 9 | Message | Calculated Check or save message |
Sample result list
| Row | Customer | Material | Condition record | Old price | New price | Change % | Status | Message |
|---|---|---|---|---|---|---|---|---|
| 2 | 200100 | FG-1001 | 0000184520 | 42.50 | 44.20 | 4 | Created | Condition record created; old record delimited on 30.11.2026 |
| 3 | 200245 | FG-1120 | 0000184521 | 62 | 64.50 | 4 | Created | Condition record created |
| 4 | FG-2050 | 57 | Error | Customer is mandatory for A305 |
How does the program work?
- The file is read; the condition table is chosen on the selection screen: A305 (customer/material) or A004 (material). The condition type must be defined in T685 for the sales application (KAPPL = V).
- Every row is checked: the customer exists in the sales area (KNVV), the material exists in the sales organization and distribution channel (MVKE), the amount is positive, currency and unit are valid and the start date is before the end date; if the same key appears twice in the file, the second row gets an error.
- The record valid today for the same key is read from A305/A004 and KONP; the old price and the change in percent are written to the result list.
- RV_CONDITION_COPY prepares the key, validity and KONP amount; the validity of an overlapping old record is delimited with the standard VK11 logic. The record is written to KONH, KONP and the condition table with RV_CONDITION_SAVE and COMMIT WORK; RV_CONDITION_RESET clears the buffer between rows.
- In test mode only the checks and the old price comparison run; no record is created. In a real run, the condition record number and message are listed per row; failed rows can be downloaded as a separate file.
Performance notes
Run price lists above a few thousand rows as a background job from a file on the application server. Read the old prices once for all keys in the file rather than row by row.
Features
- ALV list (sort, filter, subtotals)
- Test mode (check without posting)
- Line-by-line result and error log
- Download failed lines as a separate file
- Runs as a background job Large price lists can be loaded overnight from a file on the application server.
Authorization objects
- V_KONH_VKOAuthorization to create condition records by sales organization
- V_KONH_VKSAuthorization by condition type
Frequently asked questions
What happens to the old price record?
If the validity of the new record overlaps the old one, the old record's end date is moved to the day before the new start date, as in VK11. The old record is not deleted, so the price used on past invoices stays traceable.
Are other condition tables (e.g. customer group/material) supported?
Yes. The program can be built to read the condition table and key fields from a mapping table; each additional condition table adds its own key columns to the file template and raises the effort range slightly.
Does the program work on S/4HANA?
Yes. In S/4HANA condition records are still stored in KONH, KONP and the A tables (only document conditions moved from KONV to PRCD_ELEMENTS). In systems that use the Fiori 'Manage Prices – Sales' app, the same checks can also be applied to its file template.
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
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 …
Price and Quantity Differences Between Sales Order and Invoice Report
A custom ALV report that compares the invoiced unit price with the net price on the sales order, and the invoiced quantity with the delivered or …
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 program for your system
Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.