Free SAP C_S4TM_2023 Practice Exam with Questions & Answers | Set: 3

In SAP S/4HANA Transportation Management, freight settlement documents (FSDs) are created based on freight orders to settle charges with carriers. According to the SAP documentation, there isno limitto the number of FSDs that can be created from a freight order during its lifecycle, as additional FSDs can be generated for changes, such as additional charges, corrections, or disputes, provided the charge elements have non-zero values. For a freight order with two deliveries, multiple FSDs can be created to account for initial settlements, amendments, or additional charges (e.g., detention or assessorial charges) throughout the lifecycle.

The other options are incorrect:

A (3), B (1), and C (2)assume a fixed number of FSDs, which is not accurate since the system allows multiple FSDs based on changes or additional requirements.

In SAP S/4HANA Transportation Management, discrepancies in freight orders (e.g., differences in weight, quantity, or other attributes) can trigger blocks when they exceed configured tolerances. These blocks prevent certain actions until the discrepancy is resolved. According to the SAP documentation, when a discrepancy outside the tolerance is reported for a freight order:

An execution block for the freight order (A)is set to prevent further execution steps, such as loading or departure, until the discrepancy is resolved.

An execution block for the freight unit (B)is applied because the freight unit is directly tied to the goods being transported, and a discrepancy affects its execution status.

An invoicing block for the freight order (E)is set to ensure that no invoicing occurs until the discrepancy is addressed, as the charges may be impacted.

The optionsC (invoicing block for the freight unit)andD (planning block for the freight order)are not typically applied:

Invoicing blocks are generally applied at the freight order level, not the freight unit level, as invoicing is managed through freight orders or freight bookings.

A planning block for the freight order is not relevant, as discrepancies typically affect execution or invoicing rather than planning, which occurs earlier in the process.

In SAP S/4HANA Transportation Management, the path finder is a tool used to analyze and visualize transportation routes and networks, helping planners understand possible paths for freight. According to the SAP documentation:

Transportation network cockpit (C): This transaction provides a comprehensive interface for managing transportation planning, including the ability to run the path finder to analyze routes and connections within the transportation network.

Explanation tool (D): The explanation tool allows users to analyze the results of planning activities, including running the path finder to understand the routes considered by the optimizer or manual planning.

The other options are incorrect:

Carrier selection (A)focuses on selecting carriers based on criteria like cost or priority, not on running the path finder.

Edit freight order (B)is used to modify freight order details but does not directly support running the path finder.

In a shipper-to-LSP B2B scenario where both parties use SAP Transportation Management, the LSP plans and executes transportation for the shipper. According to the SAP documentation, the key documents involved are:

LSP’s forwarding quotation (A): The LSP creates a forwarding quotation to provide a price estimate to the shipper, which forms the basis for the transportation agreement.

Shipper’s freight unit (D): The shipper creates freight units based on their transportation requirements (e.g., from sales orders), which are transferred to the LSP for planning and execution.

The other options are incorrect:

LSP’s service order (B)is used for internal services, not for shipper-LSP interactions.

Shipper’s freight order (C)is created by the shipper for direct carrier execution, not in a scenario where the LSP handles planning and execution.