Analytics Catalog/SAP S/4HANA/Sales and Distribution/Shipment costs
Explore the catalogModulesSales and DistributionPricing conditionsThe purchasing flow
SAP S/4HANA · Sales and Distribution · Report

What shipping really costs you

Freight is sold in one module and bought in another. May charged customers 18,400.00 and paid carriers 24,900.00, and the 6,500.00 between them exists only in the join, route by route, where it can finally be fixed.

RuleJoin freight charged to freight paid per route monthly, because the two sides land in different modules and the gap is a price list nobody reviews.
Neverread freight recovery from either module alone. Sales sees the charges, purchasing sees the carrier bills, and the loss lives in between.
18,400.00 charged freight on invoices 24,900.00 paid out the carrier settlements 6,500.00 under water the join nobody runs
Freight is sold in one module and bought in another. Only the join knows whether shipping earns or bleeds.
◆ May freight, both sidescharged, paid, and the gap.
Freight, May 2026Amount
Charged to customers, invoice conditions18,400.00
Paid to carriers, settled through purchasing-24,900.00
Freight under-recovery-6,500.00

The charged side sums the freight conditions the waterfall page shows per invoice; the paid side settles through service orders into the purchasing module’s flow. Neither module alone can see the 6,500.00. Sample values are illustrative, never client data.

◆ The price list nobody reviewsfreight charges age in place.

Customer freight charges live in condition records set at contract time, while carrier costs move with fuel and renegotiation. Practitioners report freight price lists untouched for years while costs walked away from them. The monthly join is the review that keeps the list honest.

◆ Route-level truthaverages hide the bleeders.

A single under-recovery number hides routes that earn against routes that bleed. Cut by route and customer, the join turns one awkward total into a short list of fixable prices.

Use case
Problem
Freight charges age in condition records while carrier costs climb, the two sides live in different modules, and shipping bleeds quietly.
What we build
Charged and paid joined monthly per route and customer, under-recovery trended, the charge list reviewed against real carrier costs.
What you get
Shipping that knows its own economics: the gap on one page, bleeding routes named, and a freight price list with a review date.
Is your freight charge list older than your carrier contracts?
We run the join and date both sides.
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.
freight condition
The charge line on the customer invoice.
carrier settlement
The cost side, paid through purchasing.
under-recovery
Charged minus paid, below zero.
route cut
The per-lane view that names the bleeders.