ERPClimb logoERPClimb

SAP TM Freight Units Interview Questions

In SAP TM rounds, freight units questions are where configuration knowledge meets day-to-day behaviour — what a setting does, and what breaks in a live system when it is wrong.

This page carries 25 reviewed SAP TM freight units interview questions, each with a complete written answer and no sign-in required. The set breaks down into 5 foundational, 5 mid-level and 15 advanced questions, so you can start at the top for a first interview or skip ahead to the scenario-based items for a senior round.

Rehearse these out loud rather than reading them. If you can explain each answer in your own words, including one realistic way it goes wrong on a project, you are covering what a normal SAP TM round on freight units expects.

25 Freight Units questions with answers

easyFreight Units

1. What sustainability-related information can be captured and evaluated in SAP TM freight unit planning, and how does it factor into transportation decisions?

SAP TM can calculate and display CO2 emissions at the freight unit, stage, and transportation activity level using the Carbon Emissions calculation engine, based on distance, weight, mode of transport, and emission factors maintained in Customizing. Planners can view emission values in the Transportation Cockpit and use them as an additional decision criterion alongside cost and capacity, though emissions are typically informational rather than a hard optimizer constraint in standard planning.
easyFreight Units

2. What is Load Planning in SAP TM, and how does it relate to Freight Unit building for orders originating from SD sales orders?

Load Planning in TM assigns freight units to vehicle resources or transportation units, determining how cargo is arranged within capacity limits (weight, volume, HU stacking). It follows freight unit building, where FUs are created from SD sales orders based on FU building rules. Load planning can be manual in the Transportation Cockpit or automated via the optimizer, and it produces load plans that feed shipment execution and loading instructions.
easyFreight Units

3. In S/4HANA embedded TM, what is order-based transportation consolidation and how does it relate to freight units and shipment planning?

Order-based transportation consolidation groups multiple sales or purchase orders into a single freight unit and subsequently into a shipment/freight order for planning. It leverages TM's freight unit building rules to combine deliveries or orders by criteria like route, destination, and dates, enabling better truck utilization, fewer shipments, and lower freight cost before execution and EWM handoff.
easyFreight Units

4. What is a Freight Unit (FU) in SAP TM, and what triggers its automatic creation when an SD sales order generates a transportation requirement?

A Freight Unit is the atomic planning object in TM representing the quantity, weight, volume, and dates that must move between a source and destination location; it carries incompatibilities, equipment requirements, and scheduling data used by the optimizer and cockpit. Automatic creation is triggered when the SD order/delivery is released to TM as an Order/Delivery-Based Transportation Requirement, and an FU building rule evaluates item category, transportation group, and split/merge settings to generate one or more FUs.
easyFreight Units

5. In SAP TM, what is the difference between splitting and merging freight units, and at what stage of transportation planning does each typically occur?

Splitting breaks a single freight unit into multiple FUs when the demand quantity exceeds vehicle resource capacity, incompatibility rules, or FU building rule limits, typically during freight unit building. Merging combines multiple compatible FUs (same source/destination, compatible dates, and characteristics) into one planning unit to enable load consolidation, usually during manual planning or optimizer execution. Both actions are governed by the FU building rule, planning profile settings, and can be manually overridden in the TM planning cockpit.
mediumFreight Units

6. A customer complains that hazardous and non-hazardous deliveries are being merged into a single freight unit despite regulatory restrictions. How would you diagnose and resolve this using FU building rules and incompatibilities?

I would first check the freight unit building rule's split/merge settings and the incompatibility Customizing to see if a hazmat incompatibility group is defined and assigned to the relevant material/delivery item attributes. If missing, I'd configure an incompatibility definition (e.g., based on hazard class fields) and link it to the FU building rule so that items with conflicting hazmat classifications cannot be consolidated into one freight unit, then retest with representative deliveries and validate against the incompatibility check log.
mediumFreight Units

7. A logistics team notices that deliveries containing hazardous materials and food-grade products are being consolidated into the same freight unit during Delivery-Based Transportation Requirement processing, violating compliance rules. How would you address this using incompatibility settings?

I would configure incompatibility definitions in TM customizing to prevent consolidation of hazardous and food-grade items, using product hierarchy or handling-type attributes as the incompatibility criteria. These are attached to the freight unit building rule set so the system splits or blocks combination during DTR-to-freight-unit conversion. I would also verify GIS-based routing constraints for hazmat aren't overridden by consolidation logic, and test using representative delivery combinations before go-live.
mediumFreight Units

8. How would you configure TM optimizer settings to align freight unit capacity planning with demand signals received from SAP IBP for accurate load building in an integrated order-to-freight process?

I would keep IBP demand as a planning-level input feeding forecast-driven transportation requirements, while ensuring the TM optimizer's capacity planning profile uses realistic vehicle resource and time-window parameters aligned to the IBP planning horizon. Optimizer strategy profiles should reference the same scheduling buffers used for actual order-based FUs, and integration timing must ensure IBP-driven planned quantities don't double-count capacity once real sales orders replace them.
mediumFreight Units

9. A single freight unit needs to be split because part of the order requires hazardous material handling incompatible with the rest of the shipment, while later a merge is needed once compliant transport is arranged. How would you manage this split-and-merge scenario in TM, including incompatibility handling?

Split the freight unit manually or via a split rule so the hazardous portion becomes a separate freight unit with its own incompatibility attributes (hazmat class) that prevent it from being combined with incompatible freight units during planning. Once appropriate compliant transport (e.g., ADR-certified carrier/equipment) is arranged, the split freight units can be merged back if business rules allow, or planned separately into distinct freight orders. Incompatibility rules configured against hazmat classification ensure the optimizer or manual planner cannot combine hazardous and non-hazardous freight inappropriately at any stage.
mediumFreight Units

10. After cutover, sales orders are no longer consolidating correctly into freight units through Order-Based Transportation Consolidation (OBTC), causing fragmented shipments compared to pre-migration behavior. How would you investigate and correct this?

Check whether OBTC-relevant configuration such as consolidation grouping criteria, incoterms, and planning profiles were migrated consistently, since OBTC consolidates directly from sales order schedule lines rather than deliveries and is sensitive to profile setup. Compare pre- and post-cutover freight unit building rule assignments, verify that order integration settings in TM were not reset to delivery-based defaults during migration, and review a sample of orders to confirm consolidation group fields carried over correctly from source data.
hardFreight Units

11. In a capacity optimization scenario integrated with SD, how does SAP TM determine resource availability during freight unit building, and what happens when no compatible resource is available?

During freight unit building, TM checks resource master data including vehicle resources, equipment groups, and their availability calendars/capacity profiles against the freight unit's requirements such as weight, volume, and equipment type. If SD delivery data triggers freight unit creation but no compatible resource exists within the planning horizon, the freight unit remains unplanned or is flagged with an exception, requiring manual resource assignment, capacity extension, or subcontracting via a freight order to an external carrier.
hardFreight Units

12. During freight unit building from high-volume SD orders, carrier selection consistently assigns a single preferred carrier regardless of lane-specific rate advantages from alternate carriers, causing cost overruns. As solution architect, how would you diagnose and resolve this?

Investigate the carrier selection settings in the freight unit building rule and transportation charge management to confirm whether carrier ranking is based on stale or overly weighted preference profiles rather than dynamic rate comparison. Check business share/quota arrangements, carrier profile priorities, and whether rate determination is actually being evaluated per lane at optimization time rather than defaulted from a static carrier assignment on the FU building rule itself.
hardFreight Units

13. Describe the end-to-end process of designing selection profiles for freight units in a landscape where EWM controls warehouse execution timing, ensuring only warehouse-ready freight units are pulled into a planning run.

Design selection profiles filtering freight units by status fields tied to EWM readiness signals, such as warehouse request confirmation or wave assignment completion, alongside standard criteria like transportation group, dates, and locations. Coordinate with EWM to ensure status updates flow back to TM freight unit statuses in near real time so selection profiles don't pull unready units into planning. Test selection logic against edge cases like partial wave completion or delayed goods issue confirmation to avoid premature planning.
hardFreight Units

14. How does SAP TM handle unit of measure conversion when building freight units from sales orders replicated through SD integration, particularly when weight or volume UoMs differ between the source document and TM master data?

TM uses the material master and global UoM conversion tables replicated from ERP/S4 to convert source quantities into the base UoM required for freight unit building, typically weight and volume. If conversion factors are missing or inconsistent between SD and TM, freight unit creation can fail or produce incorrect capacity utilization, so alternative UoMs must be maintained consistently across material master, transportation group, and package specifications. In complex rollouts, custom BAdI logic may be needed to handle non-standard conversions such as density-based volume calculation.
hardFreight Units

15. Freight units generated from SD deliveries are showing incorrect transit times and route distances after go-live. As the solution architect, how would you troubleshoot the route and distance determination issue in freight unit building?

First check whether the freight unit building rule is correctly deriving locations from the delivery (ship-from/ship-to) and whether master data for those locations has valid geocoding. Verify the transportation lane and route configuration in TM, since distance/duration typically come from lane-based determination or an integrated GIS/map service rather than SD. Check if a default route or transportation zone is being used incorrectly when specific lane data is missing. Review whether SD delivery changes (partial deliveries, address overrides) are being properly propagated to freight unit re-determination.
hardFreight Units

16. The TM optimizer intermittently fails to build freight units for SD orders, leaving requirements unplanned after nightly batch runs even though FU building rules appear correctly configured. As solution architect, how would you diagnose the root cause across FU building rule scope, background job scheduling, and optimizer settings?

I would first check the application log for the FU building run to see whether affected orders are being excluded due to rule scope (item category, route, or document type filters) or failing validation. Next, I'd verify the background job sequencing—confirming FU building completes before the optimizer run starts and that no locking conflicts occur during high-volume nightly batches. Finally, I'd review optimizer strategy profile scope settings to ensure the newly built FUs fall within the selection criteria used by that specific run.
hardFreight Units

17. Freight units built from SD sales orders are intermittently missing transportation requirement dates, causing planning runs to skip them entirely, and this only occurs for orders with certain delivery types. As solution architect, how would you troubleshoot this freight unit building issue?

Start by comparing FU building rule configuration across delivery types to identify which rule variant lacks proper date determination settings, then check the scheduling condition and route determination linked to the affected delivery type. Review the underlying sales order/delivery date fields feeding the FU building process and confirm copy control or item category settings aren't suppressing date propagation. Trace a failing FU in the Transportation Cockpit's freight unit monitor to see which date field is null and cross-check against FU building rule date source configuration.
hardFreight Units

18. Design a freight unit selection profile architecture for a global network where EWM-managed distribution centers have differing outbound readiness lead times, ensuring the optimizer only evaluates freight units that are truly execution-ready across all sites.

Architect site-specific selection profile variants keyed on plant/warehouse, each parameterized with a lead-time buffer reflecting that DC's typical EWM outbound processing time, rather than a single global selection profile. FU status should be enriched with a warehouse-readiness attribute updated via EWM integration events, and the optimizer run should be scheduled per site-cluster to align with each DC's readiness window, avoiding a one-size-fits-all selection criterion that either delays fast DCs or prematurely selects FUs from slower ones.
hardFreight Units

19. Freight units from SD sales orders are not consolidating into a single planned shipment despite matching destination and delivery date, even though load consolidation is enabled. As the architect, what are the likely root causes and how would you diagnose them?

Likely causes include mismatched freight unit building rule parameters (e.g., different transportation groups, incoterms, or means of transport derived from SD data), incompatible or conflicting split/merge settings in the FU building rule, differing planning stages or transportation zones due to address discrepancies, or scheduling windows that don't overlap once transit/loading times are calculated. I would compare the FU attributes on both units side by side, check the FU building rule's grouping criteria, and verify the SD delivery/order data feeding those attributes is consistent.
hardFreight Units

20. During Delivery-to-Transportation freight unit building, the TM optimizer is producing excessive fragmentation of freight units instead of consolidating deliveries as expected, despite consolidation being configured. What architectural and configuration areas would you investigate?

I would first check freight unit building rule settings for split criteria (e.g., incompatibilities, transportation zone mismatches, or overly restrictive time windows) that could be forcing fragmentation. Next, review optimizer profile parameters such as consolidation weight/volume thresholds and planning horizon settings. I would also verify that master data like transportation zones and calendars are correctly maintained, since mismatched zones prevent grouping. Finally, I'd check GTS-relevant compliance blocks that might be splitting shipments for export control reasons.
hardFreight Units

21. For a high-volume SD-integrated implementation, you need to architect automatic freight unit building rules so that load consolidation happens efficiently across thousands of sales orders daily without creating bottlenecks in the FU building process. What architectural decisions would you make regarding FU building rule design, consolidation grouping, and performance?

Design FU building rules to group by consolidation-relevant attributes (destination zone, delivery date window, incompatibility group) at the earliest possible stage rather than building one FU per order line, reducing volume entering the optimizer. Use background job scheduling with parallelization for FU creation from SD documents, and separate FU building profile settings from planning profile to decouple document creation performance from optimizer runtime. Monitor FU building via application log and periodically review consolidation group sizes to avoid oversized FUs that slow optimizer processing.
hardFreight Units

22. Design an exception handling architecture for delivery-to-transportation processing where optimizer settings include multiple incompatibility rules and GTS compliance checks must occur before freight unit release, ensuring no non-compliant shipment is planned.

I would design a staged exception framework where freight units are first held in a compliance-pending status until GTS screening (embargo, sanctioned party, license checks) completes successfully, feeding results back into TM via integration. Optimizer incompatibility rules would run only against GTS-cleared freight units, with exception codes distinguishing compliance holds from consolidation/incompatibility conflicts. A monitoring cockpit or exception workflow would route compliance failures to trade compliance teams and incompatibility conflicts to transportation planners, preventing either issue from silently blocking planning without visibility.
hardFreight Units

23. Post-go-live, a high-volume SD-integrated implementation shows Planning Profiles intermittently creating duplicate freight units for the same sales order line, causing double-booked capacity. As the architect, how would you diagnose and resolve this?

Review the freight unit building rule and planning profile trigger conditions for overlapping or redundant execution paths, such as both a background job and a manual re-trigger processing the same order. Check for re-determination logic firing on order changes that regenerates freight units without properly canceling prior ones. Examine change pointer/BAdI logic controlling freight unit creation, and verify idempotency safeguards exist so repeated triggers don't create duplicates. Correct the rule logic or add existence checks before freight unit creation.
hardFreight Units

24. How do carrier calendars influence freight unit building and delivery-to-transportation date determination in SAP TM?

Carrier calendars define the working days, cutoff times, and blackout periods a carrier can operate, and they are referenced during freight unit building to adjust requested pickup and delivery dates against actual carrier availability. When an SD delivery's requested dates fall outside carrier working times, the FU building rule shifts dates to the next valid carrier working day, affecting scheduling, lead times, and consolidation windows. In complex multi-carrier scenarios, calendar conflicts can cause FU dates to diverge from delivery dates, requiring exception monitoring.
hardFreight Units

25. Walk through how selection profiles determine which freight units are eligible for an optimizer run in a scenario where EWM-managed warehouse outbound processing constrains transportation scheduling.

The selection profile filters freight units based on criteria like planning stage, status, and date range, but in EWM-integrated scenarios it must also account for warehouse readiness indicators (e.g., delivery not yet released for picking) so FUs aren't selected for optimization before the warehouse confirms feasible pick/pack timing. This typically requires aligning FU status transitions with EWM outbound delivery order status so the selection profile only pulls FUs once warehouse constraints are satisfied.

Related topics

Integration with EWMFreight SettlementTransportation PlanningCharge CalculationTenderingTransportation Master DataIntegration with SDEmbedded TM, EWM Integration, Migration and SupportCarrier CollaborationExecutionEmbedded/Decentralized TM, EWM Integration, Migration and ArchitectureFreight Orders

Next practice step

Practice with Interview AITake a mock test