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

Explanation:

The Material Status field in the material master is specifically designed to control how a material can be used across different business processes, including procurement. By setting an appropriate material status (for example, Blocked for Procurement or Discontinued), the system prevents the creation of purchasing documents such as purchase requisitions, purchase orders, or scheduling agreements for that material.

In SAP S/4HANA Sourcing and Procurement, this is the standard and recommended method to stop further procurement of materials that are no longer to be purchased, while still allowing historical reporting or inventory usage if required. The control is enforced automatically during document creation, making it highly reliable for discontinued materials.

❌ Why the Other Options Are Incorrect

B. Authorization Group
This field controls user access and security to the material master records. It does not restrict procurement activities in purchasing documents.

C. Control Code
Control codes are used mainly for internal processing or classification purposes and do not block procurement transactions.

D. Special Procurement Type
This defines how a material is procured (e.g., subcontracting, stock transfer, consignment) but does not prevent procurement entirely.

📚 References

SAP Help Portal – Material Master → Material Status
SAP S/4HANA Sourcing and Procurement (TS452) – Master Data for Procurement

Explanation:

SAP Fiori apps are primarily categorized into three main types (sometimes expanded to five in broader documentation). The core and universally recognized types from SAP are:

Transactional Apps:
These are used to perform business tasks or transactions, such as creating a purchase order, approving a requisition, or managing a supplier. They are the digital replacement for classic SAP GUI transactions.

Analytical Apps:
These apps provide real-time insights, KPIs, and multi-dimensional data analysis. They often feature interactive charts, graphs, and drill-down capabilities to monitor key metrics in areas like spend analysis, procurement performance, or supplier evaluation.

Fact Sheet Apps:
These provide a consolidated, contextual overview of a central business object (like a supplier, material, or purchase order). They display key information gathered from various sources and often include navigation links to related transactions and analytics.

Why the other options are incorrect or not standard primary types:

A. KPI report:
This is typically a component or a view found within an Analytical App, not a standalone top-level app type. Analytical apps are built to visualize KPIs.

E. Interactive:
This is a descriptive term rather than an official SAP Fiori app type. All Fiori apps are designed to be interactive.

Reference:
This classification is defined in SAP's Fiori design guidelines and official training materials (e.g., SAP Learning Hub courses for UX500 or specific S/4HANA procurement). The three-type model (Transactional, Analytical, Fact Sheet) is foundational for understanding the Fiori app portfolio in SAP S/4HANA, including the Sourcing and Procurement suite (C_TS452_2022).

Explanation

In SAP S/4HANA, when Production Planning (PP) and Product Costing (CO-PC) are implemented, stock valuation must be carried out at plant level.

The plant is the organizational unit where material stocks are physically managed, production takes place, and manufacturing costs are collected. For accurate product costing, SAP needs stock values and quantities to be managed at the same level where production orders, BOMs, routings, and work centers are executed.

Valuation at plant level ensures:
Correct inventory valuation per production location
Accurate material cost estimates
Proper cost collection and variance calculation during production
Therefore, plant-level valuation is mandatory and standard practice when using PP and Product Costing.

❌ Why the Other Options Are Incorrect

A. Controlling area
The controlling area is used for management accounting and cost controlling, not for inventory valuation.

B. Business area
Business areas are mainly used for reporting purposes and have no role in stock valuation.

D. Company code
Company code valuation is possible in basic scenarios, but it is not sufficient when production planning and product costing are required, as costing and stock tracking must be more granular at plant level.

References
SAP Help Portal – Organizational Structures in SAP S/4HANA
SAP S/4HANA Production Planning – Stock Valuation and Product Costing

Explanation:

In SAP S/4HANA Sourcing and Procurement, the purchasing organization is a key organizational unit responsible for procurement activities and negotiations with vendors. In Customizing (Enterprise Structure), SAP allows flexible assignment of purchasing organizations to company codes to support both centralized and decentralized purchasing models.

The following assignments are supported:

One purchasing organization to one company code
This is the standard and simplest setup, where a purchasing organization procures materials exclusively for a single company code.

One purchasing organization to several company codes
This enables centralized purchasing, allowing one purchasing organization to negotiate and procure for multiple company codes.

Several purchasing organizations to one company code
This supports decentralized purchasing, where multiple purchasing organizations operate independently within the same company code.
These options are all explicitly supported in SAP Customizing for the enterprise structure.

❌ Why the Other Options Are Incorrect

D. One purchasing organization to several plants across company codes
Purchasing organizations are assigned to company codes, not directly to plants across different company codes. Plant assignments are handled after the purchasing organization–company code relationship is defined.

E. Several purchasing organizations to one purchasing group
A purchasing group is not an organizational level in the enterprise structure. It is used for internal responsibility and reporting, and no structural assignments are defined for it in Customizing.

📚 References
SAP Help Portal – Enterprise Structure → Assignment of Purchasing Organization
SAP S/4HANA Sourcing and Procurement (TS452) – Organizational Units in Purchasing

Explanation:

When you set up a cross-company-code purchasing organization in SAP S/4HANA, certain organizational assignments are mandatory, while others are optional or not required.

A purchasing group is not part of the enterprise structure. It is used only for internal responsibility and reporting within purchasing documents. Therefore, no organizational assignment between plant and purchasing group is required in Customizing—regardless of whether the purchasing organization is company-code-specific or cross-company-code.

Because of this, Plant – Purchasing Group must NOT be maintained when configuring a cross-company-code purchasing organization.

❌ Why the Other Options Are Incorrect

A. Plant – Purchasing Organization
This assignment must be maintained so that the plant knows which purchasing organization is responsible for procurement.

B. Reference Purchasing Organization – Purchasing Organization
This assignment is commonly maintained when you want to reuse purchasing documents or conditions from another purchasing organization, especially in cross-company-code scenarios.

D. Company Code – Purchasing Organization
This is a mandatory assignment. A cross-company-code purchasing organization must be assigned to all relevant company codes it procures for.

References
SAP Help Portal – Enterprise Structure → Purchasing Organization Assignments
SAP S/4HANA Sourcing and Procurement (TS452) – Cross-Company-Code Purchasing
SAP Learning Hub – Organizational Structure in Purchasing

Explanation:

In purchase-order–based invoice verification (PO-based IV), the invoice is checked against the purchase order, not against individual goods receipt documents.

B is correct
The system automatically proposes the open invoice quantity, calculated as: Total delivered quantity − Quantity already invoiced. This ensures that vendors are invoiced only for quantities not yet invoiced, preventing duplicate invoicing and supporting accurate three-way matching (PO, GR, Invoice).

D is correct
In PO-based invoice verification, partial deliveries are not shown as separate invoice items. The invoice item is aggregated at the purchase order item level, regardless of how many partial goods receipts exist.

❌ Why the Other Options Are Incorrect

A. The system proposes the total delivered quantity as the quantity to be invoiced.
❌ Incorrect because the system considers previously invoiced quantities. It does not blindly propose the full delivered quantity.

C. Partial deliveries for a purchase order item show up as individual items in the invoice document.
❌ This behavior applies to goods-receipt–based invoice verification, not PO-based invoice verification.

📚 References
SAP Help Portal – Invoice Verification → Purchase Order–Based Invoice Verification
SAP S/4HANA Sourcing and Procurement (TS452) – Logistics Invoice Verification

Explanation:

In Logistics Invoice Verification in SAP S/4HANA, when you enter a supplier invoice for a purchase order that has already been delivered, the system allows you to reference logistics documents that confirm receipt of the goods, in addition to the purchase order itself.

B.Goods Receipt (GR)
A posted goods receipt document is a valid reference for invoice entry. It ensures that the invoice is checked against the received quantities and values, supporting accurate three-way matching between PO, GR, and Invoice.

D.Inbound Delivery
An inbound delivery document can also be used as a reference when entering the supplier invoice, especially in processes involving advanced shipping notifications (ASN). It represents the logistics receipt information tied to the purchase order.

❌ Why the Other Options Are Incorrect

A. Delivery note
A delivery note is a supplier document and is not an SAP system document. It cannot be used as a formal reference in invoice verification.

C. Bill of lading
This is a transportation document used mainly in shipping and logistics. It is not integrated into SAP invoice verification as a reference document.

📚 References
SAP Help Portal – Logistics Invoice Verification → Invoice Entry
SAP S/4HANA Sourcing and Procurement (TS452) – Invoice Verification with Reference Documents