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

Explanation:

In SAP S/4HANA, to differentiate a subset of purchase orders, such as consignment orders, you must create a new document type. The document type is the central object that controls various attributes for a purchasing document, including the allowed item categories and the number range assignment.

Document Type vs. Document Category
The key controller for settings like number ranges in purchasing documents (such as Purchase Orders) is the Document Type, not the Document Category. A Document Category (for example, 'F' for Purchase Order) is a more fundamental technical classification that defines the database table and general business purpose. You cannot create a new one or assign number ranges to it directly to meet this requirement. Therefore, answers B and C, which reference a "document category," are incorrect.

Item Category Restriction
A specific document type allows you to restrict which item categories are valid. This is critical because it ensures the new number range is used only for consignment purchasing by assigning the consignment item category exclusively to this new document type.

SAP Configuration Reference
This configuration is performed in the SAP Implementation Guide (IMG) under Materials Management > Purchasing > Purchase Order > Define Document Types. In this activity, you can create new document types (for example, ZCON) and assign the desired internal and external number range intervals. You then further configure the allowed item categories for this document type, linking it specifically to the consignment item category.

Explanation:

A subcontracting procurement process involves sending components to a vendor who provides a service and returns an assembled or processed product. Some features of this process are:
You can maintain the components to be provided in a bill of material (BOM), which specifies the quantity and type of components required for each finished product.

You can have subcontracting purchase requisitions created by MRP (material requirements planning), which calculates the demand for finished products and components based on various planning parameters.

You can customize the control parameters for the subcontracting item category (L), which determines whether a goods receipt or an invoice receipt is required, whether account assignment is possible, and whether a material number is mandatory.

References:

SAP S/4HANA Sourcing and Procurement | SAP Learning, Course S4520, Unit 4, Lesson 1.

Explanation:

🟢 B. Purchase requisition-to-order cycle time
This KPI measures the average elapsed time between the moment a purchase requisition is created and the time the final purchase order is generated. It helps procurement managers identify bottlenecks in the conversion process.

🟢 C. Overdue purchase requisitions
This KPI tracks the number or value of purchase requisitions that have passed their requested delivery date or processing window but have not yet been converted into subsequent purchasing documents.

🟢 D. Purchase requisition average approval time
This KPI tracks how long it takes for a purchase requisition to clear its release strategy or flexible workflow steps. It is essential for measuring internal administrative efficiency.

Incorrect Options Breakdown

🔴 A. Purchase requisition touch tale
This is an intentional typographical error designed to trick candidates. The actual, standard SAP Fiori KPI is named Purchase Requisition Touch Rate. The touch rate app calculates the percentage of requisition items requiring manual processing.

🔴 E. Purchase requisition average order value
This metric is not a standard KPI for purchase requisitions. Requisitions represent internal demand rather than finalized spend. Average order value analytics are typically measured at the Purchase Order or Contract level.

SAP Documentation Reference

Course Code: SAP Learning S4520 (Sourcing and Procurement in SAP S/4HANA - Analytics and Fiori Reporting Overview).

Application Framework: SAP Smart Business for Sourcing and Procurement operational analytics.

Explanation:

In SAP S/4HANA Purchasing, visibility of pricing conditions in purchase orders can be controlled using user parameters.

The EFB parameter
The EFB parameter determines whether pricing conditions are displayed in purchase order transactions for a given user.

By configuring and assigning this parameter to specific users, you can restrict access so that only authorized users see the pricing conditions.

This is a common requirement when sensitive pricing information should not be visible to all procurement staff.

Why the other options are incorrect

A. Field selection key for the activity category
Field selection keys control field visibility at the transaction level, but they do not specifically restrict pricing conditions visibility by user.

B. Field selection key for the transaction
Similar to option A, this affects field behavior globally for the transaction, not user-specific visibility.

D. User parameter EVO
EVO controls default values for purchase order document types, not pricing condition visibility.

Reference

SAP Help Portal – User Parameters in Purchasing
Explains how parameters like EFB and EVO influence purchase order behavior.

SPRO Path
Materials Management > Purchasing > Environment Data > Define Parameter IDs: Customizing path to configure user parameters.

Explanation:

🟢 B. The value string for account determination
When defining a movement type, you specify or reference the value string. The value string is responsible for the financial value update during a goods movement, controlling which transaction/event keys are relevant for automatic G/L account assignment.

🟢 D. The allowed transactions
You must configure which T-codes or Fiori apps (such as MIGO_GR, MIGO_GI, etc.) are permitted to use this specific movement type. If a transaction code is not mapped to the new movement type, the system blocks the execution.

🟢 E. The field control
This controls the screen layout during goods movement postings. It dictates which fields in the material document are mandatory, optional, or hidden (for example, whether a Cost Center, Reason for Movement, or Text field must be filled).

Incorrect Options Breakdown

🔴 A. The quantity string for quantity updates
This is an internal, hardcoded system indicator. Quantity strings are fixed values in the SAP standard code. Neither the control logic itself nor the direct assignment of a quantity string can be customized or changed by the user when defining a movement type.

🔴 C. The dynamic availability check
While you can activate or deactivate an availability check indicator at the movement type level, the actual Dynamic Availability Check rule itself is configured under Production, MRP, or Sales and Distribution (SD) and then simply referenced, rather than defined here.

SAP Documentation Reference

Course Code: SAP Learning S4510 / TS452 (Inventory Management and Physical Inventory in SAP S/4HANA - Setting Up Movement Types).
IMG Path: SPRO -> Materials Management -> Inventory Management and Physical Inventory -> Movement Types -> Copy, Change Movement Types.

Explanation:

Initial Stock Entry with Quantity and Value

To manually post an initial stock entry in SAP S/4HANA where you enter both quantity and amount (value), you need a transaction that supports inventory posting with movement type 561 (initial stock entry) or similar stock-increasing movements.

✅ B. Post Goods Movement app — CORRECT
This Fiori app is the standard tool for inventory postings.

It allows you to:
Enter material
Enter quantity
Enter valuation (amount)
Use movement types like 561 (initial stock posting)

✔ Fully supports manual stock initialization with value.

❌ A. Post Goods Receipt without Reference — INCORRECT
This app is designed for goods receipt against purchase orders or other references.

It is not intended for initial stock entry.

Typically tied to procurement processes, not stock initialization.

❌ C. Manage Stock — INCORRECT
This app is mainly for:
Viewing stock levels
Performing stock overview tasks

It does not support posting stock movements with value.

✅ D. MIGO (SAP GUI) — CORRECT
Standard SAP GUI transaction for goods movements.

Supports:
Movement type 561 (initial entry of stock)
Entry of quantity + valuation data

One of the most commonly used methods in exams for stock postings.

Final Answer:

👉 B and D

Key Exam Tip:
For initial stock entry (561 movement type):
SAP GUI → MIGO
Fiori → Post Goods Movement app
Both support quantity + value entry.

Explanation:

A. You can assign different account assignment objects per item.

In SAP S/4HANA, the reservation is a planning tool. While you define a default account assignment (such as a Cost Center) at the header level, the system allows for item-level overrides.

Example:
Item 1 could be reserved for Cost Center A, while Item 2 in the same reservation is reserved for Cost Center B.

Why this matters:
It reduces the number of documents you need to create if you are pulling various parts for multiple related internal projects.

C. You can set the Movement Allowed indicator per item.

This is a critical control mechanism. Creating a reservation "blocks" or "plans" the stock, but it does not necessarily mean the warehouse is authorized to hand it over yet.

The Function:
The "Movement Allowed" (XWAOK) checkbox must be active for a Goods Issue to be posted against that reservation in transaction MIGO.

Flexibility:
You can have a reservation with 10 items where only 5 are marked "Movement Allowed." This allows for staged releases of materials.

Why the others are "Exam Traps"

B. You can maintain different movement types per item

The Reality:
The Movement Type (for example, 201 for Cost Center or 221 for Project) is a header-level field. Every item in that specific reservation document must use the same movement type. If you need a different movement type, you must create a new reservation.

D. You must enter a material number in the item

The Reality:
This sounds like a strict requirement, but SAP actually allows for "Planned" reservations or the use of External Requirements where a specific material master might not be strictly enforced depending on the configuration, although in most procurement cases you will use one. In the context of selecting the two correct answers, A and C are definitively the architectural rules of the MB21 transaction.

Pro-Tip for C_TS452_2022

Keep an eye on the "Check Storage Location" and "Fixed Supply" logic during your revision. The exam often asks about how reservations interact with MRP (Material Requirements Planning). Remember that manual reservations are MRP-relevant by default unless configured otherwise.