SAP C_S4TM_2023 - SAP Certified Associate - SAP S/4HANA Cloud Private Edition, Transportation Management

In SAP S/4HANA Transportation Management, forwarding orders in LSP scenarios contain item hierarchies with categories like passive vehicle, package, service, and product. According to the SAP documentation, theservice (C)item category is not considered in subsequent execution documents (e.g., freight orders or freight bookings). Service items represent non-physical services (e.g., customs clearance) and are used for costing or documentation in the forwarding order but are not relevant to execution documents, which focus on physical goods and equipment.

The other options are incorrect:

Passive vehicle (A)represents equipment like trailers and is included in execution documents for transport planning.

Package (B)represents packaging units and is considered in execution documents for load planning.

Product (D)represents the goods being transported and is critical in execution documents.

In SAP S/4HANA Transportation Management, integration with SAP Extended Warehouse Management (EWM) is triggered from thefreight order. According to the SAP documentation, the freight order is the execution document that contains the planned transportation details, such as the assigned carrier, vehicle, and schedule. It serves as the basis for communicating transportation requirements to the warehouse for picking, packing, and loading activities. The integration between SAP TM and SAP EWM typically occurs during the execution phase, where the freight order triggers processes like loading or staging in the warehouse.

The other options are incorrect:

Freight unit (A)represents the logistical unit of goods but is not directly used to trigger EWM integration; it is linked to the freight order for execution.

Consignment order (C)is a logical grouping for communication between shippers and consignees, not for warehouse integration.

Package unit (D)is used for packaging-related data and does not trigger EWM integration.

Carrier selection in SAP S/4HANA Transportation Management can be initiated from specific interfaces or tools designed for planning and tendering. According to the SAP documentation:

From report /SCMTMS/PLN_OPT (A)allows users to trigger carrier selection as part of the transportation planning process, typically used for automated or manual planning.

From SAP Business Network for Logistics (C)enables carrier selection through tendering processes, where carriers are invited to bid on freight orders.

The other options are incorrect:

Freight booking user interface (B)is used for managing bookings (e.g., ocean or air transport) but is not typically used to initiate carrier selection, which is more aligned with freight orders.

Container unit user interface (D)is used for managing container-related data but does not support carrier selection.

To configure a scenario in SAP S/4HANA Transportation Management where a single trailer is hauled by multiple trucks (e.g., in a multi-leg transport), specific customizations are required:

Transportation unit type (A): According to the SAP documentation, the transportation unit type must be configured to allow a trailer to be defined as a separate entity that can be attached to different trucks during various stages of transport. This ensures the trailer is treated as a distinct resource.

Freight order type (D): The freight order type must be customized to support multi-leg scenarios, including settings for stage-specific assignments of trucks to the same trailer, enabling the system to manage the trailer across multiple freight orders.

The other options are incorrect:

Forwarding order type (B)is used for logistics service provider scenarios and does not directly manage trailer-truck assignments.

Freight booking type (C)is relevant for ocean or air transport, not for road-based multi-truck scenarios.