SAP C_S4TM Value Pack (Frequently Bought Together)

A regional mobile medical cart distributor uses SAP S/4HANA Transportation Management to plan outbound shipments for hospital go-live carts and routine depot replenishment. Automatic planning reduces freight order count, and subcontracting to the contracted carrier works correctly. However, go-live carts are consolidated with replenishment freight that has more flexible timing, causing several carts to miss hospital receiving windows tied to implementation schedules.
The implementation coordinator wants hospital receiving windows protected, while logistics wants to retain consolidation savings for routine replenishment. The constraint is to keep automatic planning and carrier subcontracting active while ensuring go-live timing is respected before freight orders are released.
Which planning decision best supports the constraint?
Response:

• A. Exclude all hospital go-live carts from automatic planning so implementation coordinators can manage timing manually.
• B. Adjust planning criteria so hospital receiving windows restrict consolidation before freight orders are finalized.
• C. Increase consolidation weighting so the planning run continues reducing freight order count across go-live and replenishment freight.
• D. Keep the current planning setup and ask implementation coordinators to negotiate wider receiving windows after planning.

CHALLENGE 1 - Bonded Warehouse Deliveries Reaching Transport Planning
During first-close preparation, several bonded warehouse deliveries appear in warehouse release monitoring and can be picked. When they enter transportation planning, the freight units do not consistently carry the pickup-window data used by dispatchers.
What should be validated first?
Response:

• A. Whether finance can manually adjust carrier invoices after the first settlement run is completed.
• B. Whether bonded warehouse deliveries are transportation-relevant and create freight units carrying release timing and pickup-window attributes.
• C. Whether warehouse teams can confirm loading slots before the freight units carry pickup-window data.
• D. Whether bonded warehouse shipments should be excluded until all standard plant shipments are settled.

CHALLENGE 2 - Priority Windows Preserved During Freight Order Creation
A planner manually assigns a partner staging location for a priority replenishment shipment so confirmation can be sent quickly. The freight order is executable, but the execution timing no longer matches the laboratory commitment entered by customer service.
What is the best recommendation?
Response:

• A. Convert all priority partner-staged shipments into company-operated route movements for the onboarding wave.
• B. Validate that freight order creation preserves priority-window and staging-location requirements before partner assignment.
• C. Delay all freight order execution until finance manually approves every partner handling charge.
• D. Accept the freight order because execution capability is sufficient for the partner onboarding checkpoint.

A regional exhibition lighting supplier uses SAP S/4HANA Transportation Management to plan outbound shipments for venue lighting rigs and routine warehouse replenishment. Automatic planning reduces freight order count, and subcontracting to the contracted carrier works correctly. However, lighting rigs are consolidated with replenishment freight that has later delivery flexibility, causing several rigs to miss venue setup slots.
The project delivery team wants setup slots protected, while logistics wants to retain consolidation savings for routine replenishment. The constraint is to keep automatic planning and carrier subcontracting active while ensuring venue setup timing is respected before freight orders are released.
Which planning decision best supports the constraint?
Response:

• A. Adjust planning criteria so venue setup slots restrict consolidation before freight orders are finalized.
• B. Keep the current planning setup and ask the project delivery team to negotiate wider setup slots after planning.
• C. Increase consolidation weighting so the planning run continues reducing freight order count across setup and replenishment freight.
• D. Exclude all venue lighting rig shipments from automatic planning so project delivery users can manage timing manually.

A regional mobile kiosk distributor is defining SAP S/4HANA Transportation Management scope for planned hub replenishment and short-notice kiosk removal shipments. The first release must support freight order planning, execution visibility, and later settlement for planned replenishment. Kiosk removals still depend on customer-site authorization, unclear dismantling responsibility, and variable carrier confirmation that have not been validated in the target process.
The account operations lead wants removals included immediately because they are visible in customer exception reporting. The transportation consultant warns that unclear execution ownership could create planning exceptions and settlement disputes. The constraint is to deliver a stable first release while preserving kiosk removals as a later controlled transition scope.
Which blueprinting decision best supports the rollout constraint?
Response:

• A. Delay planned hub replenishment until kiosk removals can use the same transportation and settlement model.
• B. Activate planned hub replenishment first and define kiosk removals as later-wave scope after authorization, dismantling ownership, and carrier confirmation are validated.
• C. Configure freight settlement for kiosk removals first so cost postings determine whether the flow is operationally ready.
• D. Include kiosk removals immediately so customer exception reporting captures all visible transportation demand.