Tiered Weight-Break Pricing with Rate Tables and Scales in SAP TM

Tiered Weight-Break Pricing with Rate Tables and Scales in SAP TM

Almost every road and LTL carrier contract we have loaded into SAP TM had the same structure: a price per kilogram that drops as the shipment gets heavier, a minimum charge per consignment, and an unwritten rule that the carrier never bills more than the next weight break would cost. On paper it is a simple tariff. In the system it becomes a rate table with a weight scale, a calculation method, a minimum amount and a rounding rule, and each of those is a separate setting that someone can get wrong.

Projects rarely get stuck building the rate table. They get stuck when the business compares freight order charges with carrier invoices and finds gaps just below weight breaks, or a minimum charge that never applies. Here is how we model it and prove it before go-live.

Step 1 – Translate the carrier tariff into a scale design

Before opening any screen, rewrite the carrier tariff as a table with three columns: weight break, rate, and unit. A typical example we will use throughout this article:

Gross weight from Rate (EUR per kg)
0 kg 2.00
100 kg 1.80
500 kg 1.50
1,000 kg 1.20

Minimum charge: EUR 75.00 per freight order. Charges rounded to two decimals.

Then answer three questions with the carrier or the procurement team, in writing:

  • Is the break inclusive? Does exactly 100 kg get 2.00 or 1.80? This decides the scale type.
  • Does the whole weight get the band rate, or only the part inside each band? This decides Standard versus Clipping.
  • Does the carrier charge the lower of “actual weight at its rate” and “next break at its rate”? This decides whether you need Break-weight.

The third question is the one nobody asks, and it causes most invoice differences.

Step 2 – Check the scale base and calculation base

The weight scale needs a scale base that reads gross weight from the document. Standard content usually delivers one; check its binding anyway.

Customizing path (labels vary slightly between SAP TM 9.x and S/4HANA, verify in your release):

  • SPRO > Transportation Management > Basic Functions > Charge Calculation > Data Source Binding for Charge Calculation > Define Calculation Bases
  • Same node > Define Scale Bases

What to check in the scale base entry:

  • It points to gross weight, not net weight or volume.
  • The dimension is mass and KG converts from the units your freight units carry (test tonnes or pounds explicitly).
  • For a per-consignment tariff, the weight is the freight order total, not one value per item.

Step 3 – Build the rate table with the right scale type

Create the rate table with one dimension: the gross weight scale. On the scale, the scale type controls how a weight is matched to a scale item:

Scale type Meaning Use it when
Base scale (from, >=) Item value is the lower limit of the band The tariff reads “from 100 kg”
To scale (<=) Item value is the upper limit of the band The tariff reads “up to 100 kg”
Same scale (=) Exact match only Discrete values (number of pallets, equipment type), not weight bands

For our tariff, a base scale with items 0, 100, 500 and 1,000 kg is the direct translation. A to-scale version needs items like 99.999 and 499.999, which is harder to read. Match how the carrier writes the contract.

Set the calculation type of the rate to relative (rate per scale unit, EUR per KG), not absolute. An absolute rate gives you a flat amount per band, which is correct for “0–100 kg: EUR 150 flat” tariffs but wrong for per-kilogram pricing.

Pitfall

Break-weight logic and Same scale do not combine. If you see a charge calculation message saying break-weight logic was requested with scale type “Same Scale”, the scale type is the problem, not the rates.

Step 4 – Choose the calculation method: Standard, Clipping or Break-weight

This is where the tiered behavior actually lives. Using the tariff above, here is what each method returns:

Method Logic 95 kg 450 kg
Standard Whole weight at the rate of the band it falls in 95 x 2.00 = 190.00 450 x 1.80 = 810.00
Clipping Each slice of weight at its own band rate 95 x 2.00 = 190.00 100 x 2.00 + 350 x 1.80 = 830.00
Break-weight Lower of Standard and “next break weight at next rate” min(190.00, 100 x 1.80) = 180.00 min(810.00, 500 x 1.50) = 750.00

Many LTL tariffs behave like Break-weight even when the contract does not use the word. If you configure Standard for a break-weight carrier, shipments just below a break are overcharged, which is exactly the gap the invoice check finds.

How to activate it

In the releases we have worked with, two things must be set together: the rate table scale must be flagged as relevant for the calculation method (the “relevant for calculation method” checkbox on the weight scale), and the calculation sheet item that uses this rate table must carry the calculation method Break-weight or Clipping. One of the scales in the rate table must be the weight scale for Break-weight and Clipping to apply. The exact field labels and whether the method sits on the item or on the rate differ by release, so verify in your release before documenting the procedure for key users.

Step 5 – Minimum charge and rounding

Minimum charge

There are two places where a minimum can be modelled, and they behave differently:

  • On the calculation sheet item (minimum amount field): applies to the result of the item, after the rate table is evaluated. This is what you want for “EUR 75 minimum per consignment”. A 30 kg shipment gives 30 x 2.00 = 60.00, and the item returns 75.00.
  • On the rate table values (minimum per scale item, where your release offers it): applies per band and is useful when each band has its own floor.

We have seen minimum amounts silently ignored when they were maintained on the rate table and the scale type or calculation type did not match what the minimum logic expects. SAP documentation for different releases is not consistent on whether a minimum can be combined with a rate table on the same item, so treat this as verify in your release and test it with a shipment that is clearly below the minimum.

Rounding

Carriers usually round the final amount, not the rate. Keep rates at contract precision and round the charge result through the rounding settings in charge calculation customizing (verify the node name in your release). Rounding the weight itself, for example to the next 10 kg, must be agreed with the carrier because it moves shipments across breaks.

Step 6 – Test with the charge calculation log

Do not sign off a tariff by looking at the total on the Charges tab. Recalculate charges on a test freight order and open the charge calculation log or analysis from the Charges tab (the button name and whether a user parameter is needed to activate detailed logging depend on the release, verify in your release). For each item, the log shows the agreement and calculation sheet found, the rate table, the scale item selected, the calculation base value, and the resulting amount.

Build a test matrix around the breaks, not around typical shipments:

Test weight Expected (Break-weight) What it proves
30 kg 75.00 Minimum charge applies
95 kg 180.00 Next-break comparison works
100 kg 180.00 Break is inclusive (base scale)
450 kg 750.00 Break-weight wins over Standard
480 kg 750.00 Shipment billed at next break
1,250 kg 1,500.00 Last band, open upper end
Weight in tonnes Same as KG equivalent Unit conversion

If the log shows the right scale item but the wrong amount, look at the calculation method and calculation type. If it shows the wrong scale item, look at the scale type and the scale base binding. If the minimum is missing, check where it is maintained.

Step 7 – Keep it maintainable

  • Use validity periods on the rate table for yearly tariff changes instead of editing values in place, so freight settlement documents of last year still recalculate correctly.
  • Load large tariffs with the rate table Excel upload and keep the file as audit trail.
  • Document the three answers from Step 1 in the agreement description so the next consultant does not have to reverse-engineer them.

Takeaways

  • Tiered pricing in SAP TM is the combination of scale base, scale type, calculation type, calculation method and minimum, and each one must match the carrier contract.
  • Ask the carrier explicitly whether they apply break-weight logic; Standard and Break-weight differ exactly on the shipments the business checks first.
  • Model the per-consignment minimum on the calculation sheet item and prove it with a test below the minimum.
  • Test around the breaks with the charge calculation log before go-live, not with average shipments.

How do your carriers handle weight breaks, and have you seen other combinations in practice? Let me know in the comments.

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *