The supplier consignment process in SAP requires specific master data and subsequent process steps. A mandatory prerequisite is the creation of a consignment purchasing info record. This master data record contains the price and conditions agreed upon with the supplier, which the system uses to valuate the material upon withdrawal. The core principle of consignment is that liability is incurred only when the material is consumed or withdrawn from stock, not when it is received. Consequently, a periodic settlement process must be executed to clear these liabilities with the supplier for the materials that have been used.

A. Create consignment storage locations: While creating a dedicated storage location for consignment stock is a common and recommended practice for organizational clarity, it is not a mandatory system prerequisite. Consignment stock is identified by a special stock indicator ('K'), not the storage location.

D. Settle liabilities resulting from consignment stock receipts: In the standard consignment process, no financial liability is created upon goods receipt. The material is recorded in inventory as non-valuated stock owned by the supplier. Liability is only generated upon withdrawal.

1. SAP Help Portal - Managing Special Stocks - Consignment: "For consignment materials

you must create a consignment info record." This document confirms the necessity of the consignment info record.

Source: SAP S/4HANA Documentation

"Consignment". (A specific URL is difficult as it's within the SAP Help Portal structure

but the path is typically: SAP S/4HANA -> Enterprise Business Applications -> Sourcing and Procurement -> Inventory Management and Physical Inventory (MM-IM) -> Managing Special Stocks -> Consignment).

2. SAP Help Portal - Consignment Settlement: "In consignment processing

the vendor makes material available to you... The material remains the property of the vendor until you withdraw it from the consignment stores. Only then does the vendor require payment. The liability to the vendor is created when the material is withdrawn

and the liability is settled at regular intervals..." This confirms that settlement occurs after withdrawal

not receipt.

Source: SAP S/4HANA Documentation

"Consignment Settlement". (Path: SAP S/4HANA -> Enterprise Business Applications -> Sourcing and Procurement -> Logistics Invoice Verification (MM-IV) -> Consignment Settlement).

When an invoice is posted with invoice reduction in SAP S/4HANA, the system executes two distinct actions. First, it posts an invoice document for the corrected (reduced) amount that the company accepts as a liability. Simultaneously, it automatically posts a credit memo for the difference between the vendor's original invoice amount and the corrected amount. This results in two separate accounting documents. To inform the vendor of this adjustment and the reason for the partial payment, the system generates a message (e.g., a letter of complaint) via its output determination function, which can then be sent to the supplier.

C. The invoice is blocked for payment until the supplier confirms the credit memo receipt.

This is incorrect. The system does not have a standard function to wait for supplier confirmation. Payment blocks are typically triggered by tolerance limit variances, not by the invoice reduction process itself.

D. Only one accounting document is created, containing both the invoice and the credit memo postings.

This is incorrect. To maintain accounting clarity and follow the document principle, SAP creates two separate documents: one for the invoice liability and one for the credit memo (claim against the vendor).

1. SAP Help Portal - SAP S/4HANA

"Invoice Reduction in Logistics Invoice Verification": This official documentation explicitly states the system's behavior. It confirms that two documents are created and a message is generated for the vendor.

"When you post the invoice

the system creates two documents: The invoice

for the amount you entered. A credit memo

for the difference between the amount you entered and the amount the vendor specified."

"The system also creates a mail message to the vendor

informing them of the reduction."

URL: https://help.sap.com/docs/SAPS4HANAON-PREMISE/8308e6d301d54584a33cd04a9861bc52/2c6b89535c38b44ce10000000a174cb4.html (Note: This link is for a specific S/4HANA version

but the functionality is standard across recent versions).

2. SAP Press - "Materials Management with SAP S/4HANA: Business Processes and Configuration" (2nd Edition): This publication details the business process.

In Chapter 13

Section 13.5.3

"Invoice Reduction

" the authors describe the process: "When you post the invoice

the system creates two documents: an invoice for the corrected amount and a credit memo for the difference... The system also automatically generates a letter of complaint to the vendor." This corroborates the creation of two documents and a notification message.

In SAP S/4HANA, a cross-company-code purchasing organization is defined by not being assigned to any specific company code. This configuration allows it to procure for multiple company codes. For this to be operational, the purchasing organization must be assigned to the plants for which it is responsible. These plants can belong to different company codes. During a transaction, such as creating a purchase order, the system determines the correct company code for financial postings from the plant specified in the document. Therefore, the direct and mandatory assignment that enables cross-company-code functionality is the link to the plants.

B. To a standard purchasing organization: A standard purchasing organization is a functional role used for specific processes like pipeline or consignment procurement, not a structural assignment for cross-company operations.

C. To the company codes for which it is responsible: This is incorrect. Assigning a purchasing organization to a company code makes it company-code-specific. A cross-company-code purchasing organization is explicitly not assigned to any company code.

D. To a reference purchasing organization: A reference purchasing organization is a separate concept that allows other purchasing organizations to use its contracts and conditions, focusing on centralized negotiation, not operational scope.

1. SAP S/4HANA Help Portal - Organizational Levels in Procurement: "A purchasing organization that is not assigned to a company code can procure for all plants assigned to it

regardless of the company code they belong to. In this case

the purchasing organization must be assigned to the plants it is responsible for." This source directly validates that the assignment to plants is the required step.

Source: SAP Help Portal

S/4HANA 2023

Organizational Levels in Procurement.

2. SAP S/4HANA Help Portal - Assign Purchasing Organization to Company Code: "If you do not assign a company code to a purchasing organization

this purchasing organization can engage in procurement operations for every company code... When you create a purchasing document

the system determines the company code from the plant." This confirms that the absence of a company code assignment is key

and the link is via the plant.

Source: SAP Help Portal

S/4HANA 2023

IMG Activity: Assign Purchasing Organization to Company Code.

3. SAP S/4HANA Press - Sourcing and Procurement with SAP S/4HANA: In the chapter on Organizational Structures

it is detailed that a purchasing organization's scope (plant-specific

cross-plant

or cross-company-code) is determined by its assignments. For cross-company-code purchasing

the configuration involves assigning the purchasing organization to plants of different company codes while leaving the direct assignment to a company code blank.

Source: Rheinwerk Publishing (SAP Press)

Sourcing and Procurement with SAP S/4HANA (ISBN: 978-1-4932-1939-7)

Chapter 3: Organizational Structures.

The account assignment category is a key configuration element in SAP Materials Management that dictates how a purchased item is treated financially and logistically. Its primary control functions are:

1. To determine the specific type of account assignment object that must be provided (e.g., Cost Center 'K', Asset 'A', Sales Order 'C'). The system will then display the corresponding fields for data entry.

2. To control the follow-on logistics processes, specifically whether a goods receipt (GR) posting is permissible or required, and if so, whether it should be valuated or non-valuated. These settings are configured directly for each account assignment category.

A. Whether you must enter a material: This is incorrect. Using an account assignment category enables procurement without a material master (text-based purchase), making the material number optional, not mandatory.

D. The item categories you are allowed to use: This is incorrect. The relationship is reversed; the item category (e.g., Service, Standard) can restrict which account assignment categories are permissible, but the account assignment category does not control the selection of the item category.

1. SAP S/4HANA Help Portal - Account Assignment in Purchasing: "The account assignment category determines: The nature of the account assignment (cost center

sales order

and so on). Which accounts are to be charged when the incoming invoice or goods receipt is posted. Which account assignment data you must provide." This directly supports option B. The same document details how GR/IR control indicators are set within the account assignment category

supporting option C.

URL: https://help.sap.com/docs/SAPS4HANAON-PREMISE/af9ef57f504840d2b81be8667206d485/a763b6535fe6b74ce10000000a174cb4.html (Path: SAP S/4HANA -> Materials Management -> Purchasing -> Account Assignment)

2. SAP S/4HANA Help Portal - Configuration of Account Assignment Categories: The configuration settings for an account assignment category include indicators like "Goods Receipt" and "GR Non-Valuated". This explicitly demonstrates that the account assignment category controls the goods receipt process.

URL: https://help.sap.com/docs/SAPS4HANAON-PREMISE/af9ef57f504840d2b81be8667206d485/7563b6535fe6b74ce10000000a174cb4.html (Path: SAP S/4HANA -> Materials Management -> Purchasing -> Account Assignment -> Configuration of Account Assignment Categories)

3. SAP Press (2022). Materials Management with SAP S/4HANA: Business Processes and Configuration. Rheinwerk Publishing. Chapter 5

Section 5.2.4

"Account Assignment Category

" explains that this key determines the account assignment data required (e.g.

cost center

G/L account) and controls the subsequent goods and invoice receipt postings. This supports both correct answers B and C.

In SAP S/4HANA, the Material Ledger (ML) is a mandatory component for inventory valuation. A primary function of the ML is to manage material prices in multiple currencies and valuations, allowing for parallel valuation in up to three currencies (e.g., company code, group, and hard currency). Furthermore, the ML is the foundation for Actual Costing. It collects all value-relevant transaction data throughout a period to calculate a periodic unit price (PUP). This PUP represents the actual cost of the material for that period and can be used to revalue inventory, thus providing different prices for material valuation beyond the standard price.

A: The material ledger is activated at the valuation area level (typically the plant), not the controlling area level. A controlling area can encompass multiple valuation areas.

E: The material ledger calculates the periodic unit price (actual cost) at the end of a period. The standard price is calculated via a standard cost estimate (e.g., costing run).

1. SAP Help Portal - S/4HANA - Material Ledger: "In SAP S/4HANA

the material ledger is obligatory and must be active." This supports option C.

URL: https://help.sap.com/docs/SAPS4HANAON-PREMISE/1e647943c63b4fb699935129b6120c5c/4764395876533304e10000000a114a6b.html

2. SAP Help Portal - S/4HANA - Multiple Currencies and Valuations: "The material ledger allows you to manage material inventory values in two additional currencies/valuations." This supports option D.

URL: https://help.sap.com/docs/SAPS4HANAON-PREMISE/1e647943c63b4fb699935129b6120c5c/4764395876533304e10000000a114a6b.html (within the "Features" section of the main Material Ledger page).

3. SAP Help Portal - S/4HANA - Actual Costing/Material Ledger: "At the end of the period

a periodic unit price is calculated for the material using the actual costs incurred in that period. This price can be used to revalue the inventory." This supports option B.

URL: https://help.sap.com/docs/SAPS4HANAON-PREMISE/1e647943c63b4fb699935129b6120c5c/4764395876533304e10000000a114a6b.html (within the "Features" section).

4. SAP Help Portal - S/4HANA - Activation of Material Ledger for Valuation Areas: "You activate the material ledger for one or more valuation areas." This proves option A is incorrect.

URL: https://help.sap.com/docs/SAPS4HANAON-PREMISE/1e647943c63b4fb699935129b6120c5c/4764395876533304e10000000a114a6b.html (within the "Implementation Considerations" section).