SAP TM Interview Questions

Freight unit building rules group delivery items into FUs based on grouping criteria such as ship-to, route, and departure date. When EWM manages the warehouse, scheduling in TM must factor in warehouse processing time (picking, packing) before goods issue readiness, typically reflected through duration profiles or lead time buffers tied to the shipping point. TM's scheduling then back-calculates pickup/loading windows so that EWM wave planning and TM transportation dates align, avoiding freight units scheduled earlier than the warehouse can physically release goods.

Start by checking whether the relevant delivery change is configured to trigger TM relevance (transportation-relevant delivery type/item category settings), then review integration monitoring for failed or delayed messages between the delivery and freight order objects. Check for custom logic or enhancement spots that may be filtering certain delivery changes, and verify that the freight order update rules cover the specific change scenario (e.g., quantity change vs status change) causing the gap.

Configure handling unit stacking factors and loading sequence attributes in the FU building rules derived from material master MM data, ensuring the load plan reflects correct pallet order within the vehicle resource. During tendering, include equipment requirement details (e.g., liftgate, specific trailer type) in the tender document via carrier communication settings so the assigned carrier receives loading instructions. Validate that load plan sequencing outputs align with EDI or print output sent to the carrier for execution.

Design three org units in TM representing the regional planning teams, each with planner/dispatcher functions assigned, mapped under a single top-level org unit tied to the company code. Carrier pools are segmented via transportation zones or carrier profile assignment per region rather than separate company codes. Cost allocation to FI/CO happens through freight settlement documents that reference cost centers or WBS elements tied to the originating org unit or shipment, ensuring granular reporting without needing multiple company codes.

I would check whether the charge calculation profile's calculation sheet is configured to reference actual execution fields (actual dates, actual distance/weight) versus planned fields, since BN4L updates only help if the charge determination logic is designed to consume them. I'd also verify the sequence of processing: charge calculation may be running before the BN4L status update is applied to the freight order, requiring a re-trigger step after execution data confirmation. Correcting this typically involves adjusting the calculation sheet's field references and adding an explicit recalculation trigger tied to the relevant execution status change.

Design starts by identifying which freight unit statuses reflect true EWM readiness—such as delivery release, wave assignment, or pick confirmation—and building selection profile filters on those status and date fields rather than raw sales order data. Iteratively test with representative volumes to confirm the profile excludes FUs still pending EWM staging or resource allocation, then align refresh timing with EWM status updates so planners never see freight units that the warehouse cannot yet fulfill.