Pricing & Condition Approval Workflow
Protect discounts and special prices from unauthorized change — embed margin discipline in the system.
What problem does it solve?
Sales prices and discount conditions are changed without control; unauthorized discounts quietly erode margin and pricing policy can't be enforced.
How does the solution work?
Conforcus's pricing & condition approval workflow routes changes on price and discount condition records to approval by threshold and authority, and won't activate the condition until released. The deviation rate is shown to the approver.
What changes in practice?
The control sits in condition record maintenance. When a price or discount condition is created or changed (VK11/VK12), the change is compared against rule tables based on condition type and threshold. Changes that stay within the user's authority and the defined threshold are saved in the usual way; those that exceed it are routed to the approval workflow. With activation control, the condition does not become active until it is approved, so an unapproved price or discount does not enter pricing in sales documents. The approver sees the change together with its deviation rate and decides with that rate in view.
The pricing team keeps maintaining conditions in the transactions it already uses; routine updates do not wait, and only discounts and price deviations above the threshold go to approval. Each exception is documented with who requested it and who approved it and when, so where discount authority lies is clearly on record. Because thresholds are kept per condition type in rule tables, a change in pricing policy means updating table entries. Margin control rests on the system at the moment of sale rather than on a report read after invoicing, and the pricing policy is applied consistently.
Benefits
- Unauthorized discounts and price deviations are blocked before they go live
- Pricing policy is applied consistently; exceptions are documented and approved
- Margin control is enforced in the system at sale time, not in a report afterward
Where it sits in SAP
Change triggering on condition records (VK11/VK12) and the pricing procedure, condition-type and threshold-based rule tables, approval workflow and activation control. Live across multiple sectors.
Who it is for: Sales Director, Pricing Lead, CFO (margin control)
Frequently asked questions
Which condition types enter approval: only discounts, or prices as well?
Scope is defined per condition type, so price and discount conditions can each be bound to approval separately. For every condition type, the threshold and the approval authority are defined in rule tables. Changes that stay below the threshold are saved without approval, so routine condition maintenance does not slow down.
What does the approver see when deciding, and how is the deviation assessed?
The approver sees the change requested on the condition record together with its deviation rate. Which deviation requires approval is defined in the rule tables through thresholds per condition type, set according to the company's pricing policy. Since the condition does not become active without approval, the decision is taken before the price or discount reaches a sale.
Can a price or discount awaiting approval be used on orders, and what happens if it is rejected?
No; the condition does not become active until it is approved, so an unapproved price or discount does not reach sales documents. A rejected change stays inactive, and the requester can correct the value and submit it again. Approved exceptions are kept on record with who approved them and when, so deviations from pricing policy can be traced afterwards.