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

In SAP S/4HANA Transportation Management, to plan freight units with multiple stages and assign different carriers to each stage, you define the carriers in thetransportation lane (C). According to the SAP documentation, transportation lanes specify the valid carriers for specific routes or stages, including multi-leg scenarios. By configuring different carriers for each stage within the transportation lane, the system ensures that the appropriate carrier is assigned during planning for each leg of the transport.

The other options are incorrect:

Schedule (A)defines departure times and carriers for regular transports but is not used for stage-specific carrier assignments in freight units.

Default route (B)is used for simplified routing but does not support detailed stage-specific carrier assignments.

Carrier profile (D)contains carrier attributes but does not define stage-specific assignments for freight units.

In SAP S/4HANA Transportation Management, a business partner with the role Driver is defined in the master data with specific attributes. According to the SAP documentation:

Non-working times and absences (C): These attributes specify the driver’s availability, including holidays, vacations, or other non-working periods, critical for planning.

Validity period (D): The validity period defines the time frame during which the driver is active in the system, ensuring assignments are time-relevant.

The other options are incorrect:

Fixed assignment to a vehicle resource (A)is optional and managed in vehicle resource master data, not a mandatory driver attribute.

Planning profile (B)is used for planning settings, not for defining driver attributes.

In SAP Business Network for Logistics, dispute management allows carriers to interact with freight settlement documents to resolve discrepancies. According to the SAP documentation:

Upload files (A)is a supported activity, as carriers can upload documents (e.g., proof of delivery or additional evidence) to support their dispute claims.

Add a detention charge (B)is allowed, as carriers can add assessorial charges, such as detention charges, to address additional costs incurred during transportation.

The other options are incorrect:

Change the document currency (C)is not typically allowed in dispute management, as the currency is defined in the freight agreement or settlement document.

Change a charge line's calculation base (D)is managed by the shipper or system configuration, not by the carrier during dispute management.

In SAP S/4HANA Transportation Management, conditions are used to determine specific objects or settings during charge calculation based on predefined rules. According to the SAP documentation:

Freight agreement (A): Conditions can be used to select the appropriate freight agreement based on attributes like carrier, purchasing organization, or transportation lane.

Rate table (D): Conditions can determine the specific rate table to be used for charge calculation, based on criteria such as source/destination or service type.

The other options are incorrect:

Carrier in the freight agreement (B)is determined during carrier selection, not through conditions in charge management.

Validity date of the rate table (C)is defined in the rate table configuration and is not determined dynamically via conditions.

In SAP S/4HANA Transportation Management, freight units are created based on sales order items, with the freight unit building rule strategy determining consolidation. With the settings "Build freight units automatically" and "consolidate as much as possible," the system combines items into the fewest possible freight units, provided no incompatibilities exist. According to the SAP documentation:

Two sales orders with three items each result in six items total.

Since the items are for the same customer, have the same delivery date, and have no incompatibilities, the "consolidate as much as possible" strategy combines all six items intoone freight unit (A), assuming other criteria (e.g., same source/destination) are met.

The other options are incorrect:

B (3)andC (6)assume less consolidation (e.g., one freight unit per sales order or item).

D (2)assumes one freight unit per sales order, which is not the maximum consolidation.

In SAP S/4HANA Transportation Management, the freight unit type defines key settings that govern the behavior of freight units during planning and execution. According to the SAP documentation, the freight unit type controls:

Direct shipment options (A): Specifies whether the freight unit can be converted directly to a freight order for direct shipment scenarios.

Freight unit building rule (C): Determines how freight units are created and consolidated (e.g., based on sales order items or deliveries).

Organizational unit determination (E): Defines which organizational units (e.g., planning or execution units) are responsible for the freight unit.

The other options are incorrect:

Tendering settings (B)are defined in tendering profiles, not freight unit types.

Change controller settings (D)are configured at the document level (e.g., freight order) or in change controller strategies, not in freight unit types.

When an assessorial charge is added to a freight order after the initial freight settlement document (FSD) is posted, and the change strategy is set to "Reverse and Repost with new FSD," the system handles the update as follows, according to SAP documentation:

2 FSDs and 1 credit memo in transportation management (B): The original FSD is reversed with a credit memo, and a new FSD is created to include the assessorial charge, resulting in two FSDs (the original and the new) and one credit memo.

3 FSDs in transportation management (C): This includes the original FSD, the credit memo (counted as a separate document in some configurations), and the new FSD with the updated charges.

The other options are incorrect:

1 purchase order in materials management (A)is not guaranteed, as the number of purchase orders depends on the original setup and may not change with the FSD update.

3 service entry sheets in materials management (D)is unlikely, as typically one service entry sheet is updated or replaced, not multiplied, during the reversal and reposting process.

In SAP S/4HANA Transportation Management, thedistribution profileis directly assigned to an organizational unit to define how costs are distributed across different entities, such as cost centers or internal orders, during freight settlement. According to the SAP documentation, the distribution profile is linked to the organizational unit (e.g., a purchasing organization) to specify rules for cost allocation in materials management integration scenarios. This ensures that transportation costs are correctly assigned based on organizational structure.

The other options are incorrect:

Charges profile (A)defines the structure of charges but is not directly assigned to an organizational unit; it is used in freight agreements or calculation sheets.

Calculation profile (B)determines how charges are calculated but is assigned to documents like freight orders, not organizational units.

Dimensional weight profile (D)is used for calculating dimensional weight and is linked to calculation profiles, not organizational units.

Basic Shipping in SAP S/4HANA Supply Chain for Transportation Management provides limited transportation management functionality compared to Advanced Shipping. According to the SAP documentation, the following features are available:

Transportation execution without event management (A): Basic Shipping supports execution processes like freight order creation and carrier assignment but does not include event management capabilities.

Transportation planning based on inbound deliveries (B): Basic Shipping allows planning for inbound deliveries, enabling transportation requirements to be managed for goods receipt.

Transportation planning based on outbound deliveries (C): Basic Shipping supports planning for outbound deliveries, covering the shipping process from warehouses to customers.

The other options are incorrect:

Transportation planning based on forwarding orders (D)is part of Advanced Shipping, typically used in logistics service provider scenarios.

Transportation planning based on sales orders (E)is not directly supported in Basic Shipping, as sales orders trigger order-based transportation requirements in Advanced Shipping.

In SAP S/4HANA Transportation Management, forwarding orders in LSP scenarios allow users to specify transportation details directly. According to the SAP documentation:

Movement type (A): Users can enter the movement type in the forwarding order to define the transportation mode (e.g., road, rail) for specific stages.

Shipping type (C): The shipping type can be specified to categorize the overall transport mode (e.g., full truckload, less-than-truckload), influencing how the transport is executed.

The other options are incorrect:

Instruction set (B)is assigned via configuration (e.g., to stage types or forwarding order types) but is not directly entered in the forwarding order.

Stage profile (D)is assigned to determine stage sequences but is not manually entered as a field in the forwarding order.