All topics
TMbeginner

Charge Calculation

Charge Calculation in SAP Transportation Management determines freight costs and revenues for forwarding and shipper scenarios by applying calculation sheets, rate tables, scales, and agreements to freight orders, freight bookings, and forwarding orders, forming the financial backbone that feeds settlement, billing, and cost distribution to SD/FI/EWM.

Overview

Charge Calculation in SAP Transportation Management determines freight costs and revenues for forwarding and shipper scenarios by applying calculation sheets, rate tables, scales, and agreements to freight orders, freight bookings, and forwarding orders, forming the financial backbone that feeds settlement, billing, and cost distribution to SD/FI/EWM.

Lessons in this topic

Interview questions covered

  • A carrier connected via SAP Business Network for Logistics reports execution statuses that update the freight order in real time, but freight charge calculation is producing outdated amounts because it references planned data instead of the newly received actual execution attributes. How would you investigate and correct this?
  • Walk through the end-to-end process of how tax is determined and validated when a supplier invoice for freight charges moves through the Freight-to-Settle process into MM-LIV.
  • A production support ticket reports that transportation cost allocations posted through MM-LIV for a subcontracted freight service are hitting the wrong cost center, but only for freight orders created after a recent charge calculation profile change. How would you investigate and resolve this?
  • A carrier invoice is processed and the Freight Settlement Document posts correctly to FI, but the corresponding SD customer billing document for the same shipment reflects a different freight charge amount because a calculation sheet override was applied only on the carrier settlement side. As solution architect, how would you diagnose the mismatch and prevent recurrence?
  • A finance team complains that freight charges calculated in TM don't match expected GL postings after settlement, and they suspect the charge profile configuration is misaligned with FI cost element mapping. How would you investigate the charge profile setup causing this discrepancy?
  • A forwarding settlement document splits a single shipment's charges across multiple cost centers based on a percentage distribution rule, but production support finds that one cost center consistently receives zero allocation even though the distribution percentages sum to 100%. How would you troubleshoot this?
  • When Service Purchase Orders are generated from freight agreements in S/4HANA TM, how do you configure cost distribution so transportation charges post correctly across multiple cost objects while remaining consistent with SD-Billing revenue recognition?
  • During quarter-end reconciliation, tax amounts posted from forwarding settlement documents to FI do not match the tax reported by the tax engine used during charge calculation for cross-border shipments. How would you approach identifying and resolving the discrepancy?
  • In S/4HANA Transportation Management, what role does the Charge Calculation Sheet play in determining how a calculated charge type is ultimately account-assigned when it posts to FI during transportation cost allocation?
  • A carrier invoice processing scenario shows that charges pulled from a scale-based rate table are being cost-distributed incorrectly, causing the recovered freight revenue posted through SD-Billing to no longer match the transportation cost allocated in TM. How would you investigate and correct this?
  • In SAP TM, what is a freight agreement and how does it relate to charge calculation during the freight-to-settle process?
  • In S/4HANA TM, forwarding settlement documents post correctly to the leading ledger, but after activating parallel accounting for a new company code, certain charge types generate incomplete postings in the non-leading ledger. As the architect, how would you diagnose and resolve this?
  • A global freight settlement rollout is producing incorrect tax amounts on cross-border carrier invoices due to charge type tax classification mismatches. As the solution architect, how would you diagnose and design a fix?
  • A customer on S/4HANA Public Cloud needs custom freight rate logic that reacts to warehouse task completion data from EWM. How would you design this without violating clean-core principles?
  • A freight order's charge calculation depends on actual weight captured at a goods issue event in MM, but a warehouse system delay means the MM goods movement event arrives hours after the freight order's Event Management milestone marks the shipment as departed, causing charge calculation to run on estimated weight. How would you redesign the process to fix this?
  • A carrier updates its rate card through SAP Business Network for Logistics mid-transit, and the freight order's charge calculation reflects the old rate at settlement time, leading to a dispute with the carrier. How would you diagnose and correct the charge calculation integration?
  • A forwarding customer disputes a freight settlement invoice, claiming certain calculation sheet charges were duplicated across two cost distribution categories. How would you investigate and resolve this in the calculation sheet configuration?
  • Design a freight costing and settlement architecture where charge calculation results must feed into an SD billing document for customer freight pass-through, while also supporting independent carrier payable settlement, across multiple freight order types with different cost structures. What key architectural decisions must be made?
  • What configuration is required to ensure freight charge profiles correctly calculate and settle carrier charges when execution status updates arrive from SAP Business Network for Logistics (BN4L)?
  • Your organization is redesigning the freight-to-settle process so that charge calculation results are visible to FI as accruals within hours of freight order completion, rather than waiting for the periodic settlement run. What architectural changes to charge management and settlement scheduling would you propose to achieve near-real-time FI visibility without disrupting existing settlement document consolidation logic?

Related topics