The price, taken apart

A price is a stack of decisions wearing one number. Unstacked, this invoice runs 24,000.00 of list through two discounts and freight to 21,950.00 net, and the manual-override flag on such rows is the margin story nobody trends.

RuleLand the condition lines behind every invoice, because the price is a stack of decisions and the stack is where margin leaks hide.

Neveranalyze margin from net prices alone. The net is the end of a negotiation; the conditions are the negotiation, and the manual ones are the tell.

A price is a stack of decisions wearing one number. Unstack it and the give-aways get names.

◆ One invoice, unstackedthe waterfall, exact.

Condition	Amount
List price, 60 units	24,000.00
Customer discount, contracted	-1,920.00
Promotion, campaign priced	-480.00
Freight, charged onward	350.00
Net, the invoice line	21,950.00

After the net	Amount
Output tax at eight percent	1,756.00
Invoice total	23,706.00

Every row is a condition line the document already carries; the page just refuses to let them collapse into one number. Aggregated by customer, the discount rows become the give-away ledger the margin page needs. Sample values are illustrative, never client data.

◆ The table that changed namesand the override that never trends.

S/4 moved condition lines to a new table, which breaks old extractors politely. The deeper miss is analytical: manually entered conditions, the overrides sales types in, are flagged on every line, and no delivered report trends them by rep or customer. The flag is the margin story.

◆ The owned answerconditions as a fact.

Condition lines land beside billing lines, so realized price waterfalls, give-away by customer, and manual-override trends are groupings. The one-invoice table above becomes every invoice, summed.

Use case

Problem

Margin analysis starts from nets, give-aways hide inside one number, manual overrides trend nowhere, and the old condition extractor broke at conversion.

What we build

Condition lines landed as a fact beside billing: waterfalls per invoice, give-away ledgers per customer, override flags trended per rep.

What you get

Pricing with its decisions visible: discounts that answer for themselves, overrides with patterns, and margin analysis that starts where the negotiation did.

Who gave away the most list price last quarter?

We land the conditions 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.
condition line: One priced decision: list, discount, freight, tax.
PRCD_ELEMENTS: The S/4 condition table; the rename that broke extractors.
manual condition: A typed-in override; flagged on the line, trended nowhere.
waterfall: List to net, decision by decision.