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

Explanation:

In SAP S/4HANA Transportation Management, business shares allocate predefined transportation volumes to specific carriers. Two Fiori apps control whether these shares are considered during carrier selection.

A. Edit Freight Agreement
– Correct. Business shares are defined during strategic freight procurement. When creating a Request for Quotation (RFQ) for a freight agreement, you specify target share strategies, including minimum and maximum percentages for carriers . This establishes the business share targets.

C. Edit Carrier Carrier Selection Settings
– Correct. This app controls the operational use of business shares during automatic carrier selection. The settings include a "Business Share Usage" parameter that determines whether the system considers business shares when generating carrier rankings . As per SAP Learning, if business shares should influence carrier selection, this must be defined here .

Why Other Options Are Incorrect:
B. Create Business Share
– Incorrect. This app defines the business share values (percentages, tolerances, penalty costs) . However, the question asks where you define whether shares are considered in carrier selection, which is activated in the carrier selection settings, not in the business share master data.

D. Define Transportation Lane
– Incorrect. Transportation lanes store business share information and can reference shares . However, the activation of business share consideration during carrier selection is controlled exclusively in the carrier selection settings, not in lane definitions.

Reference:
SAP Help Portal and SAP Learning documentation confirm that business share is a carrier selection strategy option, and carrier selection settings govern its usage .

Explanation:

In SAP Transportation Management, track and trace functionality monitors the execution of transportation processes. Here are the business documents that can be used as a base for tracking:

A. Freight order
– Correct. Freight orders are primary execution documents in TM and can be tracked. SAP documentation confirms that execution tracking reports the tracking of freight orders . You can enable this in Customizing under Freight Order Management → Freight Order → Define Freight Order Types by setting "Execution Tracking Relevance" .

C. Service order
– Correct. Service orders are explicitly listed as trackable objects in SAP TM. SAP Learning materials confirm that "instruction execution for standard operating procedures" (which includes service orders) is provided with tracking and tracing functionality .

Why the other options are incorrect:

B. Resource
– Incorrect. While resources (vehicles, equipment) appear in search results as trackable objects in SAP Event Management contexts , they are not base business documents for track and trace. Resources are master data elements that support execution documents but don't initiate tracking processes themselves.

D. Forwarding order
– Incorrect. Forwarding orders are commercial documents used in freight forwarding scenarios . They are not listed among documents with tracking and tracing functionality in SAP TM documentation. Tracking is applied to execution documents (freight orders, freight bookings) rather than commercial forwarding documents.

References:
SAP Learning documentation confirms tracking is provided for freight units, freight orders, freight bookings, transportation units, resources, and instruction execution (service orders) .

Explanation:

In SAP Transportation Management, the calculation profile is directly assigned to an organizational unit. This assignment determines how freight charges are calculated for that specific organizational unit during transportation processes.

Why Calculation Profile is correct:

The calculation profile contains settings for transportation charge calculation, including calculation date type, calculation level, agreement determination rules, and default dimensional weight profile . SAP documentation confirms that you can assign a calculation profile to an organizational unit, and if assigned to both organizational unit and business partner role, the system applies the profile for the business partner role . Table /SCMTMS/C_FASET (Org Unit settings for Charge Management) shows the direct link between organizational unit and calculation profile fields, including CALC_PROFILE and PURCH_CALC_PROF .

Why other options are incorrect:

A. Charges profile
– Incorrect. This is not the standard term used in SAP TM for profiles assigned to organizational units. The search results do not mention a "charges profile" in this context.

C. Distribution profile
– Incorrect. While table /SCMTMS/C_FASET shows a field DISTR_PROFILE (Distribution Profile) linked to organizational units , this field exists alongside calculation profiles and is not the primary profile referenced in documentation for direct organizational unit assignment.

D. Dimensional weight profile
– Incorrect. Dimensional weight profiles define DIM factors for chargeable weight calculation . They are maintained separately in configuration (SPRO → TM → Basic Functions → Charge Calculation → Data Source Binding → Define Dimensional Weight Profiles) and are assigned to freight agreements, not directly to organizational units.

References:
SAP TM documentation , table /SCMTMS/C_FASET structure , and SAP Community blogs on dimensional weight configuration .

Explanation:

In SAP Transportation Management, the freight order is the primary execution document used to trigger integration with SAP Extended Warehouse Management (EWM). The integration is specifically designed around the freight order as the central object for communication .

Why Freight Order is Correct:

The integration between TM and EWM is triggered from the freight order when it reaches a specific status. Once the item status of a freight order is set to "Cargo Ready for Loading" (for outbound) or "Cargo Ready for Unloading" (for inbound), TM automatically sends a TransportationOrderLoadingAppointmentRequest message to EWM . This message triggers the creation of transportation units (TUs) and vehicle activities in EWM, enabling warehouse execution based on the transportation plan . Additionally, you must configure the freight order type in Customizing as "relevant for EWM" to enable this integration .

Why Other Options Are Incorrect:

A. Freight unit
– Incorrect. While freight units are planning objects created from orders or deliveries , they do not directly trigger EWM integration. The integration message is sent from the freight order after planning is completed .

C. Consignment order
– Incorrect. Consignment orders appear in documentation related to GTS integration for export declarations , but they are not the document that triggers the core TM-EWM loading appointment integration.

D. Package unit
– Incorrect. Package units are not mentioned in any search results as a document for triggering TM-EWM integration. Packing information (handling units) is exchanged between systems as part of the integration , but not as the triggering document.

References:
SAP Help Portal documentation confirms that when a freight order status is set to "Cargo Ready for Loading," a TransportationOrderLoadingAppointmentRequest message is automatically sent to EWM .

Explanation:

In a greenfield project, you have the advantage of establishing a clean core from the start. For data quality, SAP defines six key facets, with accuracy and timeliness being fundamental requirements .

A. Accuracy is correct because it ensures data correctly reflects business reality.
Inaccurate data leads to incorrect decision-making and inefficient processes. To maintain accuracy, implement data validation rules, perform regular quality checks, and establish data governance processes .

C. Timeliness is correct because outdated or stale data negatively impacts decision-making and business operations.
For a greenfield implementation, implementing real-time data capture and integration processes, defining data refresh schedules, and setting up monitoring mechanisms are essential for ensuring up-to-date data .

Why the other options are incorrect:

B. Stability – Incorrect.
While system stability is a benefit of clean core , it is not one of the six defined data quality aspects. Stability relates more to system operations than data quality itself.

D. Efficiency – Incorrect.
Data volume efficiency (removing redundant data) is important for clean core , but efficiency is not one of the six core data quality facets. The six facets are accuracy, completeness, consistency, timeliness, validity, and uniqueness .

References:
SAP Learning documentation confirms the six facets of modern data quality requirements for clean core compliance .

Explanation:

A. Transportation zones transfer their properties to their locations. ✅
This is a key feature designed to minimize master data maintenance. When you assign properties to a transportation zone, the system can propagate (transfer) some of those properties to all locations within that zone . This eliminates the need to maintain the same data repeatedly for every individual location.

D. Transportation zones are used to group locations. ✅
This is the fundamental definition of a transportation zone. It is a business object specifically created to aggregate multiple locations into a single, manageable unit . This grouping simplifies planning, as you can plan routes to and from a zone (e.g., "Southern Germany") rather than having to manage hundreds of individual customer locations within it.

Why the Other Options Are Incorrect

B. Transportation zones are physical locations. ❌
This is incorrect. A transportation zone is a logical grouping object, not a physical entity . Unlike a location, a transportation zone does not have a physical address . While geographical coordinates can be assigned to a zone, this is often done by calculating a center point based on its member locations, not because the zone itself is a physical place.

C. Transportation zones increase the effort needed to model the network. ❌
This is the opposite of the truth. Transportation zones are explicitly designed to reduce the effort needed to model the transportation network . By grouping locations and allowing properties to be transferred, zones dramatically simplify master data maintenance and make the network more manageable.

References
SAP Help Portal: Defines a transportation zone as an object that groups a number of locations and transfers properties to them . SAP Learning: Confirms that transportation zones aggregate multiple locations and propagate properties, minimizing master data volume . SAP S/4HANA Documentation: Details the process of defining zones by assigning or excluding locations .