VKP2Retail

SAP VKP2 — Display POS Conditions

In SAP Retail the price a customer pays at the till is not typed onto a sales order. It is stored in advance as a condition record against an article and a site, and pushed out to the point-of-sale system. VKP2 displays those records.

They are produced by the sales price calculation (VKP0 and the rest of the VKP family), which takes the purchase price, applies a markup or a competitive target, and arrives at a sales price. VKP2 is the read-only view of the result.

This distinction matters when a store reports the wrong price on the shelf. There are three separate things that could be wrong: the calculation that produced the price, the condition record it wrote, or the transmission of that record to the till. VKP2 tells you which of the three you are dealing with — if the condition here is right, the problem is transmission, and you move to WPER.

When you would actually use VKP2

What the screen looks like

Display POS Conditions
VKP2

Selection

Article000000000004182
SiteST01
Sales organisation1000
Distribution channel10
Valid on03.08.2026
The "Valid on" date matters — conditions are time-dependent, so a promotion may be live tomorrow but not today.
Client 100 | S/4HANA | Company Code 1000
Illustrative recreation.Article plus site is the key: the same article can be a different price in every store — Drawn for training with invented data; not a capture of a real SAP system. Fields with a blue border are required. SAP is a trademark of SAP SE.
Display POS Conditions: Result
VKP2
ArticleSiteCond. typeAmountCurrencyValid fromValid to
4182ST01VKP019.90EUR01.01.202631.07.2026
4182ST01VKP014.90EUR01.08.202614.08.2026
4182ST02VKP019.90EUR01.01.202631.12.2026
Promotional price 14.90 EUR active at ST01 until 14.08.2026
Client 100 | S/4HANA | Company Code 1000
Illustrative recreation.Two records for the same article and site, separated by validity date — Drawn for training with invented data; not a capture of a real SAP system. Fields with a blue border are required. SAP is a trademark of SAP SE.

The fields, in plain English

ArticleMARA-MATNR

The article whose prices you want to see. For a generic article you normally need the variant, since prices attach to the sellable unit.

Watch out: Leading zeros again. If a search finds nothing, try the zero-padded form.

SiteT001W-WERKS

The store or distribution centre. Retail prices are set per site, so the same article legitimately costs different amounts in different stores.

Watch out: A price that looks wrong is often correct for that site and wrong for the one the caller is thinking of. Confirm the site first.

Condition type

Which kind of price the record holds. VKP0 is the standard sales price condition; promotional and competitor prices use their own condition types.

Valid from / Valid to

The period the record applies to. Records overlap in the list but only one applies on any given date, which is how promotions replace base prices and then hand back.

Watch out: A promotion that "will not end" is usually a validity date, not a stuck till. Check whether the base-price record actually resumes after the promotional one stops.

Sales organisation / Distribution channel

The sales-side keys the condition is stored against, alongside article and site. If they do not match how the store is set up in WB03, no condition will be found.

Step by step

  1. 1Enter the article and the specific site the complaint came from.
  2. 2Set "Valid on" to the date in question, not today, if you are investigating something historic.
  3. 3Execute and read the condition records with their validity periods.
  4. 4Compare the amount against what the till charged.
  5. 5If SAP holds the right price, the problem is transmission — go to WPER to see whether the price reached the store.
  6. 6If SAP holds the wrong price, the problem is upstream in the sales price calculation.

Errors you will hit, and what they mean

No conditions found for this article and site

Why: No sales price has been calculated for that combination, or the article is not listed at that site.

Fix: Check listing in MM43 first — an unlisted article will not have prices. Then check whether the price calculation has been run for that site.

The price shown differs from the price at the till

Why: The condition exists but was never transmitted, or the till is running an older price file.

Fix: Check the POS interface in WPER for that store and date. This is transmission, not pricing.

A promotional price is still active after the promotion ended

Why: The validity dates on the promotional record, or a missing follow-on base-price record.

Fix: Look at the validity periods here. If the promotion has genuinely expired in SAP, the problem is again transmission.

Common questions

What is the difference between VKP2 and VKP0?

VKP0 is the sales price calculation — it works the price out. VKP2 displays the resulting POS conditions. Calculation versus result.

Why is the same article a different price in two stores?

That is normal in Retail. Conditions are held per site, so pricing can vary by store, region or competitive situation.

The price is right here but wrong in the shop. What now?

Transmission. The condition is correct in SAP but has not reached the point of sale. WPER monitors that interface.

Transactions that go with VKP2

MM43Check the article is listed at the site firstWPERSee whether the price reached the storeWB03Confirm the site's sales organisation setup

Reading about it only gets you so far

Practise SAP transactions in a safe simulated environment and keep what you learn.

See the SAP games →Study the full module

Practise SAP transactions hands-on

Interactive modules, games, and an AI tutor — free to start.

Get started free →