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

Explanation:

In the context of SAP S/4HANA's flexible workflow for purchasing, item-wise release refers to the ability to approve or reject individual items within a document separately, rather than having to approve the entire document as a whole.

B. Purchase requisition
Item-wise release is a core capability for purchase requisitions. The flexible workflow framework allows individual requisition items to be routed to different approvers based on attributes like material group, plant, or account assignment, and each item can be released independently.

Analysis of Other Options:

A. Purchase order
While flexible workflow is available for purchase orders, it is typically at the header level (overall release). Item-wise release is not the standard workflow for purchase orders in this context.

C. Scheduling agreement
Scheduling agreements do not typically use an approval or release workflow process. They are created in a non-released (blocked) status and are managed differently.

D. Request for quotation (RFQ)
RFQs are not typically subject to an internal item-wise release workflow. They are external-facing documents sent to suppliers.

Reference:
SAP S/4HANA documentation on Flexible Workflow for Purchasing (under Materials Management > Purchasing) specifies that item-wise release is supported for purchase requisitions as part of the flexible workflow configuration.

Explanation:

When posting invoices for consumable materials in SAP S/4HANA, you may want to allow changes to the account assignment data (for example cost center, internal order, project) during invoice receipt.

This control is set in the account assignment category customizing.

Each account assignment category (such as K = Cost Center, F = Order, P = Project) has parameters that determine whether account assignment data can be changed at different stages (purchase order, goods receipt, invoice receipt).

By enabling the parameter for invoice receipt, you allow users to adjust account assignment data when posting the invoice.

Why the other options are incorrect

A. Item category
Controls procurement type (standard, subcontracting, consignment, etc.), not account assignment flexibility.

B. Purchase order document type
Defines number ranges, field selection, and permissible item categories, but not account assignment change rules.

C. Material master
Holds material-specific data (valuation, MRP, etc.), but does not control invoice account assignment changes.

Reference
SPRO Path
Materials Management -> Purchasing -> Account Assignment -> Define Account Assignment Categories
SAP Help Portal
Account Assignment in Purchasing

Explanation:

🟢 B. Organization
This category represents a legal, social, or economic entity such as a company, corporation, department, subsidiary, or government institution. It is used when dealing with businesses rather than individual people.

🟢 C. Group
This category represents a shared relationship or association between multiple entities, such as a married couple, a shared living community, or an informal buying group.

🟢 D. Person
This category represents a private individual. It is used for master records concerning physical humans, such as an internal employee, a retail buyer, or an individual contact person.

Incorrect Options Breakdown

🔴 A. Supplier
This is an incorrect choice because "Supplier" is a Business Partner Role (for example FLVN00 or FLVN01), not a structural category. You assign a BP role to a category after it has been created as an Organization, Group, or Person.

🔴 E. Customer
Similar to the supplier distinction, "Customer" is a Business Partner Role (for example FLCU00 or FLCU01). Roles determine which application-specific data views can be extended, whereas the Category defines the fundamental database structural archetype.

Reference:
Course Code: SAP Learning S4500 (Business Processes in SAP S/4HANA Sourcing and Procurement - Master Data Segment).
Core Technical Concept: The category is selected at the very beginning of the Business Partner transaction (or corresponding Fiori app) and cannot be changed after the master record is saved.

Explanation:

Account Determination for Planned Delivery Costs

In SAP MM Pricing Procedures (Calculation Schemas), planned delivery costs such as:

Freight
Insurance
Customs charges

can be posted to different G/L accounts.

The system determines the correct account through an account key assigned in the Calculation Schema (Pricing Procedure).

The account key links the condition type to automatic account determination in FI.

✅ C. Assign an account key in the calculation schema — CORRECT
In the pricing procedure, each condition type can have:
An account key
An accrual key

SAP uses this account key during automatic postings.

Example:
Freight condition type → Account key FR1
FR1 maps to freight clearing account in OBYC

Why the other options are incorrect

❌ A. Assign an account key in the access sequence
Access sequences determine how condition records are found.
They do not control account determination.

❌ B. Assign an account key in the condition type
Condition types define pricing behavior.
Account keys are assigned in the pricing procedure, not directly in the condition type.

❌ D. Assign an account key in the condition record
Condition records store values (prices, freight amounts, etc.).
They do not contain account determination logic.

Key Exam Tip

For MM pricing:

Condition Type = what kind of charge
Access Sequence = how SAP finds the condition record
Calculation Schema / Pricing Procedure = where account keys are assigned
OBYC = final G/L account determination

Final Answer:
👉 C. Assign an account key in the calculation schema

Explanation:

A. A supplier confirmation is pending
One of the most common standard templates in the Procurement domain is for Supplier Confirmations. The system monitors Purchase Order items where a confirmation is expected but has not been received from the vendor by a specific date. It then alerts the purchaser so they can follow up, preventing potential supply chain delays.

D. A contract is ready as a source of supply
There is a specific template for Contract Management. This situation occurs when the system identifies that a high percentage of a contract's value or quantity has been consumed, or when a contract is about to expire, alerting the buyer that a new source of supply needs to be established or the existing one renegotiated.

Why the other options are incorrect

B. A purchase order approval is pending
While this sounds like a logical candidate for an alert, SAP handles this via the Workflow engine and the "My Inbox" app rather than the Situation Handling framework. Workflows are used for active decision-making processes, whereas Situation Handling is used for "noticing" a state that requires attention.

C. The due date for a blocked invoice has passed
Invoices that are blocked (for price, quantity, etc.) are generally managed through the "Release Blocked Invoices" apps or specific workflow escalations. While there are templates for pending invoices in some versions, "due date passed for a blocked invoice" is not a standard situation template in the baseline C_TS452_2022 scope.

Key Takeaway for the Exam
Situation Handling is designed to bridge the gap between "standard data" and "human action."
Common Procurement Templates to Remember:
Quantity or Price deficits in confirmations
Contract expiration or consumption levels
Catalog item request failures
Missing Supplier Confirmations

Explanation:

🟢 C. The shelf life expiration date check is activated for the movement type in Customizing
For the system to prompt or enforce expiration date entries at goods receipt, the function must be explicitly turned on for the specific movement type (for example 101 for Goods Receipt for Purchase Order) in SAP Customizing. This configuration dictates whether the shelf life check is active, inactive, or only active if a minimum remaining shelf life is maintained in the material master.

🟢 D. The purchase order item contains the remaining shelf life
During the goods receipt process, the system evaluates the production or expiration date entered by the user. It compares this against the minimum remaining shelf life requirement specified in the purchase order item details (or pulled automatically from the Material Master record). If the material does not have enough remaining days to meet this requirement, the system rejects the goods receipt.

Incorrect Options Breakdown

🔴 A. The total shelf life is maintained in the purchasing info record
The purchasing info record stores vendor-specific pricing, lead times, and tolerances. It does not control or maintain total shelf life metrics. The total shelf life is instead maintained on the Plant Data / Storage 1 view of the Material Master.

🔴 B. The shelf life expiration date check is activated for the material type in Customizing
Shelf life verification parameters are configured at the plant and movement type levels in Customizing, not at the high-level material type configuration.

Reference

Course Code: SAP Learning S4510 / TS452 (Inventory Management and Physical Inventory in SAP S/4HANA - Using Date Checks in Goods Receipt Processing).
IMG Configuration Path:
SPRO -> Materials Management -> Inventory Management and Physical Inventory -> Goods Receipt -> Set Expiration Date Check.

Explanation:

This question addresses the core behavior of Logistics Invoice Verification (LIV) when an invoice is entered with reference to a purchase order in SAP S/4HANA:

C (Correct)
When entering a purchase-order-based invoice, the system calculates the proposed invoice quantity by considering how much has been delivered but not yet invoiced. Specifically, it proposes the quantity as the difference between the total delivered quantity and the total quantity already invoiced. This ensures accurate tracking and prevents duplicate invoicing for the same goods.

D (Correct)
In purchase-order-based invoice verification, each goods receipt (partial delivery) against a purchase order item is treated as a separate line item in the invoice document. This allows for detailed matching of invoice items to specific receipts and facilitates any necessary price or quantity adjustments at the receipt level.

Analysis of Other Options:

A (Incorrect)
The system does not propose the "total delivered quantity" unless nothing has been invoiced yet. It proposes the open (un-invoiced) delivered quantity.

B (Incorrect)
Partial deliveries are flagged or shown as individual invoice items, providing detailed clearing control between specific goods receipt documents and the invoice. The statement that they are "NOT flagged" is false.

Reference:
SAP Help Portal documentation on Logistics Invoice Verification, specifically the section "Entering Invoices with Reference to Purchase Orders," which explains the proposed quantity logic and handling of partial deliveries through the PO history.