ERPClimb logoERPClimb

SAP TM Tendering Interview Questions

Tendering is a standard block in SAP TM interviews. It is rarely asked as a definition; it is asked as a situation you have to talk your way through.

Tendering in SAP Transportation Management covers the process of offering freight orders/freight bookings to carriers, capturing their responses, and confirming shipment assignment. This topic explains the business purpose of tendering, the underlying master data and configuration (tendering profiles, rules, carrier selection sets), the runtime document flow between freight order, tendering, and carrier confirmation, integration with carrier collaboration channels, and troubleshooting/production support considerations across Embedded TM, Decentralized TM, and S/4HANA deployments.

This page carries 42 reviewed SAP TM tendering interview questions, each with a complete written answer and no sign-in required. The set breaks down into 2 foundational, 28 mid-level and 12 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.

Treat the answers as a starting structure, not a script. Interviewers in SAP TM rounds follow up on whatever you sound least certain about, so the value is in being able to keep going after the first answer.

42 Tendering questions with answers

easyTendering

1. What is transportation tendering in SAP TM, and how does the system determine which carriers receive a freight order tender based on rate agreements and carrier profiles?

Tendering is the process of offering a freight order to one or more carriers for acceptance, driven by the tendering profile assigned to the freight order type. The system evaluates carrier selection settings, freight agreements, and carrier profile suitability (mode, region, service level) to build a tendering plan—either broadcast or sequential—and sends the offer via carrier collaboration channels until a carrier accepts or the tender expires.
easyTendering

2. What is Carrier Selection in SAP TM, and how does it fit into the sequence of freight unit building, planning, and tendering for an SD-integrated order-to-freight process?

Carrier Selection is a rule-based (or manual) step in TM that determines which carrier should execute a freight order or freight booking, typically run after freight units are built from SD orders/deliveries and planned into freight orders. It uses carrier profiles, rate/rank criteria, and business shares to propose a carrier before tendering. It occurs after freight unit building and planning but before or during the tendering process to the selected carrier.
mediumTendering

3. An MM-driven inbound scenario requires load planning to account for pallet stacking sequence tendered to a third-party carrier that has specific loading equipment constraints. How would you configure load planning and tendering to communicate these constraints to the carrier?

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.
mediumTendering

4. After tendering freight orders through the optimizer, a client wants tender acceptance data to feed back into IBP so future capacity forecasts reflect actual carrier commitments. How would you architect this feedback integration?

Accepted tender outcomes (carrier, volume, lane, date) would need to be extracted from TM freight order data and mapped to a format IBP can consume, typically through a periodic integration job or API rather than real-time embedded coupling, since IBP forecasting cycles operate on aggregated planning horizons rather than transactional freight order events. Design should aggregate tender acceptance data by lane/period before pushing to IBP to avoid overwhelming forecast models with transactional noise.
mediumTendering

5. A shipper's carrier selection process must consider export compliance screening before tendering a freight order to a carrier operating cross-border routes involving denied-party checks. How would you design the integration between TM carrier selection and GTS in this scenario?

Carrier selection would run first based on rate/capacity rules, then before final tender release, the freight order or party data triggers a compliance check call to GTS for sanctioned party list screening on the selected carrier, consignee, and route. If GTS flags a hold, the freight order is blocked from tendering until compliance clears it. This requires configuring an integration touchpoint at the tendering step, often via BAdI or workflow, ensuring compliance results are visible to planners before carrier confirmation.
mediumTendering

6. A forwarding order created for an ocean shipment is tendered to carriers through SAP Business Network for Logistics, but the execution status on the freight order remains stuck at 'Tendering in Process' even though the carrier accepted the load in the network portal. How would you investigate and resolve this?

I would first check the integration monitor for the Business Network for Logistics connection to confirm the acceptance message was received and processed without error. Next, verify the tendering status mapping configuration so the external acceptance event correctly triggers the internal freight order status update. If the message queue shows a stuck IDoc or API call, reprocess it; if the mapping is missing an entry for the specific carrier response code, correct the customizing and manually update the freight order status if needed.
mediumTendering

7. A distribution company receives inbound MM purchase order deliveries where certain freight units must be tendered only to carriers pre-approved for handling temperature-sensitive materials. How would you configure freight units and tendering to enforce this carrier eligibility restriction?

Tag the relevant materials or freight units with a handling requirement attribute (e.g., temperature-controlled) derived from MM material master data, then use this attribute in the carrier selection settings to filter eligible carriers via carrier profile qualifications or means of transport restrictions. Configure the tendering process to only include pre-approved carriers in the tender sequence for these FUs, and set the selection profile to exclude non-qualified carriers automatically, preventing manual override errors during exception handling.
mediumTendering

8. When configuring Tendering settings that feed from IBP-driven demand signals, what optimizer settings and tendering profile parameters must be aligned to ensure planned freight orders are tendered within carrier response-time windows?

Align the optimizer's planning horizon and freight order creation timing with IBP's demand forecast update cycle so freight orders are generated early enough for tendering lead time. Configure tendering profiles with realistic response deadlines, escalation rules, and carrier ranking that reflect contracted SLAs. Ensure optimizer cost/time parameters don't create last-minute freight orders that leave insufficient tendering windows, and synchronize batch job scheduling between IBP data refresh and TM optimizer runs.
mediumTendering

9. During hypercare, a carrier onboarded to SAP Business Network for Logistics is not receiving tendering notifications from embedded TM freight orders. What integration settings would you check first?

First verify the business partner's communication setup and role assignment (carrier flagged for network exchange), then check the output determination/condition records for the freight order tendering process pointing to the network-relevant output type. Confirm the BTP integration/cloud connector settings and communication arrangement are active and not blocked by a certificate or authorization issue, and check the integration monitoring (message/queue monitor) for failed outbound calls before assuming a network-side onboarding problem.
mediumTendering

10. A shipper wants Carrier Selection and Tendering to factor in MM-driven vendor performance ratings so that inbound freight from underperforming vendors' shipments is more strictly monitored, without changing the actual carrier tendering logic. How would you approach this design?

Keep Carrier Selection and Tendering logic focused on carrier attributes, but enrich freight unit or transportation requirement data with a vendor performance indicator sourced from MM vendor evaluation data. Use this indicator in selection profiles or exception monitoring rules to flag shipments from underperforming vendors for closer tracking or expedited escalation, without altering carrier ranking criteria itself. Ensure the MM vendor rating data is refreshed on a schedule that keeps the indicator current for planning decisions.
mediumTendering

11. A freight order's carrier selection process repeatedly assigns a carrier that later fails a GTS denied-party screening milestone, causing the shipment to be pulled back from tendering after the carrier was already notified. How would you redesign the event-to-resolution flow to prevent this from recurring?

I would move the GTS compliance check earlier, before carrier assignment finalizes in carrier selection, rather than as a post-assignment milestone. This requires integrating GTS screening as a synchronous check within the carrier selection strategy or as a hard gate before the tender is released. Additionally, configure an Event Management milestone that monitors screening completion status and blocks tender release until a 'cleared' event is received, with automatic exception handling and carrier re-selection if screening fails.
mediumTendering

12. During hypercare for an Advanced Shipping and Receiving (ASR) rollout integrated with SAP Business Network for Logistics, what configuration checks are critical when carriers report missed tender notifications?

Verify the Business Network integration add-on and communication arrangement (SOAP/REST endpoints) are active, check tendering profile assignment on the freight order/forwarding order, confirm carrier business partner has a valid Business Network ID mapped, and review the tendering strategy sequence and timeout settings. Also check queue monitoring (SMQ1/SMQ2 equivalents in S/4HANA) for stuck IDocs or failed outbound calls, and confirm the carrier's network subscription and connectivity status on the Business Network side.
mediumTendering

13. What configuration is required to ensure a GTS compliance/embargo check is triggered before a carrier is confirmed during tendering in SAP TM?

You configure the compliance integration scenario (sanctioned party list and embargo checks) between TM and GTS, typically triggered at freight order save or carrier confirmation via the compliance check BAdI/enhancement spot. The carrier business partner and tendering process must be flagged as relevant for compliance checks, and a block status is set on the freight order if GTS returns a hold, preventing tender confirmation until the block is cleared in GTS.
mediumTendering

14. A manufacturing client receives inbound deliveries from MM purchase orders and wants to tender consolidated inbound freight units to a shared carrier pool, but planners find that tender responses arrive after the planned pickup window has passed. How would you redesign the tendering timeline in this Delivery-to-Transportation process?

Shift the tendering trigger earlier in the process by shortening the freight unit building lead time relative to the planned pickup date, or introduce a tender response deadline shorter than the buffer between planning completion and pickup, so carriers must respond within a window that still allows execution. Review carrier tendering profile settings for response time limits and consider parallel tendering to multiple carriers in the pool to reduce single-carrier response latency risk.
mediumTendering

15. Inbound freight units generated from MM purchase orders are not appearing in the tendering selection profile even though similar deliveries are included, and the team suspects an Incoterms-driven responsibility mismatch. How would you diagnose this?

I would check the FU's transportation planning point and responsibility attributes derived from the purchase order Incoterms, since freight units where the vendor holds carrier responsibility (e.g., Incoterms placing transport under vendor arrangement) may be flagged as not TM-managed and excluded from selection by design. I'd verify the Incoterm-to-shipment-responsibility mapping in configuration and confirm whether the selection profile's inclusion criteria properly account for buyer-managed versus vendor-managed inbound freight.
mediumTendering

16. A distribution company wants to tender freight orders automatically to preferred carriers using MM-driven purchase order lead times, but planners are seeing tenders sent before goods receipt confirmation windows are met. How would you configure planning profiles and tendering to address this timing gap?

I would review the freight unit building rule scheduling that derives pickup dates from the purchase order, ensuring it factors in vendor confirmation and goods receipt processing time rather than the raw PO date. The tendering profile's start condition should be tied to a planning stage that only triggers after the FU's scheduled pickup window reflects confirmed availability, with an added buffer in the planning profile to prevent premature tender release.
mediumTendering

17. During carrier tendering, output documents (tender confirmations) fail to generate for freight orders created from SD sales orders with a specific shipping condition. How would you troubleshoot this output management exception?

I would check the output determination configuration for the freight order type, confirming the condition records include the shipping condition value inherited from the SD sales order. Then verify the output channel (email, IDoc, print) is correctly configured and that the partner determination procedure resolves a valid carrier partner with communication data. I'd also check whether the SD-to-TM integration correctly transferred the shipping condition attribute, since a missing or mismatched field value in the freight order would prevent the output condition record from finding a match.
mediumTendering

18. When configuring freight agreements in SAP TM for carriers subject to GTS export control screening, what master data and configuration steps ensure that agreement-based tendering does not bypass compliance checks?

Freight agreement master data (validity, rate scales, carrier assignment) must be linked to a carrier business partner whose GTS-relevant classification (denied party list status, license data) is current. Configuration should ensure that tendering profiles trigger GTS screening before agreement-based carrier selection is finalized, typically via integration checkpoints in the freight order or booking process. Agreement validity periods should be synchronized with GTS block/unblock status changes, and screening must not be skipped simply because a valid rate agreement exists for that lane and carrier.
mediumTendering

19. A global shipper needs to ensure that no freight order is tendered to a carrier before a denied-party and embargo screening is completed via SAP GTS. How would you design the integration between TM tendering and GTS compliance checks?

I would design a compliance check step in the tendering workflow that calls GTS before the tender request is released to the carrier, blocking or holding the freight order status until GTS returns a clear result. This typically means adding a status or condition on the freight order/forwarding order that GTS screening must complete successfully, using the standard SPL (sanctioned party list) screening integration, and configuring the tendering process so blocked orders cannot progress to carrier selection or tender release.
mediumTendering

20. You are cutting over an embedded TM implementation where outbound shipments require GTS export compliance checks before tendering. What steps ensure compliance checks are correctly integrated at cutover?

Confirm the GTS plug-in configuration and legal control settings are active for the relevant sales organizations/plants, validate that freight order creation triggers the compliance check via the standard integration before tendering is allowed, and run parallel test scenarios in cutover mimicking blocked and cleared shipments. Ensure master data (business partners, denied party lists) is synchronized to GTS ahead of go-live, and define a fallback manual process if GTS is unavailable during initial days.
mediumTendering

21. A carrier's master data record was flagged and blocked in MDG for compliance review, but planners in TM continue selecting that carrier for tendering. What is the likely governance gap and how would you fix it?

The likely gap is that the MDG block status was not synchronized to the corresponding business partner or carrier profile status in TM, or the TM carrier selection logic does not check the relevant status field before tendering. The fix involves ensuring the MDG-to-TM replication updates the block/status indicator on the business partner role for carrier, and configuring carrier determination and tendering profiles to respect status checks so blocked carriers are automatically excluded from freight assignment and rate determination.
mediumTendering

22. A procurement team notices that inbound Transportation Requirements from MM purchase orders are not being tendered to preferred carriers on time, delaying vendor pickups. As the consultant, how would you investigate and resolve the tendering timing issue?

Check the timing between purchase order/inbound delivery creation and freight unit/transportation requirement generation, since delays upstream in MM push back the entire tendering timeline. Review the tendering profile's lead time settings and carrier response deadlines against actual vendor pickup windows. Verify batch job scheduling for freight unit building and tendering runs is frequent enough, and confirm carrier master data (calendars, response times) is current. Adjust tendering profile deadlines or trigger frequency to close the gap.
mediumTendering

23. A dangerous goods shipment fails carrier selection because the assigned carrier is blocked during a GTS compliance check. What steps would you take to resolve the tendering issue while maintaining compliance controls?

I would first confirm the GTS block reason, such as a denied-party list hit or missing DG certification, rather than overriding it. If the block is a false positive, I'd work with the compliance team to release it through the proper GTS workflow. If the carrier genuinely lacks required DG handling qualifications, I'd exclude them from the carrier selection set for that freight order and let the system re-run selection against qualified DG-certified carriers, then re-tender accordingly.
mediumTendering

24. A carrier business partner is used both for freight execution in TM and for customs screening in GTS, but recent updates to the carrier's export license data in GTS are not reflected when planners attempt to tender shipments in TM. How would you investigate this integration gap?

Confirm whether the carrier business partner's compliance-relevant attributes (license, denied-party status) are maintained in GTS and whether the integration between GTS and the business partner replication to TM is configured to trigger real-time or scheduled synchronization. Check if TM tendering logic actually calls GTS screening at execution time versus relying on a cached compliance flag on the business partner. If screening is only triggered on business partner replication and not re-evaluated at tender time, license updates in GTS won't be reflected until the next sync cycle, requiring either more frequent replication or moving the check point closer to tender execution.
mediumTendering

25. A procurement team wants inbound freight orders from MM purchase orders tendered automatically to a pool of approved carriers, but tenders are going out before the freight unit's actual pickup date is confirmed by the vendor. How would you adjust planning profile and tendering settings to fix this?

I would adjust the freight unit building rule's scheduling logic so the pickup date reflects vendor confirmation rather than the initial PO delivery date, then set the tendering profile's start condition to trigger only once the freight unit reaches a planning stage indicating confirmed scheduling. Adding a configurable buffer in the planning profile provides a safety margin so premature offers aren't sent to the approved carrier pool while a legitimate confirmation is still pending.
mediumTendering

26. During hypercare, how would you configure the integration between embedded TM and SAP Business Network for Logistics to ensure carrier tendering status updates flow back correctly?

Configure the Business Network integration via the cloud integration gateway/SAP Integration Suite scenario for TM freight order tendering, mapping carrier response statuses (accept/reject/counter) to TM tendering status codes. Ensure communication arrangements and business system definitions are active, monitor via the integration monitoring cockpit, and validate that status change events trigger correct freight order updates without duplicate tender cycles during hypercare volume spikes.
mediumTendering

27. A distribution client needs load plans for MM inbound purchase order deliveries to be tendered to a pool of approved carriers before execution begins, but planners report tendering is being triggered before load consolidation is finalized. How would you address the sequencing issue?

The tendering process step should be positioned after freight order/load consolidation completion in the transportation process controller settings, not immediately after freight unit creation. Review the freight order status transitions and process control profile to ensure tendering only fires once the load is finalized (e.g., status 'planned/confirmed'), and check whether automatic tendering rules were inadvertently triggered on FU-level rather than at consolidated freight order level.
mediumTendering

28. A shipment requires carrier selection to also account for SAP GTS compliance screening before a carrier can be confirmed, particularly for restricted-party or embargo checks. How would you approach integrating carrier selection with GTS compliance in this scenario?

Carrier selection should run first to identify the best-ranked carrier based on cost, service level, and capacity, but final confirmation must be gated by a GTS compliance check on the carrier, consignee, and route combination. This typically means the freight order or forwarding order triggers a compliance check (sanctioned party list screening, embargo check) via the GTS integration before the tender is released to the carrier. If GTS blocks the transaction, the process should fall back to re-run carrier selection excluding the blocked carrier/route rather than allowing tendering to proceed.
mediumTendering

29. A distribution center uses carrier selection rules that don't account for dock scheduling constraints, and trucks from selected carriers repeatedly arrive without an available dock slot, causing yard congestion. As solution architect, how would you redesign carrier selection to incorporate execution status awareness synchronized with Business Network for Logistics tracking?

I would extend carrier selection profiles to factor in carrier reliability metrics and appointment-slot compatibility, and integrate real-time execution status feeds from Business Network for Logistics into the carrier scoring so that carriers with poor on-time pickup/delivery history or frequent appointment mismatches are deprioritized. Additionally, I'd sequence tender confirmation to require carrier commitment to a specific appointment window before finalizing, and use Event Management alerts to flag carriers whose network-reported ETA conflicts with the booked dock slot for dispatcher intervention.
mediumTendering

30. Your inbound logistics team wants freight units created from MM purchase orders to be tendered automatically to preferred carriers, but the tendering process keeps proposing carriers outside the MM source-list preference. How would you investigate and correct this?

I would first check whether the tendering strategy in the planning profile ranks carriers by freight agreement cost/priority rather than by MM source list or quota arrangement preference, since these are separate master data objects not automatically synchronized. Verify that preferred carriers have valid, active freight agreements with matching validity and lane coverage, and if needed, adjust carrier selection settings or build a custom BAdI to weight MM vendor preference into the tendering carrier ranking logic.
hardTendering

31. During carrier tendering for a forwarding order, the tendering process appears stuck: the assigned carrier hasn't accepted or rejected within the expected timeframe, and no Event Management alerts have fired to notify the planner. As solution architect, how would you diagnose and structure a fix?

I would first verify the tendering plan's response deadline and escalation configuration to confirm an alert should have fired, then check whether the Event Management (or embedded alerting) rule set is correctly linked to the tendering status and deadline field. Next, I'd review whether the carrier's response channel (portal, EDI, or manual) is functioning, since a broken inbound channel can leave tenders indefinitely open without triggering a rejection or timeout event. Architecturally, I'd recommend adding a monitoring job or workflow-based fallback escalation so tenders don't silently stall when the primary notification path fails.
hardTendering

32. A rail freight tender is repeatedly rejected by the assigned carrier, and the resulting delay is not automatically raising an exception in Event Management. How would you resolve this in a way that supports faster event-to-resolution cycles?

I would first check whether the tendering process for rail is configured to escalate after a defined number of rejections, since repeated rejection without an automatic re-tender or exception trigger indicates a gap in the tendering rule or event profile setup. I'd then verify the event profile includes a rejection-count or time-based deviation trigger to raise an exception, and ensure the exception is routed to the correct planner or resolution workflow rather than remaining a silent status change.
hardTendering

33. A road freight order is tendered simultaneously to a ranked list of carriers with a sequential tendering strategy. When the top carrier rejects, the system should automatically re-tender to the next carrier and raise an Event Management alert if no acceptance occurs within a defined SLA window. In production, rejections are processed but the automatic re-tender to the next carrier silently fails, and no exception alert is raised. As solution architect, how would you diagnose and fix this?

Check the tendering strategy configuration (sequential vs. parallel, number of rounds, timeout settings) and confirm the tendering rule status is correctly re-evaluated on rejection via the tendering cockpit/BOL. Verify the event/condition-based exception rule for 'no carrier response' or 'tender rejected' is active and linked to the freight order's process controlling strategy. Check application log (SLG1) for tendering workflow errors, confirm the rejection status update triggers the next-carrier logic, and validate the alert profile in Event Management is subscribed to the correct event type.
hardTendering

34. Walk through how event integration during carrier tendering of a forwarding order can trigger downstream MM purchase order creation, and what design elements ensure the event-to-PO linkage is reliable.

When a carrier accepts a tender on the freight order, a status change event (e.g., tendering completed) can be configured to trigger creation of a subcontracting purchase order in MM via the TM-MM integration for freight settlement. Reliability depends on correct freight order status profile configuration, PO creation being tied to a specific status transition (not just any event), proper vendor/carrier master data mapping, and error handling for failed PO creation attempts surfaced through application logs or exception monitoring.
hardTendering

35. Design a carrier selection architecture for a distribution network where selection profiles must consider EWM warehouse readiness, such as pick and pack completion, before candidate carriers are proposed for tendering.

I would design a two-stage selection process: an initial candidate carrier pre-selection based on freight agreement and lane suitability that can run early for planning visibility, and a final tendering-eligible selection profile gated on EWM status fields confirming pick/pack completion or cargo-ready confirmation. An event-based trigger from EWM status changes would update freight unit readiness flags in TM, ensuring the final carrier tender only fires once cargo is genuinely ready for pickup.
hardTendering

36. Design an architecture for tendering selection profiles in a global network where EWM wave release timing must gate which freight units are eligible for carrier tendering, preventing tenders from going out before goods are pick-confirmed.

I would model the FU's logistics status to include an EWM-synchronized readiness flag (e.g., wave released/pick confirmed) propagated through integration middleware, then build the tendering selection profile to filter on this status alongside standard date and location criteria. Tendering execution would only trigger for FUs meeting both timing and readiness conditions, with an exception queue capturing FUs that reach their tender deadline without readiness confirmation for manual escalation, ensuring auditability and preventing premature carrier commitments across regions.
hardTendering

37. Walk through how Event Management integration influences the tendering process in a plan-to-execute transportation scenario, from initial carrier tender to acceptance and downstream execution triggering.

Event Management monitors expected milestones such as tender response deadlines, carrier acceptance, and pickup confirmation. When a tender is sent, an expected event (carrier response) is registered; if the carrier doesn't respond within the threshold, an exception is raised, prompting escalation or re-tendering to the next carrier per the carrier selection sequence. Once accepted, the acceptance event transitions the freight order into execution readiness, feeding subsequent milestone tracking through dispatch, loading, and departure, tying tendering outcomes directly to execution monitoring.
hardTendering

38. A shipper's yard has multiple dock doors, and a carrier truck arrives for loading before the freight order tender has been formally confirmed by the carrier. Dispatchers report conflicting loading sequences and delayed departures. How would you design the tendering and dock coordination process in TM to prevent this?

I would enforce a tendering status gate so freight orders cannot be released to dock scheduling until tender acceptance status is confirmed, using the tendering status profile to block premature dock slot assignment. Dock/yard scheduling integration (via Event Management or a yard management extension) should only trigger slot booking after acceptance, with exception handling for early arrivals routed through a manual override workflow visible to dispatchers on the cockpit, avoiding silent sequence conflicts.
hardTendering

39. At a distribution center, carrier selection is repeatedly assigning carriers whose trucks cannot get a dock slot in the yard management system in time, causing recurring dock congestion and detention costs. As the solution architect, how would you redesign the carrier selection and tendering process to account for dock/yard constraints?

I would extend carrier selection logic to consider yard/dock availability by integrating relevant time-window or capacity data from Event Management or a yard scheduling system before finalizing the carrier ranking, rather than treating rate and service level as the only criteria. This could involve introducing a pre-check step that filters or deprioritizes carriers whose planned arrival windows conflict with available slots, and building an event-driven feedback loop so yard congestion signals adjust tendering sequence dynamically for future orders.
hardTendering

40. During tendering of a dangerous goods road shipment, the carrier accepted the tender but the freight order later fails a route restriction check tied to DG classification. How should the tendering and monitoring process be designed to prevent this reaching execution?

I would design the tendering process so DG classification and route restriction validation occur before or at tender offer creation, not after acceptance, using DG master data checks integrated into carrier selection so only carriers and routes approved for the specific DG class are eligible. Event Management should monitor for any late-arriving DG attribute changes on the freight order and automatically re-trigger validation, cancelling or re-tendering if the accepted carrier or route becomes non-compliant, rather than allowing execution to proceed silently.
hardTendering

41. Describe the end-to-end tendering process in SAP TM when freight units originate from EWM-managed deliveries, including how selection profiles determine which shipments are eligible for tendering.

After freight units are consolidated into a shipment, the tendering process selects eligible carriers based on carrier profiles, rate agreements, and business share rules, sending tender requests sequentially or in parallel. Selection profiles filter shipments ready for tendering based on status, planning stage, and EWM confirmation of pick/pack completion so tenders aren't issued prematurely. Once a carrier accepts, the shipment is confirmed and released to EWM for loading, with rejections triggering re-tendering to the next carrier in sequence.
hardTendering

42. A carrier master record was recently updated with a new default resource (truck/trailer) assignment, but planners report that tendering still offers the old resource capacity for certain lanes. GTS screening also seems to be bypassed for this carrier on international lanes. How would you investigate and resolve both issues?

First check whether the resource change was made at the correct level (carrier BP resource assignment vs. transportation unit master) and confirm change was saved and released, since caching or unreleased changes can cause stale data in tendering. Check if freight unit building rules or transportation lane assignments still reference old resource IDs. For GTS bypass, verify the business partner's compliance/GTS integration flag and check whether the lane or carrier profile is configured to trigger sanctioned party or embargo screening; missing BP classification or incomplete country/region master data on the location can cause screening to be skipped.

Related lesson

Architecting Enterprise Tendering Strategy: Governance, Scale, and Deployment Trade-offs

Related topics

Integration with EWMFreight SettlementTransportation PlanningCharge CalculationTransportation Master DataFreight UnitsIntegration 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