In SAP S/4HANA Transportation Management, when no agreement determination condition is used, the system relies on thecarrierandpurchasing organizationto determine the correct freight agreement for charge calculation in a freight order. According to the SAP documentation, the carrier (the party providing transportation services) and the purchasing organization (the organizational unit responsible for procurement) are key involved parties in the freight agreement. The freight agreement is selected based on the carrier assigned to the freight order and the purchasing organization defined in the document, ensuring that the correct rates and conditions are applied.
The other options are incorrect:
* Ordering party (B)is typically the customer or shipper requesting transportation but is not directly used to determine the freight agreement unless specified via conditions.
* Executing carrier (D)is redundant with the carrier (A), as the carrier assigned to the freight order is considered the executing carrier.
Reference:
SAP S/4HANA Cloud Private Edition, Transportation Management Study Guide: Unit 5 - Charge Calculation and Freight Settlement, Section on Freight Agreement Determination.
SAP Help Portal: Transportation Management - Freight Agreements ().

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.
Reference:
SAP S/4HANA Cloud Private Edition, Transportation Management Study Guide: Unit 5 - Charge Calculation and Freight Settlement, Section on Freight Settlement Documents.
SAP Help Portal: Transportation Management - Freight Settlement ().

In SAP S/4HANA Transportation Management, incompatibilities are used to define restrictions during automatic and manual planning to prevent certain combinations of objects. According to the SAP documentation, the following incompatibility types are valid in the Automatic and Manual Planning incompatibility area:
* Vehicle resource - Location (stay level) (A): This incompatibility type restricts a vehicle resource from staying at a specific location (e.g., due to regulatory or operational constraints).
* Freight unit - Freight booking (C): This type prevents specific freight units from being assigned to certain freight bookings (e.g., for ocean or air transport) due to incompatibilities like cargo type or equipment restrictions.
The other options are incorrect:
* Transportation request header - Transportation request header (B)is not a standard incompatibility type for planning; it is more relevant to freight unit building or other processes.
* Carrier - Transportation order (D)is used in carrier selection or tendering, not in the Automatic and Manual Planning incompatibility area.
Reference:
SAP S/4HANA Cloud Private Edition, Transportation Management Study Guide: Unit 3 - Transportation Planning, Section on Incompatibilities.
SAP Help Portal: Transportation Management - Incompatibility Settings ().