SD Pricing Part 3: Condition Types and the Pricing Procedure

📌 KEY POINTS
✅ Condition type (V/06) defines behavior: class (price, discount/surcharge, tax), calculation type (percentage, fixed amount, quantity-based), plus/minus, manual changes, header/item, scales.
✅ Pricing procedure (V/08) orders condition types with step/counter and adds rules: from/to base, manual, required, statistical, subtotal, requirement, alternative calculation, account key.
✅ Account keys (ERL revenue, ERS sales deductions, ERF freight, MWS tax) link pricing to revenue account determination (VKOA).
✅ OVKK assigns the procedure per sales area, document pricing procedure and customer pricing procedure.
⚠️ A condition type in the procedure without "required" can be missing silently — mark the price as required.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 2 explained price finding. Now the condition types and the procedure that combines them.

━━━━━━━━━━━━━━━━━━━━
▶ 1. CONDITION TYPE CONTROL

• Access sequence, condition class (A discount/surcharge, B price, D tax).
• Calculation type: A percentage, B fixed amount, C quantity.
• Plus/minus (only negative for discounts), rounding rule.
• Manual entries priority, changeable amount/percent, delete allowed.
• Header condition / item condition, group condition, scales.

━━━━━━━━━━━━━━━━━━━━
▶ 2. PROCEDURE COLUMNS

• Step/counter: sequence.
• From/to: base for percentages (e.g. discount on gross).
• Manual: only entered manually; required: must exist; statistical: not in net value.
• Print, subtotal (to fields like KZWI1–6), requirement, alt. calc type, alt. base value.
• Account key and accrual key.

━━━━━━━━━━━━━━━━━━━━
▶ 3. TYPICAL STRUCTURE

• Price → gross value subtotal.
• Discounts → net value subtotal.
• Freight → surcharges.
• Tax on net + freight.
• Statistical: cost (VPRS), cash discount.

━━━━━━━━━━━━━━━━━━━━
▶ 4. PROCEDURE DETERMINATION

• OVKK: sales area + document pricing procedure + customer pricing procedure → procedure + condition type for display (e.g. price).

━━━━━━━━━━━━━━━━━━━━
▶ 5. CHANGES AND IMPACT

• Changing a procedure affects new pricing; existing documents keep their conditions until repriced.
• Account key changes affect revenue postings → coordinate with finance.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

1. Copy standard condition types to Z where behavior must differ.
2. Copy the standard procedure to Z and adjust steps.
3. Mark price required, set subtotals and account keys.
4. Maintain OVKK.
5. Test pricing and posting (billing → accounting).

✅ CHECKPOINT: an order shows gross, discounts, net, freight, tax and cost in the expected steps, and billing posts to the right accounts.

After a pricing procedure redesign, finance noticed customer discounts posting to the revenue account instead of the sales deductions account. The new discount condition type had been added without account key ERS. Revenue and deductions were misstated for a month. The team added ERS, corrected the postings with finance, and added a procedure review checklist including account keys and a billing-to-accounting test for every new condition type.

• Forgetting account keys for new condition types.
• Not marking the main price as required.
• Wrong from/to ranges for percentage discounts.
• Changing standard condition types instead of copying.
• Adding statistical conditions to net value.

• Keep pricing procedures few and well documented.
• Always set required on the price and account keys on revenue-relevant conditions.
• Test pricing through billing and accounting.
• Copy standard objects to Z.
• Review procedure changes with finance.

Questions: "Which settings do you maintain in a condition type?", "Explain the pricing procedure columns", "How is pricing linked to FI?"
Strong answer: condition class, calculation type, plus/minus, manual, header/item, scales in V/06; step, counter, from/to, manual, required, statistical, subtotal, requirement, alt calc, account key in V/08; OVKK determination; account keys to VKOA revenue account determination.