In an SAP S/4HANA Cloud Greenfield project, maintaining a clean core focuses on ensuring the system remains standard, extensible, and efficient with high-quality data. According to the SAP documentation, key aspects for clean core data quality include:

Stability (B): Ensuring data stability prevents inconsistencies and errors, supporting a reliable and maintainable system core.

Efficiency (D): Efficient data processes reduce redundancy and improve performance, aligning with clean core principles of streamlined operations.

The other options are incorrect:

Accuracy (A)is important for data quality but is not specifically emphasized as a clean core principle, which focuses more on system stability and efficiency.

Timeliness (C)relates to data availability but is less critical for clean core data quality compared to stability and efficiency.

In SAP S/4HANA Transportation Management, adimensional weight profileis used to calculate the dimensional weight of goods, which is often used for charge calculations in scenarios where volume impacts costs (e.g., air freight). According to the SAP documentation, the dimensional weight profile is assigned to thecalculation profile, which defines the rules and settings for charge calculation, including how dimensional weight is factored into the cost. This allows the system to apply the dimensional weight logic consistently across relevant freight orders or agreements.

The other options are incorrect:

Charge type (A)defines specific charge categories (e.g., base freight, fuel surcharge) but does not directly support dimensional weight profiles.

Charges profile (B)structures the charges but is not used for dimensional weight assignments.

Calculation base (D)refers to the basis for charge calculations (e.g., weight, distance) but does not hold dimensional weight profiles.

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.