The valuation grouping code is the standard mechanism in SAP S/4HANA to simplify account determination across multiple valuation areas (plants). By assigning the same valuation grouping code to several plants, you only need to configure the G/L account assignments once for that code, and all associated plants will use those settings. This is only effective for plants belonging to company codes that use the same chart of accounts, because the G/L accounts themselves are defined at the chart of accounts level. This approach directly reduces redundant configuration effort.

A: Incorrect. Account determination is defined per chart of accounts. You cannot group plants that use different charts of accounts to share the same G/L account settings.

B: Incorrect. The "account grouping code" (more precisely, the Account Category Reference) is used to group material types with similar valuation characteristics, not to group plants.

D: Incorrect. This option uses the wrong tool (account grouping code for materials, not plants) and the wrong condition (different charts of accounts).

SAP Help Portal

SAP S/4HANA

Grouping Together Valuation Areas: "The valuation grouping code makes it easier to set automatic postings. Within a chart of accounts

you can group together valuation areas by assigning them the same valuation grouping code... You then only have to define the G/L accounts for this one valuation grouping code."

URL: https://help.sap.com/docs/SAPS4HANAON-PREMISE/af9ef57f504840d2b81be8667206d4c8/4d7fe7536e8e2a4be10000000a174cb4.html (This link points to the concept in the context of Materials Management -> Valuation and Account Assignment).

SAP Help Portal

SAP S/4HANA

Automatic Posting - Configuration: "Prerequisites: You have grouped together the valuation areas that are to be treated in the same way for account determination purposes. To do this

you have assigned the same valuation grouping code to these valuation areas in the activity Group Together Valuation Areas."

URL: https://help.sap.com/docs/SAPS4HANAON-PREMISE/af9ef57f504840d2b81be8667206d4c8/4d7ff0536e8e2a4be10000000a174cb4.html (This link details the configuration steps where valuation grouping is a prerequisite).

SAP Signavio Process Governance is the specific solution used to automate and execute business processes as structured workflows. After a process is modeled in SAP Signavio Process Manager, Process Governance is used to turn that model into an executable workflow, managing tasks, approvals, and ensuring compliance. This directly addresses the requirement to "create the necessary workflows" for the newly remodeled business processes.

A. SAP Signavio Process Manager: This tool is for modeling, documenting, and simulating business processes (the "to-be" design), not for creating the executable, automated workflow itself.

B. SAP Signavio Process Insights: This solution provides analysis and insights into the performance of existing processes within an SAP system; it does not create new workflows.

D. SAP Signavio Process Intelligence: This is a process mining tool used to discover, monitor, and analyze the actual execution of processes based on system data, not for building new workflows.

1. SAP Signavio Process Governance: According to the official SAP Help Portal

"SAP Signavio Process Governance is an approval workflow engine. You can use it to automate and monitor your approval processes." This confirms its role in creating and managing executable workflows.

Source: SAP Help Portal

"What is SAP Signavio Process Governance". (URL: https://help.sap.com/docs/signavio-process-governance/user-guide/what-is-sap-signavio-process-governance)

2. SAP Signavio Process Manager: The documentation states

"SAP Signavio Process Manager is a professional process modeling tool. It allows you to document

design

and simulate processes." This clearly defines its function as modeling

distinct from workflow execution.

Source: SAP Help Portal

"What is SAP Signavio Process Manager". (URL: https://help.sap.com/docs/signavio-process-manager/user-guide/what-is-sap-signavio-process-manager)

3. SAP Signavio Suite Overview: Official documentation differentiates the products

positioning Process Governance as the tool for workflow automation based on models from Process Manager.

Source: SAP Help Portal

"SAP Signavio Process Transformation Suite". (URL: https://help.sap.com/docs/signavio-process-transformation-suite)

In SAP S/4HANA, a stock transport order (STO) is a robust method for managing internal stock movements between plants.

(B) As STOs are integrated with the purchasing module, they utilize the condition technique. This allows for the inclusion of planned delivery costs, such as freight and customs, directly within the order.

(C) Upon goods receipt at the receiving plant (e.g., using movement type 101), the system provides the flexibility to post the incoming materials to various stock types, including unrestricted-use, quality inspection, or blocked stock, depending on the business requirement.

(E) In a two-step stock transfer procedure, once the goods issue is posted from the supplying plant, the material quantity is logically removed from the supplying plant's inventory and placed into "stock in transit." This stock is visible to and managed by the receiving plant, providing transparency over in-bound logistics.

A: The standard process for a goods issue against a stock transport order requires the stock to be in "unrestricted-use" status in the supplying plant. Stock in quality inspection must first be cleared via a usage decision.

D: For an intra-company code stock transfer, the goods issue posting generates a single accounting document. This document debits the stock-in-transit account and credits the inventory account, all within the same company code's books.

1. SAP S/4HANA Help Portal - Stock Transfer Using a Stock Transport Order: This official documentation confirms key features.

For B

C

E: "You can enter delivery costs in the stock transport order... At the time of goods receipt

you can post the material to... blocked stock... The quantity posted from stock is managed as stock in transit in the receiving plant."

For A: "The goods issue is posted from the unrestricted-use stock of the issuing plant."

URL: https://help.sap.com/docs/SAPS4HANAON-PREMISE/32da8359c8ee4e8b86032e2a7ac0424b/a758b45343e4b44ce10000000a174cb4.html (Specific version: SAP S/4HANA 2023)

2. SAP S/4HANA Help Portal - Goods Movement Documentation: This source details the accounting impacts of goods movements.

For D: For an intra-company stock transfer (movement type 351)

the material document is accompanied by one accounting document that reflects the value change within the single company code.

URL: https://help.sap.com/docs/SAPS4HANAON-PREMISE/32da8359c8ee4e8b86032e2a7ac0424b/a758b45343e4b44ce10000000a174cb4.html (This page also covers the financial posting logic implicitly by describing the process within a single company code). A more detailed look at movement type accounting confirms a single FI document.

SAP's Clean Core strategy mandates the use of stable, released, and decoupled interfaces to ensure the system remains upgrade-safe and maintainable. OData and SOAP are the primary types of modern, synchronous APIs that SAP officially releases and recommends for building such integrations. These APIs are documented and discoverable on the SAP Business Accelerator Hub. They are designed to be upgrade-stable and are based on open standards (REST for OData, XML for SOAP), aligning perfectly with the principles of a clean, modern architecture.

B. IDoc: IDoc is a classic asynchronous integration technology. While still supported, SAP's modern integration strategy for Clean Core prioritizes modern, released APIs over these legacy methods for new developments.

D. RFC: Remote Function Call (RFC) is a classic, tightly coupled, and proprietary SAP protocol. Its use is explicitly discouraged in a Clean Core approach in favor of loosely coupled, standardized APIs.

1. SAP Official Documentation - Extensibility Guide for SAP S/4HANA Cloud: The guide outlines the extensibility patterns for maintaining a Clean Core. It emphasizes the use of released SAP APIs for side-by-side extensions. The guide states

"SAP S/4HANA Cloud offers a wide range of local and remote APIs that are based on standard protocols

such as OData and SOAP."

Source: SAP Help Portal

Extensibility Guide for SAP S/4HANA Cloud

Section: "Released SAP APIs". (A specific URL is dynamic

but this can be found by searching the title on help.sap.com).

2. SAP Whitepaper - Clean Core for SAP S/4HANA: This whitepaper details the principles of Clean Core

highlighting the importance of using public

stable APIs for integrations. It contrasts modern APIs (like OData and SOAP) with classic technologies.

Source: SAP Community Whitepaper

"An Introduction to Clean Core for SAP S/4HANA

" Page 5

Section: "Pillar 2: Integration." It advocates for using APIs from the SAP Business Accelerator Hub

which primarily features OData and SOAP services.

3. SAP Business Accelerator Hub: This is the central catalog for all SAP APIs. A review of the available APIs for SAP S/4HANA Cloud and On-Premise shows that the vast majority of recommended and released interfaces are OData and SOAP services

confirming their status as the preferred choice for Clean Core integrations.

Source: SAP Business Accelerator Hub

https://api.sap.com/. Filter by Product "SAP S/4HANA" to view the catalog of recommended APIs.

SAP allows an existing purchasing info record to be updated automatically only when a purchase order is saved with the “Info Update” indicator set. In this case the system delimits the old time-dependent conditions and writes the new conditions from the PO into the already-existing info record. The indicator in contracts or release orders is either not available or does not update the info record; in quotations it creates a new info record if none exists but does not overwrite an existing one. (SAP S/4HANA MM Purchasing, Automatic Creation/Update of Info Records).

A. Contract maintenance (ME31K/ME32K) has no “Info Update” field; outline agreements never update info-records.

B. Release orders copy prices from the contract; even if “Info Update” were set, no condition change is written back.

C. In quotations the indicator can create an info record, but existing time-dependent conditions are not overwritten.

1. SAP Help Portal – S/4HANA 2023

Materials Management > Purchasing > Master Data > Purchasing Info Record > Automatic Creation of Purchasing Info Records

section “Updating Existing Info Records from Purchase Orders”.

https://help.sap.com/docs/SAPS4HANAON-PREMISE/e64d3eca859a4e43b4e7a1d5e451ab41/automatic-creation-of-purchasing-info-records

2. SAP Press

“Materials Management with SAP S/4HANA” (Keller/Teige)

ch. 7.2

p. 308-309: “Only the Purchase Order offers the option to update time-dependent conditions of an existing info record via the Info Update indicator.”

For a split-valuated material, the price control set in the accounting view at the valuation area level (the "header record") dictates the price control options for the individual valuation types. A refurbishment process inherently involves changes in material value (e.g., from a low-value 'defective' state to a higher-value 'repaired' state). The moving average price ('V') is the appropriate price control to automatically reflect these value changes. To use moving average price for the valuation types, the system requires that the price control for the valuation area header record must also be set to moving average price ('V'). This is a fundamental configuration prerequisite.

A. For the valuation area, the price control must be standard price.

This is incorrect. Setting the header to standard price ('S') would force all valuation types to also be 'S', which is unsuitable for a refurbishment process.

B. For each possible valuation type, the price control must be moving average price.

While this is the recommended practice for the valuation types in this scenario, it is a consequence of the business need, not the primary system prerequisite. This choice is only possible if the valuation area is set correctly first.

C. For each possible valuation type, the price control must be standard price.

This is incorrect. Standard price does not automatically update with value changes from goods movements, making it unsuitable for tracking the value increase during refurbishment.

1. SAP Help Portal (S/4HANA): In the documentation for "Valuation of a Material with Split Valuation

" it is stated as a prerequisite: "In the accounting view of the material master record: ... For the valuation header record

you have entered V (moving average price) as the price control. (If you choose S

you must use the standard price for all valuation types.)" This confirms that to use 'V' for the types

the header must be 'V'.

Source: SAP Help Portal

S/4HANA

"Prerequisites for Valuating a Material with Split Valuation".

2. SAP Learning Hub: The course content for SAP S/4HANA Sourcing and Procurement (e.g.

TS452) explains that the price control in the valuation header record constrains the price control in the valuation-type-specific data. For processes with fluctuating values like refurbishment

moving average price is the standard recommendation

which necessitates setting the header record to 'V'.

Source: SAP Learning Hub

Course TS452

Unit: "Valuation and Account Assignment".

3. SAP Press Publication: In "Materials Management with SAP S/4HANA: Business Processes and Configuration" by Akhtar & Murray

the configuration of split valuation is detailed. The book clarifies that the header record's price control setting is a critical first step that determines the valuation strategy for all subordinate types.

Source: Akhtar

J.

& Murray

M. (2021). Materials Management with SAP S/4HANA: Business Processes and Configuration. SAP Press. Chapter 6

Section 6.5 "Material Valuation".

In purchase-order-based invoice verification within SAP S/4HANA, the system's behavior is designed to simplify the process by referencing the cumulative history of a purchase order item. When an invoice is entered, the system aggregates all goods receipts associated with a single PO item into one line on the invoice document, rather than listing each partial delivery separately. For the quantity proposal, the system calculates the outstanding quantity to be invoiced. This is determined by taking the total quantity delivered to date and subtracting the total quantity that has already been invoiced for that specific PO item.

A: This statement describes the behavior of Goods-Receipt-Based (GR-Based) Invoice Verification, where each goods receipt is treated as a distinct item to be invoiced, not PO-based verification.

D: This is incorrect as it fails to account for quantities that have already been invoiced. Proposing the total delivered quantity could lead to duplicate payments for the same goods.

1. SAP Help Portal - S/4HANA - Invoice Verification Based on Purchase Orders: "When you post an invoice with reference to a purchase order

the system proposes the items from the purchase order. The quantity and value are defaulted from the difference between the goods receipts and the invoices posted so far. All goods receipts for a purchase order item are totaled and posted as one item in the invoice." This directly supports options B and C.

URL: https://help.sap.com/docs/SAPS4HANAON-PREMISE/af9ef57f504840d2b81be8667206d485/6147b7536e8e254be10000000a174cb4.html (Version 2023)

2. SAP Help Portal - S/4HANA - GR-Based Invoice Verification: This document clarifies the alternative process

stating

"If you are expecting several deliveries for a purchase order

it makes sense to have GR-based Invoice Verification. This means that each goods receipt is settled in a separate invoice item." This confirms why option A is incorrect for PO-based verification.

URL: https://help.sap.com/docs/SAPS4HANAON-PREMISE/af9ef57f504840d2b81be8667206d485/6547b7536e8e254be10000000a174cb4.html (Version 2023)

Setting the "Delivery Completed" indicator (technical field name: ELIKZ) in a purchase order (PO) item signals that the procurement process for that item is considered finished. Consequently, any remaining open quantity for the item is no longer considered an expected receipt by Material Requirements Planning (MRP), making the item irrelevant for the MRP run. While the indicator signals that no further deliveries are expected, the system does not by default prevent further goods receipts. Postings are still possible, for instance, if they fall within specified under/overdelivery tolerances.

C. The commitment for the PO item increases.

This is incorrect. Setting the "Delivery Completed" indicator reduces or clears the open financial commitment associated with the PO item, as the obligation is now considered fulfilled.

D. The order quantity of the PO item is still open.

This is incorrect. The primary function of the "Delivery Completed" indicator is to manually close the PO item, effectively setting the open order quantity to zero for planning purposes.

1. SAP Help Portal - S/4HANA - "Delivery Completed" Indicator:

"If the "delivery completed" indicator has been set for an item

the open purchase order quantity is zero

even if the full quantity has not been delivered. The item is then no longer taken into account by materials planning." This supports option B and refutes option D.

"Even if an item is considered closed

you can still post goods receipts against it. These goods receipts will be flagged as excess deliveries." This supports option A.

URL: https://help.sap.com/docs/SAPS4HANAON-PREMISE/af9ef57f504840d2b81be8667206d485/4d788d341a360974e10000000a114a6b.html (Specific section on "Delivery Completed" Indicator).

2. SAP Help Portal - S/4HANA - Commitment Management:

The documentation on commitment management explains that commitments from purchase orders are reduced by goods receipts and invoice receipts. Setting the "Delivery Completed" indicator finalizes the item

which leads to the clearing of any remaining commitment value. This refutes option C.

URL: https://help.sap.com/docs/SAPS4HANAON-PREMISE/e296651f454c4284ade361292c633d69/45b99558048341dee10000000a114a6b.html (General concept of commitment reduction/clearing).

For the system to automatically convert a purchase requisition (PR) into a purchase order (PO), several master data and transactional data prerequisites must be met. First, both the material master record (plant-specific purchasing view) and the business partner master record (purchasing data) must have the "Automatic Purchase Order" indicator set. This flags both the item and the supplier as eligible for this automated process. Second, the purchase requisition itself must have a unique and valid source of supply assigned to it. This source, typically a purchasing info record or a contract, provides the necessary information, such as the vendor and valid pricing conditions, that the system needs to create the purchase order document without manual intervention.

A. A contract with plant-specific conditions exists for the material and the vendor.

This is too specific. A purchasing info record is also a valid source of supply, so a contract is not a mandatory prerequisite.

E. A plant-specific source list entry exists for the material.

While a source list is a primary tool for automatic source determination, the direct prerequisite for PO conversion is that a source is assigned to the PR, which is stated more accurately in option D.

1. SAP S/4HANA Help Portal

"Automatic Creation of Purchase Orders from Requisitions": This official documentation outlines the prerequisites for the process. It explicitly states:

"The automatic purchase order indicator has been set in the purchasing data of the material master record." (Supports option B)

"The automatic purchase order indicator has been set in the business partner master record." (Supports option C)

"A source of supply that is valid for the delivery date has been assigned to the purchase requisition item." (Supports option D)

URL: https://help.sap.com/docs/SAPS4HANAON-PREMISE/af9ef57f504840d2b81be8667206d485/abe5b553088f4308e10000000a174cb4.html (Version 2023)

2. SAP S/4HANA Help Portal

"Prerequisites for Source Assignment": This page details how a source is found

mentioning the source list as a key tool

but reinforces that the outcome—an assigned source on the PR—is what enables subsequent processes like automatic PO creation.

URL: https://help.sap.com/docs/SAPS4HANAON-PREMISE/af9ef57f504840d2b81be8667206d485/a2e5b553088f4308e10000000a174cb4.html (Version 2023)

SAP S/4HANA uses the low-level code to determine the sequence for material requirements planning. The low-level code represents the lowest level at which a material appears in any Bill of Material (BOM). The planning run processes materials sequentially by their low-level code, starting with code 0 (e.g., finished products) and proceeding to higher-numbered codes (e.g., raw materials). This hierarchical approach ensures that all demands for a material are known before the system plans the material itself, guaranteeing correct net requirements calculation down the entire BOM structure.

A. Source list: This defines approved sources of supply for a material. It determines where a material is procured from, not the sequence in which it is planned.

B. MRP group: This groups materials to assign common planning control parameters (e.g., planning strategy). It influences how a material is planned, not its sequence relative to others.

D. Quota arrangement: This distributes procurement quantities among different sources of supply. It controls the proportion of supply from various sources, not the planning order.

1. SAP Help Portal - Low-Level Code: "The low-level code represents the lowest level of usage of a material within all product structures... During the MRP run

the system plans the materials in the order of their low-level codes

starting with low-level code 0."

URL: https://help.sap.com/docs/SAPS4HANAON-PREMISE/f899ce30af9044299d573ea30b533f1c/4d7fe05314894208e10000000a174cb4.html (Version 2023)

2. SAP Help Portal - The Logic of the Planning Run: "The system plans all materials with the low-level code 0 first

then all those with low-level code 1

and so on. This ensures that the dependent requirements for a component are created before the component itself is planned."

URL: https://help.sap.com/docs/SAPS4HANAON-PREMISE/f899ce30af9044299d573ea30b533f1c/4d7fe35314894208e10000000a174cb4.html (Version 2023)