Analytics Catalog/SAP S/4HANA/Sales and Distribution/Margin by customer
Explore the catalogModulesSales and DistributionBilling registerThe valuation diary
SAP S/4HANA · Sales and Distribution · Report

What each customer really earns you

Margin is two moving numbers pretending to be one. May’s 1,858,000.00 of net revenue meets 1,454,900.00 of issue-dated cost, and the 403,100.00 between them cuts by customer without rotting, because every credit kept its reference.

RuleCompute margin from referenced documents end to end, because revenue without its credits and cost at a moving average are both numbers that change behind you.
Nevertrust a margin whose cost side you did not date. The warehouse repriced during the month, and margin moved with it while sales were looking elsewhere.
1,858,000.00 net the register, partitioned Cost at the average dated, from the diary 403,100.00 margin 21.7%, by customer
Margin is two moving numbers pretending to be one. Date both sides and the pretense becomes analysis.
◆ May margin, by customerfour rows, both sides dated.
CustomerNet revenueCostMarginMargin %
Meridian Retail684,200.00512,300.00171,900.0025.1
Harbor Industrial575,800.00448,900.00126,900.0022.0
Crest Distribution391,400.00322,500.0068,900.0017.6
Smaller accounts206,600.00171,200.0035,400.0017.1
May margin1,858,000.001,454,900.00403,100.0021.7

The revenue column is the register’s net, partitioned: credits included because their references held. Cost is the issue quantity at the day’s moving average, which is why the valuation diary matters to a sales page. Sample values are illustrative, never client data.

◆ Margin that moves without sales movingthe cost side reprices.

Cost of goods reads the moving average at issue time, so a warehouse reprice shifts margin on sales that were already made. Practitioners report margin reviews chasing discounts when the mover was the average. Dating both sides splits the bridge into price, cost, and mix honestly.

◆ The migration woundhistory that lost its cost side.

Margin history across a migration breaks when old cost bases do not carry: the editorial page walks the failure. The owned model lands cost with every billing line at posting time, so history keeps its own cost side forever.

Use case
Problem
Margin by customer rots through unreferenced credits, moves when the warehouse reprices, and loses its history at every migration.
What we build
Margin computed from referenced documents with cost dated at issue: customer cuts, price-cost-mix bridges, history that keeps its cost side.
What you get
A margin number sales and finance share: credits inside, cost dated, repricing visible as its own bridge line, and history that survives platforms.
Did discounts or repricing move your margin last quarter?
We build the bridge that answers in one row each.
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.
net revenue
Invoices less referenced credits plus debits.
moving average
The cost price at issue time; it moves, so date it.
margin bridge
Price, cost, and mix explaining the change.
referenced credit
A credit that knows its invoice; margin’s lifeline.