Explanation:

For a product to be delivered, the system must allow delivery creation at the sales order item level. The "Item Relevant for Delivery" indicator (D) is the fundamental switch that determines if a sales document item can be included in a delivery document. Without this, the item will be blocked from delivery processing entirely. The "Schedule Lines Allowed" indicator (A) controls whether schedule lines (which carry the delivery quantity and dates) can be created for the item. A delivery requires these schedule lines to determine what and when to deliver.

Why the other options are incorrect:

B (Relevant for delivery-related billing):
This links the delivery to billing, but is not a prerequisite for creating the delivery itself. You can create deliveries without this setting; billing simply wouldn't be triggered automatically.

C (Copying control in Logistics Execution):
This governs data transfer from the sales order to the delivery, but it is not a mandatory setting to allow delivery creation. It refines how data is copied once delivery is allowed by the item category settings (A & D).

Reference:
SAP S/4HANA Sales documentation on Item Category Determination and Delivery Processing states that for an item to be deliverable, the item category must be configured with both the "Delivery" and "Schedule line" relevancies (SAP Help Portal: "Define Item Categories" and "Schedule Line Categories").

Explanation:

In an SAP S/4HANA Cloud greenfield project, maintaining clean core data quality is essential to ensure reliable processes, compliance, and scalability. Two critical aspects to focus on are accuracy and timeliness.

Accuracy (B):
Accurate data ensures that business transactions, reporting, and analytics reflect the true state of operations. Inaccurate master or transactional data leads to errors in order processing, financial postings, and compliance reporting. For example, incorrect customer master data can cause delivery failures or billing disputes. SAP emphasizes that clean core principles rely on precise, validated data to avoid downstream inefficiencies and costly corrections.

Timeliness (D):
Timely data entry and updates are equally important. Outdated or delayed information reduces the relevance of analytics and decision-making. For instance, if inventory updates are not recorded promptly, the system may show incorrect stock levels, leading to stockouts or overstocking. Timeliness ensures that the system reflects the current business reality, supporting agile responses to customer and market demands.

Why the other options are not correct:

A. Stability:
While system stability is important, it refers more to technical reliability and performance rather than data quality. Stability is achieved through system architecture and operations, not through clean core data practices.

C. Efficiency:
Efficiency relates to process optimization and resource utilization. Although efficient processes benefit from clean data, efficiency itself is not a direct measure of data quality. Data can be accurate and timely even if processes are not fully optimized.

References

SAP Help Portal – Clean Core Principles in SAP S/4HANA Cloud (help.sap.com in Bing)
SAP Community Blog: Clean Core and Data Quality in SAP S/4HANA Cloud

Explanation:

In SAP S/4HANA Sales, the shipping point is determined at the sales order item level using a combination of master data and document data. The standard determination routine uses three key fields to uniquely identify the correct shipping point for the delivery:

Plant (B):
The plant from the material master (or assigned in the sales order item).

Shipping Conditions (C):
A document-level condition (e.g., immediate delivery, postal shipment) agreed with the customer, stored in the customer master or specified in the order.

Loading Group (E):
A material master classification that groups materials with similar loading requirements (e.g., heavy machinery, refrigerated goods).

The system uses a shipping point determination table (configuration table TVST) where the combination of these three keys points to a specific shipping point.

Why the other options are incorrect:

D. Sales document type:
While the document type influences many other determinations (like billing and pricing), it is not a direct key for shipping point determination in the standard routine.

E. Transportation group:
This is a material master field used for route determination (finding the transportation route), not for determining the shipping point itself.

Reference:
SAP S/4HANA documentation on Delivery Processing and Shipping Point Determination confirms that the plant, shipping condition, and loading group are the primary keys for this determination (SAP Help Portal: "Determination of Shipping Point"). This is a core, stable configuration concept in SAP SD/Logistics Execution.

Explanation:

When configuring a delivery item category, the settings directly control specific item-level behaviors during delivery processing.

Over-delivery allowed (B):
This is a key decision managed in the delivery item category's tolerance settings. It determines if the delivered quantity can exceed the ordered quantity (e.g., for bulk items) and by what percentage.

Route redetermination (C):
This setting dictates whether the transportation route (determined from the sales order) should be recalculated during delivery creation, which may be necessary if shipping conditions or dates have changed.

Why the other options are incorrect:

A. Split by warehouse number:
Delivery splitting rules are typically defined at a higher level in Logistics Execution configuration (e.g., for the delivery document type or plant), not specifically within the settings of a single delivery item category.

D. Storage location determination:
This is governed by material master settings (storage location MRP views) and plant-specific configuration in WM/IM, not by the delivery item category.

Reference:
The configuration for delivery item categories is documented in the SAP Help Portal under "Define Delivery Item Categories" (Logistics Execution -> Shipping -> Basic Shipping Functions -> Delivery -> Define Item Categories for Deliveries). The relevant configuration fields include:

Explanation:

In SAP S/4HANA, the delivering plant for a sales order item can be determined automatically using several configuration sources. The system uses master data and predefined rules to identify the appropriate plant for fulfilling an order.

Sold-to party:

The sold-to party (customer) can have a default delivering plant assigned in the customer master. This ensures that orders from specific customers are automatically linked to a predetermined plant for efficiency in order fulfillment.

Material master:
The material master contains plant-specific data, including the plants where the material is produced or stored. When a sales order is created, the system can select the delivering plant based on material availability, production, or storage data from the material master.

Customer material info record:
This record links a specific material with a customer and can specify a preferred delivering plant. It provides the system with precise plant selection information for customer-specific products, overriding general defaults if required.

Why the other options are incorrect

D. Ship-to party:
The ship-to party defines the delivery address but does not directly determine the delivering plant. While shipping conditions can influence route determination and shipping point selection, plant determination is independent of the ship-to party.

E. Material determination:
Material determination is used to substitute one material for another in sales processes but does not control the plant assignment. It helps in alternative product selection but does not automatically determine the delivering plant for an order item.

References

SAP Fiori Apps Library: Manage Sales Orders – Plant Determination Rules
SAP Training: C_TS462_2023 Exam Guide – Sales Order Configuration and Plant Determination

Explanation:

A billing plan in SAP SD is a tool designed for managing and scheduling multiple invoice documents for a single sales document item over time. The billing plan type is the configuration key that defines the structure and rules for this schedule. Milestone billing is a classic use case, where billing dates and amounts are tied to the completion of predefined project milestones or delivery phases (e.g., for long-term projects, service contracts, or plant engineering). The billing plan type controls how these dates are determined (e.g., based on confirmation dates, fixed dates) and how the values are calculated.

Why the other options are incorrect:

A. Invoice lists:
This is a billing document type function used to combine several individual invoices into one collective document for a customer on a specific date. It is not managed via a billing plan type.

C. Settlement management:
This is a Controlling (CO) or Project System (PS) function used to settle costs to receivers (e.g., cost centers, projects). It is unrelated to SD billing plans.

D. Convergent billing:
This refers to a high-level architecture or solution (like SAP BRIM) for billing diverse services (telecom, utilities) on a single invoice. It is not a specific function of the standard SD billing plan type.

Reference:
SAP S/4HANA SD documentation on Billing Plans explicitly lists milestone billing and periodic billing as primary use cases. The billing plan type configuration determines the dates, pricing, and rules for generating the partial invoices (SAP Help Portal: "Billing Plans").

Explanation:
In SAP S/4HANA, a new plant must be integrated into the sales organizational structure to be available as a delivering plant for sales orders. The critical organizational element for this purpose is the distribution chain, which combines the sales organization and distribution channel. By assigning the plant to a distribution chain, the system recognizes it as a valid source of supply when processing sales orders within that sales organization and distribution channel combination.

Why the other options are incorrect

A. Warehouse number:
Warehouse numbers are linked to physical storage locations and are used in logistics execution and inventory management. They do not control whether a plant is allowed for sales order deliveries.

B. Distribution channel:
A distribution channel alone does not define the combination with a sales organization. The distribution chain (sales organization + distribution channel) is needed for plant assignment.

D. Division:
Divisions categorize products or product lines for reporting and processing purposes. While important for sales order item categorization, a division assignment alone does not determine whether a plant is allowed for delivery.

References:

SAP Help Portal: Assign Plants to Distribution Chains – SAP S/4HANA Cloud Sales
SAP Fiori Apps Library: Manage Sales Organizations – Plant Assignment
SAP Training: C_TS462_2023 Exam Guide – Organizational Structure for Sales and Distribution

Explanation:

This requirement involves configuring text determination to copy header text from a specific source (sold-to party) under specific conditions. The setup follows a structured procedure:

A: The text type (e.g., header note) must be assigned to the sales document type to enable text copying for that document type.

B: This text type must be included in a text determination procedure. The procedure must have an access sequence that defines the order of text sources (e.g., quotation first, then sold-to party).

E: The entire text determination procedure must be assigned to the sales document type for it to be active during order creation.

Why the other options are partially relevant or incorrect:

C (Access sequence reads sold-to party text first):
This is incorrect for the stated requirement. The requirement specifies that the text should be copied from the quotation first. If not found there, then from the sold-to party. Therefore, the access sequence must be Quotation → Sold-to Party, not sold-to party first.

D (Set partner function language to "sold-to party"):
While correct for ensuring the text is in the sold-to party's language when copied from them, this is a detail within the access sequence configuration (specifically in the source text determination settings for the sold-to party access). It is implied by step B ("appropriate access sequence"), but it is not a standalone mandatory step in the listed hierarchy; the core setup steps are A, B, and E.

Reference:
SAP S/4HANA documentation on Text Determination explains that text copying is controlled by a text determination procedure assigned to a document type. The procedure uses an access sequence (e.g., predefined sequence TAXESK) to define the source hierarchy (e.g., preceding document → master data). The partner language for master data texts is configured within the access sequence's source text determination settings (SAP Help Portal: "Text Determination in Sales and Distribution").

Explanation:

SAP recommends using API-based approaches for clean core integrations in S/4HANA to minimize custom modifications and adhere to the “clean core” principle. This principle ensures that the S/4HANA standard system remains as close as possible to SAP’s delivered solution, reducing upgrade and maintenance complexity.

OData APIs:
OData (Open Data Protocol) is SAP’s preferred modern standard for cloud and Fiori-based integrations. It allows CRUD (Create, Read, Update, Delete) operations on SAP business objects in a secure, standardized, and scalable way. OData services are lightweight, support real-time integration, and are ideal for both SAP Fiori apps and external application connectivity, enabling clean core integration without altering SAP standard objects.

SOAP APIs:
SOAP-based web services are another SAP-recommended option for clean integrations. They are standardized, reliable, and widely used for enterprise-to-enterprise (E2E) integrations. SOAP APIs support complex business logic and transactional requirements, making them suitable for integrating with external systems while maintaining the SAP standard without modifications.

Why the other options are incorrect

C. RFC (Remote Function Call):
While RFCs can be used for integration, they often involve direct calls to ABAP function modules, which may require custom coding or modifications. This can violate the clean core principle if standard SAP objects are enhanced.

D. IDoc (Intermediate Document):
IDocs are mainly used for asynchronous data exchange in older or middleware-heavy scenarios. They are not recommended for modern clean core integrations because they often require custom mapping, extra middleware, and additional processing, which increases the complexity and risk of core modifications.

References

SAP Help Portal: API-Based Integration in SAP S/4HANA –
SAP Blog: Clean Core Principle for S/4HANA – SAP Community

Explanation:

The automatic determination of a storage location during delivery creation is primarily controlled by a rule (called the "storage location determination rule" or "checking rule") that is assigned to the shipping point. This rule defines the sequence in which the system searches for a suitable storage location (e.g., based on material master settings, picking area, or storage conditions). The shipping point is the central organizational unit for execution, so it governs this logistics-specific determination.

Why the other options are incorrect:

A. Outbound delivery type:
While the delivery document type influences overall delivery processing, it does not contain the configuration for storage location determination rules.

B. Material:
The material master stores the default storage location (in the MRP or Work Planning views) and can have storage location requirements, but the rule that decides how to find the storage location is not defined here.

C. Outbound delivery item category:
The delivery item category controls item-specific behaviors (e.g., weight calculation, packing) but not the storage location determination rule.

Reference:
SAP S/4HANA documentation on Storage Location Determination confirms that the determination rule is configured and assigned to the shipping point. The path in customizing is: Logistics Execution → Shipping → Basic Shipping Functions → Delivery → Define Storage Location Determination (SAP Help Portal: "Storage Location Determination in Shipping").

Explanation:

A billing type is a key configuration object that controls the behavior of billing documents (invoices, credit memos, etc.). Among its settings are:

A. Billing type for cancellation:
Defines which billing document type should be used to cancel (reverse) a document created with this billing type (e.g., an invoice is cancelled with a cancellation invoice).

B. Reference mandatory indicator:
Specifies whether a billing document of this type must be created with reference to a preceding document (e.g., a delivery or another billing document).

Why the other options are incorrect:

C. Default delivery type for billing:
This is not configured in the billing type. The relationship between billing and delivery is controlled by copying control settings (e.g., which delivery types can be billed with which billing types).

D. Item number increment:
This is configured at the document type level in the Sales Document Header configuration (e.g., for sales orders, quotations), not specifically for the billing type.

Reference:
SAP S/4HANA configuration for billing types includes these fields in transaction VOFA or the SPRO path: Sales and Distribution → Billing → Billing Documents → Define Billing Types (SAP Help Portal: "Billing Types"). The "Cancellation billing type" and "Reference mandatory" are standard configuration fields within this activity.

Explanation:

In SAP S/4HANA, a service item in a sales order represents a service that does not involve the physical delivery of goods. Examples include consulting, maintenance, or support services. Because no physical product is shipped, certain fields and processes that are mandatory for material items are not relevant for service items.

A key characteristic of service items is that the Delivering Plant field is not required (Answer C). The delivering plant is relevant for physical goods to identify the source of supply for delivery processing. For services, no material is being issued from a plant, so the system does not require a delivering plant. This simplifies order entry and ensures that service items can be processed without linking to physical logistics processes.

Why the other options are incorrect

A. The material has a specific item category group:
While the item category determines that the item is a service, the “material item category group” refers to materials in the material master, which is not relevant for service items since services do not require material master linkage.

B. The item in the sales order is blocked for delivery:
Service items are not blocked for delivery; rather, they do not require delivery at all. No delivery blocking is necessary.

D. The service item has no schedule line assigned:
Service items can have schedule lines for planning and billing purposes. Lack of schedule lines is not a defining characteristic.

References

SAP Help Portal: Service Items in Sales Orders – SAP S/4HANA Cloud Sales
SAP Fiori Apps Library: Manage Sales Orders – Service Item Processing