Configuring Tendering Strategies, Profiles, and Carrier Selection Sets (Part 3)

Tendering in SAP TM is driven by a tendering strategy that is attached to a tendering profile, which in turn is linked to freight order types or determined via condition technique (transportation charge management determination or freight agreement determination logic reused for carrier selection). Understanding how these pieces fit together is essential because a misconfigured strategy either sends tenders to the wrong carrier pool or creates operational delays.

There are two core strategy types. Broadcast tendering sends the tender simultaneously to all carriers in a selection set and awards the freight order to the first carrier who accepts (or based on best offer if rate negotiation is enabled). Sequential tendering sends the tender to carriers one at a time in a defined ranking order, waiting for a response (accept, reject, or timeout) before moving to the next carrier. Sequential tendering is typically used when there is a preferred carrier hierarchy driven by contract commitments or historical performance, while broadcast tendering is used to maximize speed of coverage, often for spot freight or urgent shipments.

A tendering profile bundles the strategy with time-based parameters: response deadline per carrier (or per round in broadcast mode), overall tendering horizon, and what happens on timeout (auto-reject, escalate, or fallback to a default carrier). These parameters must be tuned realistically — too short a deadline causes carriers to reject due to insufficient decision time, too long delays shipment execution and risks missed customer commitments.

Carrier selection sets are built from business partners flagged as carriers, and can be static (a fixed list of carrier IDs) or dynamic, using conditions based on transportation zone, mode of transport, equipment type, or existing freight agreements. In many implementations, the selection set is derived from active freight agreements so that only carriers who have a valid, non-expired rate agreement covering the relevant lane are considered.

During configuration, you also decide whether tendering is manual (planner explicitly triggers tendering from the freight order) or automatic (triggered by a background job or event, such as freight order creation or a planning stage completion). Automatic tendering is common in high-volume distribution scenarios, while manual tendering is retained for exception lanes, new carriers, or high-value shipments requiring human judgment.

A critical design decision is how carrier acceptance updates the freight order. Once a carrier accepts, the system should automatically set the freight order to an appropriate status (e.g., carrier assigned) and stop further tendering rounds. If your configuration does not correctly terminate parallel rounds, you risk double-booking freight with two carriers, which is a serious operational and financial issue.

Testing this configuration requires end-to-end scenarios: create a freight order, trigger tendering, simulate carrier responses (accept, reject, no response/timeout), and verify that status transitions, notifications, and any subsequent charge calculation trigger correctly. Because tendering strategy behavior varies with deployment (Embedded TM close integration with S/4HANA logistics execution versus Decentralized TM communicating over standard interfaces with an ERP system), always validate configuration against the actual landscape rather than assuming identical behavior across deployment types.

A retail distribution client used sequential tendering for contracted domestic lanes (to respect committed carrier hierarchy) and broadcast tendering for overflow/spot freight during peak season. During initial go-live, the sequential timeout was set to 30 minutes, which was too short for regional carriers who needed to check truck availability manually; this caused excessive escalation to the planner work list. The team extended the timeout to 3 hours for regional carriers while keeping 30 minutes for national carriers with EDI-integrated automated responses, resolving the escalation volume issue.

• Setting identical response deadlines for EDI-integrated carriers and manually-responding carriers, ignoring their different response capabilities
• Failing to define a fallback/escalation path when all tendering rounds are exhausted, leaving freight orders stuck with no carrier
• Using a static carrier selection set that does not reflect expired or newly onboarded freight agreements
• Not testing double-booking prevention logic when broadcast tendering receives near-simultaneous acceptances
• Assuming tendering profile assignment via freight order type covers all cases, without accounting for condition-based overrides needed for exception lanes

• Tie dynamic carrier selection sets to active freight agreements to avoid tendering to expired-contract carriers
• Differentiate response deadlines by carrier communication capability (EDI/API vs. manual/portal)
• Always define an escalation path for exhausted tendering rounds to avoid orphaned freight orders
• Validate double-booking prevention logic explicitly in broadcast scenarios before go-live
• Document strategy-to-freight-order-type mapping clearly for support teams to reduce production troubleshooting time

Interviewers often probe whether a candidate can explain the operational difference between sequential and broadcast tendering and justify when each is appropriate. Be ready to discuss how timeout and escalation design prevents freight orders from being stuck without carrier assignment, and how carrier selection sets should tie back to valid freight agreements rather than static lists.