SD Program Custom development Mass upload

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

  • VK11 Create Condition. Creates or copies condition records one at a time; does not load from a file.
  • VK13 Display Condition. Displays existing condition records; no comparison with new prices and no upload.

Tables used

The tables the program reads and updates. ECC and S/4HANA differences are marked separately.

TableRoleAccessSystem
T685Condition TypesCondition type check (sales application)ReadECC + S/4
KNVVCustomer Master Sales DataCheck that the customer exists in the sales areaReadECC + S/4
MVKESales Data for MaterialCheck that the material exists in the sales organization and distribution channelReadECC + S/4
A305Condition Table: Customer/Material with Release StatusCustomer/material condition table: the old record is read, the new key and validity are writtenRead / writeECC + S/4
A004Condition Table: MaterialMaterial condition table (when price per material is selected)Read / writeECC + S/4
KONHConditions (Header)Condition record headerWriteECC + S/4
KONPConditions (Item)Condition amount, currency, price unit and unit of measureRead / writeECC + 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

ParameterDescriptionTypeReference fieldRequiredExample
P_FILEPrice list file (XLSX or CSV)Single value—YesC:\temp\fiyat-listesi-2027.xlsx
P_KSCHLCondition typeSingle valueA305-KSCHLYesPR00
R_A305Customer/material price (A305)Radio button—NoX
R_A004Material price (A004)Radio button—No—
P_TESTTest mode (check without saving)Checkbox—NoX

Input file columns

The columns of the upload template and the SAP fields they are written to. Columns with an asterisk are mandatory.

#ColumnTarget fieldRequired
1Sales organizationA305-VKORGYes
2Distribution channelA305-VTWEGYes
3Customer (mandatory for A305)A305-KUNNRNo
4MaterialA305-MATNRYes
5AmountKONP-KBETRYes
6CurrencyKONP-KONWAYes
7Price unitKONP-KPEINNo
8Unit of measureKONP-KMEINNo
9Valid fromA305-DATABYes
10Valid toA305-DATBIYes

Sample upload file

1Sales organization *Distribution channel *Customer (mandatory for A305)Material *Amount *Currency *Price unitUnit of measureValid from *Valid to *
2100010200100FG-100144.20TRY1CS12/01/202606/30/2027
3100010200245FG-112064.50TRY1CS12/01/202606/30/2027
4100010FG-205057TRY1PC12/01/202612/31/9999
A view built with fictional sample data; not real system data.

Result list columns

#ColumnSource
1RowCalculated Row number in the file
2CustomerA305-KUNNR
3MaterialA305-MATNR
4Condition recordKONH-KNUMH
5Old priceCalculated KONP-KBETR of the record valid today
6New priceKONP-KBETR
7Change %Calculated (New price − old price) ÷ old price × 100
8StatusCalculated Created, test OK or error
9MessageCalculated Check or save message

Sample result list

RowCustomerMaterialCondition recordOld priceNew priceChange %StatusMessage
2200100FG-1001000018452042.5044.204CreatedCondition record created; old record delimited on 30.11.2026
3200245FG-112000001845216264.504CreatedCondition record created
4FG-205057ErrorCustomer is mandatory for A305
A view built with fictional sample data; not real system data.

How does the program work?

  1. 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).
  2. 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.
  3. 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.
  4. 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.
  5. 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

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 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 program 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: Mass Sales Price Condition Upload from Excel Program