SAP Pricing Analysis Decoder
The pricing analysis already knows why a condition is missing; it just says it in a format that takes practice to read. Paste what it shows — condition type, then its access lines — and this page explains each outcome in plain terms and gives the check that settles it: the record in VK13, the key field that was empty, the requirement routine, or the exclusion that removed the condition. Nothing you paste leaves your browser.
Paste the pricing analysis
Open the document in VA03 or VF03, select the item, go to the Conditions tab and choose Analysis. Expand the condition type that is wrong and copy it with its access lines. You can also type it: one condition type per line, then the access results under it.
The five results that matter
Condition record is missing. The access ran with real key values and found nothing valid on the pricing date. Display the records in VK13 with exactly those values; a record that exists but starts tomorrow, or belongs to another distribution channel, is the usual surprise.
Access not made. One key field of the access was empty in the document, so the access was skipped without reading any record. This is a master-data problem far more often than a pricing one: a price group, price list or material pricing group that nobody filled.
Requirement not fulfilled. A routine on the procedure step or the access said no. Note the number from V/08 or V/07 and read it in VOFM; requirement 2 failing on an item category that is not pricing-relevant is the classic case.
Record exists but has not been set. The record was found but the condition did not take effect — condition exclusion picked a better value, or an earlier exclusive access already won.
Record found. Pricing worked as configured. If the amount is still wrong, the record itself is wrong: check its scales, calculation type and validity.
Before you change the procedure
Most pricing tickets are fixed in master data or condition records, not in V/08. Changing the pricing procedure affects every document that uses it, so treat it as the last step and test it on several document types. After any fix, re-price the existing document with Update → New pricing; old documents do not pick up new records on their own.
Related tools
If the billing document will not post because revenue account determination fails, use the account determination finder. For e-invoices rejected on tax amounts, run the e-invoice JSON validator.
The explanations reflect standard SD pricing behaviour. Custom requirement routines, condition types and user exits can change the outcome; check the routine itself before changing configuration. ERPClimb is an independent educational platform and is not affiliated with SAP SE.