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

Explanation:

A. Export to a spreadsheet:
This is a standard feature in SAP Fiori analytical apps. The toolbar on the smart chart includes a function that allows you to directly export the data displayed in the chart or table view to a spreadsheet format (like Microsoft Excel) for further offline analysis or reporting .

C. Change the dimensions that are shown:
When analyzing a KPI, the "Settings" option within the smart chart toolbar allows you to interact with the data. You can select a different dimension for the chart, which means the chart will be re-rendered instantly based on your new selection (for example, changing the chart from showing "Spend by Supplier" to "Spend by Material Group") .

Why the other options are incorrect:

B. Import from a spreadsheet:
This option is incorrect. The flow of data in these analytical apps is unidirectional; you can export data out of SAP S/4HANA, but you cannot import data from an external spreadsheet to change the live KPI report data.

D. Select the CDS view to be used:
This option is incorrect. The underlying Core Data Services (CDS) view is a technical definition of the data source for the KPI and is configured at design time by a developer or administrator. Business users working with the KPI report at runtime do not have the option to select or change the underlying CDS view .

Reference:
These functions are part of the "Smart Chart" capabilities in SAP S/4HANA's purchasing analytics, designed to provide interactive data exploration through drilldowns, chart type selection, and the specific functions mentioned

Explanation:

The parameter that allows changing account assignment data for a consumable material during invoice receipt is configured in the account assignment category in SAP Materials Management (MM) Customizing.

Analysis of Other Options

A. In the material master of the consumable material:
Incorrect. The material master contains data such as base unit of measure, material group, and valuation class, but it does not contain a parameter to control the changeability of account assignments during invoice receipt .

C. In the item category:
Incorrect. While the item category in the purchase order does influence various procurement functions, the specific control for allowing account assignment changes at invoice receipt is a direct attribute of the account assignment category, not the item category .

D. In the purchase order document type:
Incorrect. The purchase order document type controls parameters such as number ranges and release strategies for the procurement document, but it does not govern whether account assignment data can be modified during invoice verification .

Reference:

The Customizing settings for this function are maintained via the IMG path: Materials Management → Purchasing → Account Assignment → Maintain Account Assignment Categories (transaction OME9), where the "Acct Assgt changeable at IR" indicator is set

Explanation

Contract leakage is the specific SAP S/4HANA Procurement KPI used to identify Maverick Buying or "off-contract" purchasing where a valid contract was available but not utilized. In the SAP Fiori analytical framework, this KPI calculates the total value of purchase order items that were created without a contract reference, even though a matching, valid contract existed for that specific material or material group and supplier at the time of the order.

By monitoring this metric, procurement managers can identify where automated source determination is failing or where buyers are manually bypassing established agreements, leading to a loss of negotiated savings.

Why Other Options are Incorrect

B. Off-contract spend:
While this sounds like a logical term, in the context of standard SAP S/4HANA Analytics and KPI libraries, "Contract Leakage" is the official technical designation for this specific measurement.

C. Unused contracts:
This refers to the value of contracts that have had no release orders (purchase orders) issued against them at all, rather than identifying POs that missed an available reference.

D. Purchase order value:
This is a broad metric that simply reflects the total monetary value of orders without filtering for contract compliance or references.

Reference
SAP S/4HANA Sourcing and Procurement: Analytical Apps for Purchasing (Contract Leakage).SAP Learning: S4500 (Business Processes in SAP S/4HANA Building Blocks) or S4520 (Purchasing in SAP S/4HANA).

Explanation:

B. Create consignment info records:
This is a mandatory prerequisite for the entire consignment process. Before you can order consignment material, post a goods receipt, or settle withdrawals, you must create a purchasing info record with the info category "Consignment" for the specific combination of supplier and material . This info record is critical because it contains the price that will be used later to value and settle the withdrawals from consignment stock .

C. Settle liabilities resulting from consignment stock withdrawals:
This is the core financial step that completes the consignment process. When you withdraw material from consignment stock (either for consumption or by transferring it to your own stock), a liability to the supplier is created . You must regularly clear these liabilities through the consignment settlement process (often using transaction MRKO), which generates a settlement document and payment to the supplier without requiring a traditional invoice from them .

Analysis of Other Options

A. Create consignment storage locations:
Incorrect. It is not necessary to create specific storage locations for consignment stock. Consignment stock and your own stock can be managed in the same storage location . The system tracks consignment stock separately using a special stock indicator (K), not by requiring dedicated storage locations.

D. Settle liabilities resulting from consignment stock receipts:
Incorrect. No liability is created when you receive consignment stock from the supplier . The goods remain the property of the supplier until they are withdrawn. Therefore, goods receipts for consignment stock are non-valuated postings and do not generate any financial liability or require settlement .

Reference:
The supplier consignment process is defined by specific steps in SAP S/4HANA: creating a consignment info record (required), creating a purchase order with item category K, posting a non-valuated goods receipt, posting withdrawals (which create liabilities), and finally settling those liabilities

Explanation:

The GR/IR (Goods Receipt/Invoice Receipt) clearing account is a suspense account used to reconcile the timing difference between goods receipt and invoice receipt. An open item on this account arises when the quantities posted from these two transactions do not match for a purchase order item.

A. The delivered quantity is more than the invoiced quantity:
This is correct. When goods are received, the stock account is debited, and the GR/IR account is credited. If the invoice for these goods has not yet been posted, the GR/IR account retains a credit balance, representing an open liability to the vendor.

C. The invoiced quantity is more than the delivered quantity:
This is correct. When an invoice is received, the GR/IR account is debited, and the vendor account is credited. If the corresponding goods have not yet been received, the GR/IR account retains a debit balance, representing goods that have been paid for but are not yet in inventory.

Why the other options are incorrect:

B. The ordered quantity is more than the delivered quantity:
A purchase order is a request and does not create a financial posting. The GR/IR account is only affected by actual postings (goods movements and invoice receipts). Therefore, an order/delivery comparison does not impact the GR/IR balance.

D. The ordered quantity is more than the invoiced quantity:
Similar to option B, this compares a non-posting document (the order) with a posting document (the invoice). The GR/IR account balance is driven strictly by the comparison of the two posting documents: goods receipt quantity and invoice receipt quantity.

Reference:
This process is governed by the standard SAP logic where the GR/IR clearing account is cleared only when the cumulative goods receipt quantity equals the cumulative invoice receipt quantity for a purchase order item.

Explanation:

To enable cross-purchasing organization procurement and leverage centrally agreed conditions, you must set up a reference purchasing organization. This configuration allows multiple purchasing organizations to operate independently while sharing centrally negotiated purchasing conditions (such as prices and terms) from a central entity.

When a reference purchasing organization is defined, the system enables the following:
Purchasing organizations can create their own purchase orders.
These purchase orders can reference conditions (like info records or contracts) that were created by the reference purchasing organization .

This ensures that local procurement activities benefit from global or regional agreements without needing to renegotiate terms.

Why the other options are incorrect:

A. A purchasing group:
A purchasing group is an individual or group responsible for procurement activities (a buyer). It is an organizational unit within a purchasing organization and does not facilitate the sharing of conditions across different purchasing organizations .

C. A standard purchasing organization:
A standard purchasing organization is responsible for procuring materials and services for specific plants. While it can create its own conditions, it cannot automatically share them with other purchasing organizations without additional configuration like a reference organization .

D. A purchasing team:
A purchasing team is a group of buyers or purchasing groups that work together, often in SAP Ariba or other collaborative scenarios. It is not an organizational unit in SAP S/4HANA used to share conditions across purchasing organizations .

Reference:
SAP S/4HANA organizational structures allow for a reference purchasing organization to centrally maintain conditions that can be used by other assigned purchasing organizations. This is defined in Customizing under Enterprise Structure → Definition → Materials Management → Maintain Purchasing Organization.

Explanation:

The Info Update indicator in a purchase order is specifically designed to automatically update an existing purchasing info record . When you select this indicator while creating a purchase order, the system updates the info record by setting the purchase order document number as the "last document" and refreshing the order price history . This ensures that future procurement documents reference the most current purchasing activity.

Why the other options are incorrect:

A. Select the Info Update indicator when maintaining a contract:
For contracts, if an info record already exists for the vendor-material combination, selecting the Info Update indicator results in no updates to the conditions in the existing info record . The system only creates a new info record with conditions if none existed previously.

B. Select the Info Update indicator when creating a contract release order:
A contract release order behaves like a standard purchase order—it updates only the "last document" reference and order price history, but does not update conditions in the info record .

C. Select the Info Update indicator when maintaining a quotation:
While quotations do transfer time-dependent conditions to the info record , the question specifically asks about updating conditions in an already created info record. For purchase orders, the indicator serves this exact purpose.

Reference:
SAP Help documentation confirms that the InfoUpdate field in purchase orders determines whether the info record is updated, with the system setting the purchase order as the last document and updating the order price history