Learn, Practice, and Improve with SAP C_S4TM_2023 Practice Test Questions

Explanation:

In your scenario, you have fixed-price contracts with carriers who have guaranteed availability. This means you don't need to solicit bids or compare offers—you simply need to assign the transport to a contracted carrier efficiently. The "No Response Required" tendering type is designed precisely for this situation.

D. Use tendering with the Peer-to-Peer Tendering
- No Response Required type is correct because this tendering type sends the freight order directly to a carrier without requiring them to actively accept it. As explained in SAP Learning documentation, "the system generally awards a carrier if he or she does not reject the road FO within a given time limit" . This streamlines the process by assuming carrier acceptance based on their contractual commitment, eliminating unnecessary back-and-forth communication while still providing an opt-out mechanism if the carrier cannot perform.

Why the other options are incorrect:

A. Use carrier selection with the Assign Best Carrier option
– Incorrect. Carrier selection with "Assign Best Carrier" is used when you need to evaluate multiple carriers based on costs, priorities, or business shares to determine the optimal choice . Since you already have fixed-price contracts with guaranteed availability, there's no need for comparative evaluation—the carrier is predetermined.

B. Use carrier selection with the Automatic Tendering option
– Incorrect. Automatic tendering is used when no carrier is directly assigned, triggering a procurement process to find one . This adds unnecessary steps when you already have committed carriers.

C. Use tendering with the Broadcast Tendering - First Acceptable Offer type
– Incorrect. Broadcast tendering sends requests to multiple carriers simultaneously and selects either the first acceptable offer or the best offer after response time expires . This competitive bidding process contradicts your scenario of fixed-price contracts with guaranteed carrier availability.

References
: SAP Learning documentation confirms that in direct/peer-to-peer tendering with no response required, "the system generally awards a carrier if he or she does not reject the road FO within a given time limit" . This approach leverages existing contracts while maintaining an exception path for carrier rejection.

Explanation:

In SAP S/4HANA Transportation Management (TM), the display and organization of worklists (such as the Forwarding Order personal object worklist or POWL) are primarily controlled through Page Layouts.

Define a new page layout (Choice B):
This is the correct technical approach. Within the TM UI framework (Floorplan Manager), a page layout allows a user or consultant to define which columns are visible, the sequence of those columns, and how the data is grouped. By creating or modifying a page layout, you can specifically "hide" or "show" fields to ensure the forwarding order worklist only displays the data relevant to the specific business role.

Why Other Options are Incorrect:

Define a new view (Choice A):
While "views" exist in various SAP technologies (like SAPUI5 or ABAP List Viewer), in the specific context of TM worklist configuration, the configuration entity is the Page Layout. A view typically refers to a saved set of selection criteria rather than the structural layout of columns.

Define a new query (Choice C):
A query is used to define the selection criteria (the "What") of the worklist—for example, filtering for all forwarding orders created in the last 24 hours. It does not control the visual display or column count of the results table.

Apply a filter (Choice D):
Filtering is a runtime activity used to narrow down the rows displayed based on specific data values within a column. It does not remove or limit the columns themselves from the UI.

References
SAP Help Portal: Transportation Management (TM) > UI Technologies in TM > Page Layouts.
SAP Learning Journey: S4TM1 (Business Processes in SAP S/4HANA TM) – Unit: Master Data and General Functions.

Explanation:

In SAP Transportation Management, when you need to model a scenario where a single trailer is hauled by more than one truck (e.g., trailer swap or coupling/uncoupling at different locations), you must customize specific document types to support this complexity.

A. Transportation unit type is correct because transportation units (specifically trailer units) are the key objects used to model trailers that can be coupled and uncoupled from trucks .
The transportation unit type must be defined in Customizing to configure the most important settings for how these trailer units behave . For trailer swap scenarios, you need to define at which locations coupling or uncoupling takes place, and to or from which tractor the trailer is coupled .

D. Freight order type is correct because the freight order represents the capacity document (the truck/tractor) that hauls the trailer unit .
You can assign the trailer unit to a freight order, and the system automatically transfers the transportation unit items . The freight order type configuration controls how these assignments work and how the combined vehicle is processed .

Why the other options are incorrect:

B. Forwarding order type – Incorrect.
Forwarding orders are commercial documents in freight forwarding scenarios . While you can create forwarding orders from transportation units , the forwarding order itself is not the document you customize for the truck-trailer physical coupling scenario.

C. Freight booking type – Incorrect.
Freight bookings are capacity documents primarily used for ocean and air transportation . While transportation units (containers) can be assigned to freight bookings , freight booking types are not relevant for configuring the truck-trailer coupling scenario.

References:
SAP Help Portal documentation confirms that for trailer units, you define coupling/uncoupling locations and assign them to freight orders . SAP Community blogs explain that trailer units are required specifically when trailers get loaded/unloaded while not coupled to the truck .

Explanation:

When you add an assessorial charge to a freight order after the FSD has been posted and accruals booked, the background report determines the change strategy "Reverse and Repost with new FSD." This triggers a specific sequence of documents in both systems.

B. 2 FSDs and 1 credit memo in transportation management is correct because the reverse and repost strategy creates a credit memo to cancel the original FSD, followed by a new FSD containing the updated charges (including the new assessorial charge) . SAP documentation confirms that "the system creates a credit memo to reverse the settlement document" and then "creates a new settlement document for the total amount in the freight order" . This results in two FSDs (original + new) and one credit memo in TM.

D. 3 service entry sheets in materials management is correct because each FSD creates a corresponding service entry sheet (SES) in MM for accrual posting . Additionally, when the credit memo is transferred to MM, it creates a return SES to reverse the original accruals . The sequence produces: original SES (from first FSD), return SES (from credit memo reversal), and new SES (from new FSD) = three service entry sheets total.

Why the other options are incorrect:

A. 1 purchase order in materials management – Incorrect.
The purchase order remains the same throughout the process; it is not recreated. Only service entry sheets are created and reversed against the existing PO .

C. 3 FSDs in transportation management – Incorrect.
The reverse and repost strategy creates exactly one credit memo and one new FSD, resulting in two FSDs total (original plus new), not three FSDs .

References:
SAP Learning documentation confirms the reverse and repost process flow , and SAP Help Portal details that a credit memo cancels the existing settlement document before creating a new one .

Explanation:

In SAP Transportation Management, the "Automatic and Manual Planning" incompatibility area controls how planning objects are assigned during both automated (VSR optimizer) and manual planning processes .

A. Vehicle resource -
Location (stay level) is correct because this incompatibility type prevents specific vehicles from being assigned to particular locations where they cannot be loaded or unloaded due to physical constraints such as ramp height or space limitations . This ensures that during both automatic and manual planning, vehicles are not routed to incompatible locations.

D. Transportation request header -
Transportation request header is correct because it defines incompatibilities between two transportation request headers. This type prevents specific transportation requests from being combined in the same shipment or freight order, which is useful when certain orders must be kept separate due to customer requirements, delivery constraints, or other business rules .

Why the other options are incorrect:

B. Freight unit - Freight booking – Incorrect.
While freight units can be assigned to freight bookings (capacity documents for ocean/air), this is not a standard incompatibility type in the planning area. Freight bookings are managed through different mechanisms .

C. Carrier - Transportation order – Incorrect.
Carrier selection has its own dedicated incompatibility area separate from automatic and manual planning . Carrier-related incompatibilities are handled in the carrier selection incompatibility area, not in the planning incompatibility area.

References:
SAP Help Portal confirms that incompatibility types define the business objects between which an incompatibility is valid, and these are assigned to specific incompatibility areas including automatic and manual planning

Explanation:

In SAP Transportation Management, specific resource types are designed with capacity definitions to support planning and execution activities .

A. Transportation unit resource is correct because it represents instances like containers used to map capacity for transportation . You can define up to eight dimensions and units of measurement to describe its capacity, and planning can only consider this capacity if the dimensions correspond to those defined in freight unit building rules . The capacity is typically measured in terms of weight, volume, pallets, or custom units of measurement .

D. Handling resource is correct because it provides the capacity needed to load and unload goods at specific locations such as doors or forklifts . Handling resources include capacity profiles that detail the resource's capacity based on time-dependent shifts, allowing for precise planning of loading and unloading activities .

Why the other options are incorrect:

B. Calendar resource – Incorrect.
A calendar resource is used to specify operating hours for a location, determining when goods can be dropped off or picked up . Its capacity is NOT utilized during scheduling; the system only takes the calendar into consideration, and it cannot be scheduled finitely .

C. Equipment types – Incorrect.
Equipment types are templates used to define physical properties of resources such as containers, including capacity and weight . However, they are not themselves resources that represent capacity; they are used as templates to create transportation unit resources .

References:
SAP Learning documentation confirms the four main resource types in TM (vehicle, handling, calendar, and transportation unit) and explains which represent capacity for planning .

The correct answers for the SAP C_S4TM_2023 exam regarding the use of conditions in charge management are: Correct Answers: A and D Explanation In SAP S/4HANA Transportation Management (TM), Conditions are a flexible tool used to determine business entities based on specific attributes of a business document (such as a Freight Order or Forwarding Order). Within the Charge Management module, conditions are extensively used to automate the selection of the correct pricing master data. Freight Agreement (Choice A): This is one of the most common applications of conditions. Instead of the system simply looking for a direct link, a condition can be defined to determine the correct Freight Agreement based on criteria like the purchasing organization, the shipping point, or the transportation mode. This allows the system to dynamically select which contract should be used for calculation. Rate Table (Choice D): Within a calculation sheet, you can assign a condition to a charge line to determine which Rate Table should be accessed. This is particularly useful when different rate tables apply under different scenarios (e.g., different seasonal rates or rates based on specific equipment types) that aren't easily handled by standard scale lookups alone. Why Other Options are Incorrect: Carrier in the Freight Agreement (Choice B): While conditions can help determine a Freight Agreement, the carrier is typically a mandatory header component of the agreement itself or determined during the Carrier Selection process (which uses its own set of constraints and rankings), not directly through a Charge Management condition. Validity Date of the Rate Table (Choice C): The validity dates are maintained as part of the master data within the Rate Table or the Freight Agreement lines. They are static attributes of the record used to ensure the rate is current; they are not "determined" by a condition during the calculation process. Valid References SAP Help Portal: Transportation Management (TM) > Charge Management and Service Product Catalogs > Conditions in Charge Management. SAP Learning Journey: S4TM3 (SAP S/4HANA TM Transportation Charge Management) – Unit: Basic Charge Management Settings.