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

Explanation:

Document parking in SAP allows you to temporarily save incomplete or problematic documents so they can be reviewed, corrected, or completed later before final posting. It is particularly useful in Logistics Invoice Verification scenarios:

Missing account assignment in invoice item
If an invoice item lacks account assignment data (for example cost center or internal order), the system cannot post it directly. Parking lets you save the document until the missing data is provided.

EDI invoice with variances
When an electronic invoice (EDI) arrives with discrepancies (such as price or quantity differences), the system can park the invoice instead of rejecting it outright. This allows manual review and resolution before posting.

Why the other options are incorrect

A. Goods receipt with quality inspection
This is handled via inspection lots in Quality Management, not document parking.

B. Missing account assignment in purchase order item
Purchase orders must be complete before release; parking is not applicable here.

Reference
SAP Help Portal – Logistics Invoice Verification: Document Parking
SPRO Path Materials Management -> Logistics Invoice Verification -> Document Parking Settings

Explanation:

🟢 C. You can maintain plant-specific conditions in centrally agreed contracts
Even though a centrally agreed contract is created at a high organizational level (negotiated by a central purchasing organization for multiple locations), SAP allows you to maintain separate pricing, discounts, and terms for individual receiving plants. This lets you account for varying localized costs, such as freight, duties, or local transit routes.

🟢 D. You can use centrally agreed contracts in a procurement hub scenario
In SAP S/4HANA Central Procurement (hub architecture), a central purchase contract can be created, managed, and approved within a single hub system. The system then automatically distributes these standardized contractual terms and operational conditions down to all connected satellite ERP systems.

Incorrect Options Breakdown

🔴 A. You CANNOT specify plants in centrally agreed contracts
While items in a centrally agreed contract do not require a specific plant at the global item header level, you can specify plants within the item breakdown details to manage plant-specific pricing scales or to target specific fulfillment sites.

🔴 B. You can use centrally agreed contracts without restrictions for any purchasing organization
This statement is too broad and technically false. To allow local or separate purchasing organizations to issue release orders against a central contract, you must explicitly assign the global negotiating unit as a Reference Purchasing Organization in SAP enterprise structure customizing.

Reference
Course Code: SAP Learning: Working with Centrally Agreed Contracts.
Application Capability: Explaining Purchase Order Handling - Global Sourcing.

Explanation:

Invoice Blocking Reason “Quality”

In SAP Invoice Verification, an invoice can be blocked for payment with the blocking reason:

👉 Quality

This happens when the quality inspection process is not yet completed for the related goods receipt.

The key factor is usually:

An inspection lot exists
No usage decision (UD) has been made yet

✅ C. Goods-receipt-based invoice verification is used and NO usage decision has been made for the inspection lot for the item in the invoice — CORRECT
With GR-based IV enabled:
Invoice is linked to the goods receipt
If the inspection lot still lacks a usage decision, SAP blocks the invoice for quality reasons.

✅ D. Goods-receipt-based invoice verification is NOT used and NO usage decision has been made for any inspection lot for the item in the invoice — CORRECT
Even without GR-based IV, SAP can still block invoices if:
Quality inspection is incomplete
No usage decision exists

Why the other options are incorrect

❌ A. Goods-receipt-based invoice verification is used and NO goods receipt has been posted
If no goods receipt exists under GR-based IV:
The issue is typically quantity or reference-related
Not specifically a Quality block reason.

❌ B. Post to Inspection Stock flag set in material master
Posting to inspection stock alone does not automatically trigger a quality block.
The critical trigger is missing usage decision for the inspection lot.

Key Exam Tip

Invoice block reason “Quality” is mainly connected to:

QM integration
Inspection lots
Missing usage decisions (UD)

Final Answer:
👉 C. Goods-receipt-based invoice verification is used and NO usage decision has been made for the inspection lot for the item in the invoice
👉 D. Goods-receipt-based invoice verification is NOT used and NO usage decision has been made for any inspection lot for the item in the invoice

Explanation:

In SAP S/4HANA Output Management, activation is controlled at the level of the application object:

The application object represents the business document category (for example purchase order, scheduling agreement, RFQ).

By activating output management here, you enable the new BRF+-based output framework for all documents of that category.

This replaces the classic NAST output determination used in SAP ECC.

Why the other options are incorrect

A. Purchasing organization
Output management is not activated per purchasing organization.

B. Document category
While categories exist, activation is not performed here but at the application object level.

D. Document type
Document types define control parameters but do not activate output management.

Reference
SAP Help Portal – Output Management in S/4HANA
SPRO Path
Cross-Application Components -> Output Control -> Activate Output Management for Application Objects

Explanation:

C. Carry out a net requirement calculation for every material included in the planning run
This is always the first step in the planning run. In reorder point planning, the "Net Requirement Calculation" is simple: the system compares the Plant Stock + Fixed Receipts (like confirmed Purchase Orders) against the Reorder Point defined in the Material Master. If the available stock falls below the reorder point, a requirement exists.

A. Carry out a lot-size calculation for every material with net requirements
Once the system determines that a requirement exists (Step C), it must decide how much to order. This is the second step. The system looks at the Lot Size Key (for example HB - Replenish to Maximum Stock, or FX - Fixed Lot Size) to calculate the specific quantity for the procurement proposal (Purchase Requisition).

Why the other options are incorrect

B. Flag materials that have been subject to an activity relevant to MRP
This describes the Planning File Entry process. While this happens before the planning run to tell the system which materials need to be checked, it is not a task performed during the execution of the reorder point calculation itself for a specific material.

D. Perform backward scheduling to determine the availability dates
This is a trap related to Forward Scheduling. In Reorder Point planning, the system usually uses Forward Scheduling. It starts from "Today" (the date the reorder point was breached) and adds Purchasing Processing Time, Planned Delivery Time, and GR Processing Time to determine when the goods will be available. Backward scheduling is more typical of MRP based on independent requirements (like a specific Sales Order date).

The MRP Logic Flow for the Exam:
Check Planning File: Is the material marked for a run?
Net Requirement Calculation: Is Stock < Reorder Point? (Answer C)
Lot Size Calculation: How much do we need? (Answer A)
Scheduling: When will it arrive? (Usually Forward for Reorder Point)
Procurement Proposal: Create the Purchase Requisition.

Explanation:

In message determination (output control) within SAP S/4HANA, an access sequence is a search strategy. Its purpose is to locate valid output condition records. The system searches through the defined access sequence (a series of accesses or "keys") to find an existing condition record that matches the specified criteria (for example vendor, document type, purchasing organization). Once a valid condition record is found, it provides the output parameters (such as printer, email, form template) for the corresponding message type.

Here is a breakdown of the options:

A (Incorrect)
The message schema is assigned to a document category (for example Purchase Order), but the access sequence searches within the schema to find condition records, not the schema itself.

B (Incorrect)
The message type (for example "Purchase Order Print") is an element within the message schema. The access sequence is assigned to the message type and searches for its condition records, but the sequence does not "determine" the message type.

C (Incorrect)
The output device (for example a specific printer) is a value stored inside an output condition record. The access sequence finds the record, which then supplies the output device.

D (Correct)
The access sequence is the tool that locates the specific output condition record. Its whole purpose is to search through the criteria (for example first try vendor/master data, then company code, then general) until a matching record is found.

Reference:
SAP S/4HANA documentation on Output Management (or classic Message Determination in MM) states: "The access sequence is a search strategy that the system uses to find valid condition records for a condition type (message type)."

Explanation:

If you want to plan materials differently within a plant, you use MRP areas.
An MRP area allows you to subdivide a plant into smaller planning segments.
Each MRP area can have its own planning parameters (lot-sizing, safety stock, reorder point, etc.).
This is especially useful when you want to plan materials separately for production supply areas, storage locations, or subcontractors.
By assigning materials to different MRP areas, you can tailor planning strategies without duplicating material masters across plants.

Why the other options are incorrect

A. Vendor consignment info records
Used for consignment stock management, not for planning differentiation.

C. Production supply areas
Relevant for Kanban and shop floor logistics, but not for MRP planning segmentation.

D. Storage bins
Part of warehouse management; they define physical storage, not planning logic.

Reference
SAP Help Portal – MRP Areas in S/4HANA
SPRO Path
Production -> Material Requirements Planning -> Master Data -> Define MRP Areas