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

Explanation:

C. Quantity and value updates when posting a goods movement:
Movement types determine whether a goods movement updates stock quantities (inventory management) and whether it updates stock values (financial accounting). For example, a goods receipt increases both quantity and value, while a transfer posting might only change the stock type without affecting valuation .

D. Field selection when recording a goods movement:
Movement types control which fields are required, optional, or hidden on the transaction screen. For instance, a movement type for a consumption posting might require a cost center, while a simple stock transfer might not .

E. Account determination for financial posting:
Movement types determine which G/L accounts are posted to when valuated stock changes occur. They work with valuation classes and modification keys to ensure debits and credits are posted to the correct accounts (inventory, consumption, GR/IR, etc.) .

Why the other options are incorrect:

A. Selection of the storage location at goods receipt:
The storage location is determined by the user during goods receipt entry or by the purchase order, not directly controlled by the movement type. Movement types may make the storage location field required or optional, but they do not "select" it .

B. Determination of the shipping point for deliveries:
Shipping points are determined by loading and shipping conditions, typically from the customer master or delivery document, not by inventory movement types. Shipping point determination is part of Sales and Distribution (SD), not inventory management movement types .

Reference:
This information is based on SAP standard functionality where movement types are defined in Customizing (transaction OMJJ or OMCB) and control various aspects of goods movements including quantity/value updates, screen field selection, and account determination .

Explanation:

A. Transfer posting between stock types in one plant:
This transaction can trigger account determination errors if configuration is missing. When moving stock between different valuation classes (e.g., from consignment to company-owned stock), the system attempts to post to G/L accounts. If the account determination (OBYC) for the relevant transaction key (like GBB or BSX) is not properly maintained, you will receive an error such as "Account determination for entry not possible" .

C. Stock transfer between company codes:
Intercompany stock transfers involve complex account determination, especially when parallel ledgers or transfer prices are involved. If the automatic account determination is set up incorrectly—for example, if the clearing accounts have "Open Item Management" turned on when they should not—the system will fail with errors like FINS_ACDOC_POST135 . These transactions require specific G/L accounts for company code clearing, and missing or incorrect configuration prevents the posting .

D. Material valuation price change (MR21):
When changing material prices using transaction MR21, the system must post revaluation amounts to G/L accounts. If account determination is incorrect, you may encounter various errors. For example, if the price change results in a posting to the stock account and the variance exceeds configured tolerance limits, the system issues error messages like "Price change more than & % in previous period" . Additionally, material status restrictions can block price changes entirely (error C+811) .

Why the other options are incorrect

B. Goods receipt into blocked stock:
Goods receipts into blocked stock (movement type 103) are generally non-valuated postings. Since blocked stock is not value-updated in the G/L, incorrect account determination typically does not trigger errors at this stage. The valuation occurs later when the stock is transferred from blocked to unrestricted (movement type 105) .

E. Purchasing condition price change:
Changing condition types in purchasing (e.g., via MEK1) involves condition technique and calculation schemas, not G/L account determination. Errors in this area relate to missing condition types or calculation schema configuration, such as message V1 227 "New pricing is no longer possible" or message 06657 "Not possible to determine a condition type for the price" .

References
Error M8 147 "Account determination for entry not possible" occurs when OBYC settings are missing
Intercompany stock transfers fail with error FINS_ACDOC_POST135 when clearing accounts have Open Item Management incorrectly enabled
MR21 price changes can trigger error M8 785 regarding excessive price variance or error C+811 regarding material status

Explanation:

Situation Handling in SAP S/4HANA uses predefined templates to proactively notify users about business issues that require attention.

B. A supplier confirmation is pending:
This template (specifically SIT_PURSUPPLIERCONFIRMATIONPENDING) monitors purchase order items for which a supplier confirmation is expected but hasn't been received by the deadline. It helps procurement and production planners avoid supply chain disruptions.

C. A contract is ready as a source of supply:
This template (specifically SIT_PURCONTRACTREADYFORUSAGE) notifies the responsible purchaser when a newly created or updated purchase contract is fully approved and ready to be used for source determination in purchase orders.

Why Other Options are Incorrect

A. The due date for a blocked invoice has passed:
While SAP has "Blocked Invoice" situations, they typically focus on the reason for the block (e.g., price or quantity variance) rather than simply a due date passing. Standard templates exist for "Invoice Request Postponed" but not specifically for a passed due date on a block in this context.

D. A purchase order approval is pending
While pending approvals are critical, they are traditionally handled by the SAP Fiori My Inbox and the Flexible Workflow notification framework rather than the Situation Handling "standard templates" for Sourcing and Procurement.

Reference
SAP S/4HANA Sourcing and Procurement: Situation Handling in Procurement (Templates for Purchasing).
SAP Help Portal: Situation Templates in Sourcing and Procurement (Scope Item 18_I).

Explanation:

In the SAP S/4HANA Refurbishment Process, split valuation is used to track materials based on their condition (e.g., New, Refurbished, Defective). When setting up the material master for split valuation, the system requires a specific configuration of price control across different levels:

Valuation Area Level (Header): At the main plant/valuation area level, the price control must be set to Moving Average Price (V). This acts as a "weighted average" header that aggregates the values of the various sub-stocks.

Valuation Type Level (Sub-stocks):For the individual valuation types (e.g., C1 for New, C2 for Refurbished), you can choose either Standard Price (S) or Moving Average Price (V) depending on your accounting requirements. However, the mandatory requirement for the header remains Moving Average.

If the header were set to Standard Price, the system would not be able to dynamically reflect the total value of the various conditions accurately as they are issued and received back into stock.

Why Other Options are Incorrect

A. For the valuation area, the price control must be standard price:
This is technically impossible in SAP S/4HANA for split-valued materials; the system will force a Moving Average price at the header level to allow for the calculation of the total stock value.

B. & C. For each possible valuation type...:
While you can choose these price controls for the sub-levels, they are not a mandatory "consideration" that restricts the process in the same way the header requirement does. The flexibility at the valuation type level is a feature, not a constraint.

Reference:
SAP S/4HANA Sourcing and Procurement: S4520 (Purchasing in SAP S/4HANA) – Valuation and Account Assignment.
SAP Help Portal: Split Valuation in Procurement and Refurbishment.

Explanation:

When entering a supplier invoice for a delivered purchase order, you can reference the specific logistical documents that triggered the posting. The system uses these references to accurately allocate the invoice to the correct goods movements and quantities.

A. Goods Receipt:
The goods receipt document is the primary operational reference for invoice verification. When you reference a purchase order, the system automatically proposes items based on the goods receipt history—selecting all items for which goods receipts have been posted but not yet fully settled . You can also explicitly reference a specific goods receipt document number to allocate the invoice to that particular delivery.

C. Delivery Note:
The delivery note can be entered as a reference during invoice posting. According to SAP documentation, for the reference document category "Delivery Note," the system selects "Goods/Services" items . Additionally, the delivery note that was entered during goods receipt posting can now be displayed in the Purchasing Document Reference section of the invoice , confirming it as a valid reference.

Why the other options are incorrect:

B. Inbound Delivery:
While inbound deliveries are used in advanced shipping notifications and warehouse processes, the standard SAP documentation does not list inbound delivery as a direct reference category for supplier invoice entry. The documented reference categories are Purchase Order, Delivery Note, Service Entry Sheet, and Bill of Lading .

D. Bill of Lading:
Although the bill of lading appears in SAP documentation as a reference document category, it is specifically used for selecting "Planned Delivery Costs" rather than goods/services items . It is not used to reference the delivered materials themselves, but rather to allocate freight or logistics costs associated with the delivery.

References:
SAP Help Portal documentation on Manage Supplier Invoices and SAP Learning content on Logistics Invoice Verification confirm these reference options.

Explanation:

SAP Smart Business KPI tiles in purchasing analytics are designed with specific features that enhance data analysis and decision-making.

A. Insight to Action provides drilldown capabilities and appropriate actions:
This is a core feature. When a user selects a KPI tile, it launches an evaluation that breaks down the individual KPI, providing drilldown capabilities and appropriate actions. This concept is explicitly referred to as "Insight to Action" .

D. Smart controls, such as smart filter and smart charts, are available:
The SAP Smart Business runtime environment is enhanced with smart controls, including smart filters and smart charts. Smart filters provide lists of all values for KPI dimensions, while smart charts allow users to display dimensions and measures, select chart types, and change dimensions dynamically .

Why the other options are incorrect:

B. When a tile is changed, the database is updated in real time:
While tile information is updated in real-time from the database , changing a tile itself (such as modifying chart settings or filters) does not update the underlying database. These runtime changes are temporary and cannot be saved .

C. Smart alert thresholds can be set to update the tile display at different intervals:
Although alert thresholds can be set to change tile colors (e.g., red when thresholds are exceeded) , these thresholds trigger color changes based on data conditions, not time-based display updates at different intervals. The information on tiles is updated in real-time, not at configurable intervals .

References:
SAP Learning materials on using analytical apps and SAP S/4HANA sourcing and procurement documentation

Explanation:

The Purchase Requisition Touch Rate card in the Procurement Overview app is specifically designed to show the proportion of purchase requisition items based on the level of manual intervention required during processing .

This card displays a donut chart divided into three categories :
No Touch Rate: Items processed automatically without any manual intervention
Low Touch Rate: Items that only require approval
High Touch Rate: The percentage of all purchase requisition items that require manual intervention during processing

The high touch rate directly answers the question, showing the percentage of items needing manual intervention. Selecting the card header or chart navigates to the Purchase Requisition Touch Rate KPI for more detailed analysis .

Why the other options are incorrect:

A. Purchase Requisition Item Types:
This card shows the distribution of different item types (catalog items, free-text items, etc.), not the level of manual intervention required .

C. Monitor Purchase Requisition Items:
This card displays open and unsourced purchase requisition items sorted by value and delivery date, helping identify sourcing issues rather than measuring touch rate .

D. Non-Managed Spend:
This card shows invoice spend not associated with a purchase order, focusing on spend analysis rather than requisition processing efficiency .

Reference:
SAP Learning materials for Procurement Overview app confirm that the Purchase Requisition Touch Rate card specifically tracks the high touch rate percentage for manual intervention during processing