The discounts typed in by hand

The override marker is decades old and summed nowhere. May’s one group-by answers it: 41 of 310 lines priced by hand, 28,400.00 given away, names attached.

RuleTrend the manual-price flag by rep and customer monthly, because every override is flagged at the line and no delivered report has ever added them up.

Nevertreat overrides as noise in the waterfall. They are the negotiation happening outside the price list, and outside the review.

The override flag has sat on every condition line for decades. This page is what happens when someone finally sums it.

◆ May overrides, by repthe flag, finally summed.

Entered by	Overridden lines
Rep A, direct accounts	19
Rep B, distributor desk	14
Other entry users	8
Manual prices, of 310 lines, giving away 28,400.00	41

The flag is on every condition the waterfall page lands, so this page is one filter and one sum. The give-away is measured against the list the margin page starts from, which is why the two read together. Sample values are illustrative, never client data.

◆ The field nobody sumsdecades of flagged silence.

Manually entered conditions carry their marker at the line, and no delivered report aggregates it: not by rep, not by customer, not over time. Practitioners discover the override rate the first time the landed conditions get one group-by, and the number starts conversations pricing committees thought were settled.

◆ Policy, not prohibitionoverrides with daylight.

Some overrides win deals worth winning. The control is daylight, not a ban: a monthly trend by rep, a threshold that routes big ones for approval, and a give-away number beside every quota conversation.

Use case

Problem

Overrides hide inside net prices, the flag that marks them sums nowhere, and pricing policy argues from anecdotes.

What we build

The manual flag aggregated monthly by rep and customer, give-away valued against list, thresholds routing the big ones for sign-off.

What you get

Negotiation with daylight: an override rate on one page, give-away beside quotas, and pricing reviews that argue from the ledger.

What did manual pricing cost you last quarter?

We sum the flag nobody sums and name the number.

Talk to us

Terms on this page

SAP: The vendor. Systems, Applications, and Products in data processing.
HANA: SAP’s in-memory database, the platform S/4 runs on.
SD: Sales and Distribution, the order-to-cash module.
manual price: A condition typed over the list at order entry.
the flag: The line-level marker delivered reports never aggregate.
give-away: List minus entered, summed where flagged.
threshold routing: Big overrides detour for approval; small ones trend.