CONFIGURATION WORKBENCHSPRO, transactions, transport, proof

P2P 404 · AT THE KEYBOARD

How do you configure Procure to Pay?

Build and prove one connected stocked-material procurement flow from enterprise structure and approved demand through purchase order, goods receipt, invoice verification, supplier payment, and clearing.

WORKBENCH ENVELOPE

One minimum configuration spine

Extensions stay outside the spine until the stocked-material flow posts and reconciles.

Included

One company code, plant, storage location, purchasing organization, and purchasing group
One approved purchase requisition converted to a standard purchase order
One stock-managed valuated material and one supplier
Partial goods receipt, PO-based invoice verification, GR/IR, supplier open item, payment, and clearing
Workflow, output, tax, tolerance, account determination, and end-to-end reconciliation evidence

Extensions—not included yet

Services, subcontracting, consignment, stock transport orders, and third-party procurement
Ariba, external sourcing networks, EDI, supplier portals, and custom integrations
Assets, projects, complex account assignment, evaluated receipt settlement, and non-PO invoices
Advanced warehouse, quality, batch, serial, import, and localization-specific scenarios
Production bank connectivity and payment-format implementation beyond a controlled test channel

CONFIGURATION WORKBENCH

Connect the procurement enterprise structure

The company code, plant, storage location, purchasing organization, and purchasing group form a valid responsibility and valuation chain.

SPRO / IMG path

Enterprise Structure → Definition → Logistics - General → Define, copy, delete, check plant

Enterprise Structure → Definition → Materials Management → Maintain storage location; Maintain purchasing organization

Enterprise Structure → Assignment → Materials Management → Assign purchasing organization to company code and plant

Materials Management → Purchasing → Create Purchasing Groups

Enterprise Structure → Definition → Logistics - General → Define valuation level

Plant definition → Assign factory calendar for purchasing delivery-date calculation

Enterprise Structure → Assignment → Logistics - General → Assign plant to company code

Transactions and apps

OX10 / OX09Define plant / storage location

OX08 / OX01Define purchasing organization / assign to company code

OX17 / OME4Assign purchasing organization to plant / maintain purchasing group

OBY6Inspect company-code settings

OX14Define valuation level before productive material valuation

OX18Assign plant to company code and valuation area

Configuration and evidence objectsT001T001WT001LT024ET024T024WT001KTFACD

Maintain in this order

Confirm legal company-code, currency, chart-of-accounts, and posting-period decisions before adding procurement assignments.
Define or reuse the plant and storage location, then verify valuation-area behavior for the target system.
Define the purchasing organization and assign it to the company code and plant using the approved central or plant-specific model.
Maintain the purchasing group and prove that the organizational combination is available in master data and purchasing documents.
Set the valuation level before productive postings and confirm its consequences for valuation areas, account determination, and Material Ledger.
Assign the plant factory calendar and prove that non-working days affect PO delivery dates as designed.

RUNME21N organization data and MM03 plant/storage views

EXPECTED PROOF

The intended company code, purchasing organization, purchasing group, plant, and storage location are valid together without manual structural overrides.

If it fails, check here first

Plant or purchasing organization unavailable: inspect definitions, company-code assignment, and plant assignment.
Company code differs from expectation: inspect plant valuation/company assignment and purchasing-organization scope.
Storage location rejected: verify that it exists for the selected plant and is valid for the material.

Release-sensitive: Valuation level is foundational and difficult or impossible to reverse after productive valuation. Factory-calendar ownership is cross-process. Confirm the installed release, migration state, and enterprise calendar governance before changing either.

CONFIGURATION WORKBENCH

Prepare supplier, material, and accounting data

Supplier and material records contain the purchasing, company-code, plant, valuation, tax, and payment inputs the process expects.

SPRO / IMG path

Cross-Application Components → SAP Business Partner → Business Partner → Basic Settings

Materials Management → Purchasing → Material Master → Define Purchasing Value Keys

Materials Management → Valuation and Account Assignment → Account Determination → Account Determination Without Wizard

Financial Accounting → Accounts Receivable and Accounts Payable → Supplier Accounts → Master Data

Logistics - General → Material Master → Basic Settings → Material Types → Define attributes and quantity/value updating

Logistics - General → Material Master → Field Selection → Maintain field selection for data screens

Materials Management → Purchasing → Material Master → Define Material Groups and Purchasing Value Keys

Cross-Application Components → Master Data Synchronization → Customer/Supplier Integration → Business Partner Settings

Transactions and apps

BPMaintain supplier general, company-code, purchasing, tax, bank, and partner data

MM01 / MM02 / MM03Maintain and inspect material purchasing, plant, storage, and accounting views

ME11 / ME13Maintain / display purchasing info record

XK03Display supplier compatibility view where available

OMS2 / OMS9Material-type quantity/value updating and field selection

OMSF / OMQWMaterial groups and non-stock default behavior

OMFI / OMCQBuyer defaults and MM message control

OMGA / OMGB / SO10Supplier and purchasing text controls where the classic text framework applies

Configuration and evidence objectsBUT000LFA1LFB1LFM1MARAMARCMARDMBEWEINAEINET134MT023T405T160MT052TINCT077KNRIV

Maintain in this order

Create or extend the supplier business partner to the company code and purchasing organization with reconciliation account, payment terms, methods, order currency, incoterms, tax, and partner roles.
Extend the material to purchasing, plant, storage, and accounting views with order units, purchasing group, planned delivery time, valuation class, and price control.
Create only the purchasing info or source data needed to prove determination; record whether price and delivery data come from the master, agreement, or PO.
Validate G/L extension, tax readiness, open posting periods, and known stock or receipt conditions before testing.
Confirm material-type quantity/value updating, field selection, material groups, purchasing value keys, reminder days, GR tolerances, and buyer defaults before creating test masters.
Govern supplier grouping, BP-to-supplier account-group mapping, number ranges, terms, incoterms, partner functions, and purchasing texts as separate decisions rather than copying legacy vendor settings blindly.

RUNBP, MM03, ME13, and a controlled ME21N

EXPECTED PROOF

Supplier, material, price source, plant, valuation class, units, terms, tax, and reconciliation account derive without unexplained manual correction.

If it fails, check here first

Supplier cannot be used: inspect BP roles, grouping, company-code extension, purchasing extension, block, and partner functions.
Material rejected: inspect plant/purchasing/accounting views, procurement type, order unit, status, and valuation data.
Accounting or payment data missing: inspect reconciliation account, payment terms/methods, bank data, G/L extension, and posting period.

Release-sensitive: SAP S/4HANA uses Business Partner as the leading supplier object and requires Customer/Supplier Integration mapping. Transactions such as MK01/MK02/XK03 and legacy vendor number-range activities are compatibility or migration references, not the default S/4HANA maintenance path. Material Ledger is mandatory; actual costing remains optional.

CONFIGURATION WORKBENCH

Configure requisitions and request approval

A complete stock-material requisition captures executable demand and follows the intended approval path before conversion.

SPRO / IMG path

Materials Management → Purchasing → Purchase Requisition → Define Document Types

Materials Management → Purchasing → Purchase Requisition → Define Screen Layout at Document Level

Materials Management → Purchasing → Purchase Requisition → Set Up Procedure with Classification, where the approved classic path applies

SAP Business Workflow → Flexible Workflow → Scenario Activation and Responsibility Management, where activated

Materials Management → Purchasing → Purchase Requisition → Number Ranges

Materials Management → Purchasing → Purchase Requisition → Release Procedure → Procedure with Classification, only for an approved classic branch

Transactions and apps

OME5 / OMEBRequisition document types / number ranges

ME51N / ME52N / ME53NCreate / change / display purchase requisition

ME54NRelease requisition in classic release scenarios

SWI1 / Fiori workflow appsInspect workflow instance and decisions

OMH7 / target IMG activityValidate the PR number-range activity in the installed release

CL03 / CT04 / CL24NInspect classic release class, characteristics, and values where retained

Manage Workflows for Purchase RequisitionsConfigure and activate the S/4HANA flexible-workflow branch where available

Configuration and evidence objectsT161T161AEBANEBKNCDHDRCDPOST16FGT16FST16FCT16FBT16FWCABNCAWN

Maintain in this order

Copy or reuse a requisition document type and confirm number range, item interval, permitted item categories, and field selection.
Define the minimum complete stock-material request: material, quantity, date, plant, storage location where needed, purchasing group, and requester.
Choose classic release or flexible workflow for the target release; define start conditions, steps, responsibility, thresholds, rejection, substitution, and restart behavior.
Run one below-threshold and one approval-required requisition, then change a consequential value and prove the intended restart.
For a classic branch, prove classification characteristics, values, release groups, codes, indicators, strategy matrix, workflow linkage, and change/reset behavior. For a flexible branch, prove scenario activation, ordered start conditions, default workflow, recipients, substitutions, and restart logic.

RUNME51N → workflow approval or ME54N → ME53N status

EXPECTED PROOF

Complete demand follows the designed authority path, records the decision, and becomes convertible only when its required release is complete.

If it fails, check here first

Workflow does not start: inspect scenario activation, start conditions, document type, value, company/plant context, and event log.
No approver: inspect responsibility rules, teams, functions, user validity, substitution, and fallback behavior.
Released request restarts unexpectedly: inspect which changed fields or values are configured as consequential.

Release-sensitive: Flexible workflow is the S/4HANA strategic approval path and available apps vary by edition and release. Classic classification-based release remains scope-dependent. Treat transaction-code differences such as OMEB versus OMH7 as target-system verification items, not universal instructions.

CONFIGURATION WORKBENCH

Configure source determination and agreements

The approved requisition finds the intended valid supplier or outline agreement and preserves why that source was chosen.

SPRO / IMG path

Materials Management → Purchasing → Source Determination → Maintain Source List

Materials Management → Purchasing → Source Determination → Define Quota Arrangement Usage

Materials Management → Purchasing → Conditions → Define Price Determination Process

Materials Management → Purchasing → Contract → Define Document Types

Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Calculation Schema

Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Condition Types and Access Sequences

Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Schema Groups and Schema Determination

Transactions and apps

ME01 / ME03Maintain / display source list

ME11 / ME13Maintain / display purchasing info record

ME31K / ME33KCreate / display contract

ME57 / ME59NAssign/process requisitions / automatic PO creation

M/08 / M/06 / M/05Calculation schemas / condition types / access sequences

MEK1 / MEK3Maintain / display purchasing condition records

TMKE / TMKK / TMKSPurchasing-organization and supplier schema groups / schema determination where exposed by the release

Configuration and evidence objectsEORDEINAEINEEKKOEKPOKONHKONPT683ST685AT682IT024E

Maintain in this order

Decide whether the minimum flow uses a fixed source list entry, info record, or contract; keep quota and tendering outside the spine unless required.
Maintain valid plant, material, supplier, purchasing organization, dates, fixed-source or agreement reference, and any MRP relevance.
Maintain the permitted commercial source and prove the price, planned delivery time, currency, terms, and target-value or quantity consumption.
Run source assignment on a controlled requisition and inspect why alternative sources were selected, skipped, or blocked.
Define the calculation sequence, condition classes, subtotals, account keys, manual-change policy, and planned delivery costs; then determine the schema through approved purchasing-organization and supplier schema groups.
Prove condition-record access, validity, scales, pricing date, currency, price unit, tax, freight, info-record and contract precedence, last-PO fallback, and manual conditions through condition analysis.

RUNME57 source assignment and ME21N with requisition reference

EXPECTED PROOF

The intended valid source is proposed for an explainable reason and the PO references the approved demand and commercial source.

If it fails, check here first

No source found: inspect material, plant, date, source-list requirement, validity, purchasing organization, agreement item, and supplier block.
Wrong source selected: inspect fixed-source flags, quotas, agreement validity, info-record organization/plant level, and MRP settings.
Price differs: identify whether it came from contract, info record, last PO, or manual condition and inspect the schema analysis.

Release-sensitive: Purchasing condition technique is stable in concept, but transaction availability, condition storage, Fiori alternatives, and S/4HANA data-model details vary. Use condition analysis and target-release product assistance rather than inferring the result from a table alone.

CONFIGURATION WORKBENCH

Configure and approve the purchase order

The requisition converts into a controlled PO with correct document behavior, terms, tolerances, approval, and supplier output.

SPRO / IMG path

Materials Management → Purchasing → Purchase Order → Define Document Types

Materials Management → Purchasing → Purchase Order → Define Screen Layout at Document Level

Materials Management → Purchasing → Purchase Order → Set Tolerance Limits for Price Variance

Cross-Application Components → Output Control or Materials Management → Purchasing → Messages, according to target output design

Materials Management → Purchasing → Confirmations → Set Up Confirmation Control

Materials Management → Purchasing → Messages or Cross-Application Components → Output Control → Define the release-appropriate PO output path

Materials Management → Purchasing → Purchase Order → Texts for Header and Item

Transactions and apps

OME9 / OMH6Account-assignment categories / PO number ranges

ME21N / ME22N / ME23NCreate / change / display purchase order

ME29NRelease PO in classic release scenarios

NACE or OPDClassic message control or S/4HANA output parameter determination

SPRO confirmation controlDefine confirmation categories, control keys, sequence, date and quantity relevance

MN04 / NACEClassic purchasing output condition records and message control, only where retained

OPD / Manage Purchase OrdersS/4HANA output parameter determination, preview, and processing evidence

Configuration and evidence objectsT161T163EKKOEKPOEKETEKKNNASTT163ET163DT163LT163GT163LVTNAPRT685BTNATIT161NTNAPN

Maintain in this order

Copy or reuse the standard PO document type and confirm number range, allowed item categories, field selection, partner behavior, and reference requirements.
Maintain stock-material item behavior, delivery and invoice indicators, over/underdelivery tolerances, confirmation control if used, and final indicators.
Configure one release approach with authority thresholds, restart behavior, and controlled changes after approval.
Configure the target output approach, approve the document, issue it to a controlled destination, and retain output status and content evidence.
Define purchasing value-key reminders and confirmation-control behavior for acknowledgements, shipping notifications, inbound deliveries, MRP relevance, automatic delivery or GR, and date/quantity checks only where the business will operate the resulting exceptions.
For output, determine output type, receiver, channel, form or template, language, dispatch time, change output, and application-log ownership; prove that the generated content agrees with the approved PO.

RUNME21N → approval → ME22N messages/output → ME23N history

EXPECTED PROOF

The PO adopts approved demand and source, derives explainable terms, receives the correct authority decision, and produces successful controlled supplier output.

If it fails, check here first

Wrong field or item behavior: inspect document type, item category, account assignment, field-selection keys, and reference document.
Approval missing or repeated: inspect release/workflow choice, conditions, responsibility, value changes, and restart rules.
Output absent: inspect output approach, determination records or parameters, form, channel, recipient, dispatch time, and application log.

Release-sensitive: Flexible workflow versus classic release, and S/4HANA Output Management/OPD versus NACE/MN04 message control, are alternative release-dependent branches. Confirmation control also depends on connected inbound-delivery and supplier-collaboration scope.

CONFIGURATION WORKBENCH

Configure goods receipt and inventory posting

A partial PO receipt posts the intended quantity to stock, updates purchasing history, and records balanced inventory and GR/IR entries.

SPRO / IMG path

Materials Management → Inventory Management and Physical Inventory → Movement Types → Copy, Change Movement Types

Materials Management → Inventory Management and Physical Inventory → Goods Receipt → Set Tolerance Limits

Materials Management → Valuation and Account Assignment → Account Determination → Account Determination Without Wizard → Configure Automatic Postings

Logistics - General → Batch Management or Quality Management integration only where included

Materials Management → Inventory Management and Physical Inventory → Plant Parameters → Automatic storage-location creation and delivery-completed defaults

Materials Management → Inventory Management and Physical Inventory → Movement Types → Field selection, account grouping, reversal, and follow-on behavior

Materials Management → Inventory Management and Physical Inventory → Number Assignment → Material Documents and Reservations

Transactions and apps

MIGOPost, reverse, and inspect goods movement

OMJJInspect movement-type control

OMC0 / OMCQInventory tolerance and message settings

MMBE / MB51Inspect stock / material-document list

OBYCAutomatic account determination

OMB2 / OMB3Automatic storage-location creation controls

OMBZ / OMCDReversal dependency and delivery-completed proposal

OMBA / MMNR / OMBT / OMC2Release-specific material-document, physical-inventory, and reservation number ranges

OMJ1Negative-stock activation only with explicit inventory-policy approval

Configuration and evidence objectsT156T030EKBEMATDOCACDOCAMARDMBEWT156XT156BT159LNRIV

Maintain in this order

Use standard movement 101/102 for the minimum spine unless a proven requirement justifies a copied movement type.
Confirm PO goods-receipt relevance, delivery tolerances, stock type, storage location, posting date, valuation, and delivery-completion behavior.
Validate valuation grouping, valuation class, transaction keys, account modifiers, GR/IR, inventory, and price-difference account determination for the observed posting.
Post nine of ten units, inspect material and accounting documents, reverse in a controlled test, and prove that PO history and stock return consistently.
Review movement-type quantity/value updates, posting string, account grouping or modifier, field selection, allowed transactions, reversal movement, reason controls, batch and shelf-life checks, and account-key assignment before copying or changing a movement type.
Keep automatic storage-location creation, negative stock, PO creation at GR, cancellation after invoice, and delivery-completed proposals disabled unless a controlled business case and negative testing justify them.

RUNMIGO 101 for partial quantity → ME23N history → MMBE → material document → FB03

EXPECTED PROOF

Stock increases by the received quantity, the remaining PO quantity stays open, MATDOC records the movement, and ACDOCA balances inventory debit with GR/IR credit.

If it fails, check here first

PO item unavailable: inspect open quantity, GR indicator, delivery-completion status, deletion/block, plant, and user authorization.
Quantity or stock error: inspect unit conversion, tolerance, storage location, batch/serial, stock type, and physical date.
Account error: inspect valuation area, valuation class, price control, transaction key/account modifier, OBYC, G/L extension, and posting period.

Release-sensitive: Movement-type settings have broad cross-process impact. Transaction names in historical inventories can overlap or differ by release; use OMJJ and the installed IMG as the primary navigation. Batch management is optional and requires its own approved activation design.

CONFIGURATION WORKBENCH

Configure invoice verification and blocking

The supplier invoice matches the PO and receipt, creates a traceable liability, and blocks material variances using the designed tolerances.

SPRO / IMG path

Materials Management → Logistics Invoice Verification → Incoming Invoice → Set Tolerance Limits

Materials Management → Logistics Invoice Verification → Incoming Invoice → Configure How Unplanned Delivery Costs Are Posted

Materials Management → Logistics Invoice Verification → Invoice Block → Stochastic Block / Automatic Release, where approved

Financial Accounting → Accounts Receivable and Accounts Payable → Business Transactions → Incoming Invoices/Credit Memos

Materials Management → Logistics Invoice Verification → Incoming Invoice → Vendor, tax, duplicate, exchange-rate, and unplanned-delivery-cost controls

Materials Management → Logistics Invoice Verification → Incoming Invoice → Number Assignment

Transactions and apps

OMR6Maintain invoice tolerance limits

MIRO / MIR4Post / display supplier invoice

MRBRRelease blocked invoices

MR11Maintain GR/IR clearing account where appropriate

FBL1NInspect supplier open items

OMRDCDefine duplicate-invoice check key fields

OMRX / OMR2Supplier tolerance and company-code invoice defaults

OMRW / V_169P_BExchange-rate differences and unplanned delivery-cost treatment; use supported IMG access

OMRMConfigure release-specific invoice messages such as supplier consistency checks

Configuration and evidence objectsT169GRBKPRSEGEKBEBKPFACDOCABSEGT169PT169LT169VT001CNRIV

Maintain in this order

Confirm PO-based or GR-based verification, expected receipt behavior, tax treatment, planned/unplanned delivery cost policy, and invoice-before-receipt policy.
Maintain company-code tolerance keys and limits using approved business thresholds; record whether each variance warns, blocks, or prevents posting.
Configure duplicate reference checks, payment-block behavior, release authority, and any automatic release only when its evidence is understood.
Post a matching nine-unit invoice and a controlled ten-unit variance; prove the match basis, block, FI document, supplier item, and GR/IR result.
Define whether supplier consistency, duplicate references, tax defaults, exchange-rate differences, planned and unplanned delivery costs, and quantity/price variances block, warn, post, or require review.
Prove invoice-number assignment, fiscal-year handling, parked versus posted behavior, blocked-invoice release authority, credit and subsequent debit/credit handling, and reversal evidence.

RUNMIRO with PO reference → MIR4 → ME23N history → FB03/FBL1N → MRBR where authorized

EXPECTED PROOF

A matching invoice posts without unexplained block; a quantity or price variance shows the designed tolerance result, liability, payment status, and controlled resolution path.

If it fails, check here first

Unexpected balance: inspect PO price unit, order unit conversion, receipt quantity, prior invoices/credits, delivery costs, tax, and exchange rate.
No block or wrong block: inspect company-code tolerance key, absolute/percentage limits, item comparison, and payment-block configuration.
GR/IR remains unexplained: reconcile PO history by quantity/value, reversals, final indicators, price differences, and the actual FI references.

Release-sensitive: Invoice messages and direct view names can differ by release. Maintain supported IMG activities rather than direct tables. A tolerance that permits posting does not necessarily permit payment; preserve the distinction between liability recognition and payment release.

CONFIGURATION WORKBENCH

Configure supplier payment and bank selection

A due, unblocked supplier item enters a controlled payment proposal, derives the intended bank and method, posts, produces test media, and clears.

SPRO / IMG path

Financial Accounting → Accounts Receivable and Accounts Payable → Business Transactions → Outgoing Payments → Automatic Outgoing Payments

Financial Supply Chain Management → Cash and Liquidity Management → Bank Account Management, according to target scope

Financial Accounting → Bank Accounting → Business Transactions → Payment Transactions → Electronic Bank Statement

Cross-Application Components → Payment Medium Workbench, where used

Transactions and apps

FBZPConfigure paying company codes, payment methods, house banks, and ranking

F110Automatic payment proposal and run

FI12_HBANKMaintain/display house bank and account data where available

FBL1N / FB03Inspect supplier items and payment document

OT83 / FEBANBank-statement rules / postprocess statement items where applicable

Configuration and evidence objectsT042AT042ET042GT012T012KREGUHREGUPPAYRACDOCA

Maintain in this order

Define permitted supplier payment methods, company-code amount and form rules, currencies, required master data, and payment-block behavior.
Maintain paying company code, house banks/accounts, ranking, available amounts, value dates, and a safe test payment-media route.
Confirm supplier payment terms, method, bank data, due date, and unblocked status; separate configuration proof from production banking authorization.
Run a proposal, review inclusions and exclusions, approve the controlled test run, inspect payment/clearing documents and media status, and reconcile the clearing account.

RUNF110 proposal → proposal log → controlled payment run → FBL1N/FB03 → test media and clearing review

EXPECTED PROOF

Only the eligible item is selected, exclusions are explained, bank and method derive correctly, approval is evidenced, the supplier item clears, and bank clearing remains reconcilable.

If it fails, check here first

Item not selected: inspect due date, payment block, method, currency, minimum amount, special G/L, supplier data, and competing run.
No bank or method: inspect FBZP company/country rules, supplier instruction, house-bank ranking, available amount, account currency, and value date.
Posted but not reconciled: inspect payment-media status, bank acknowledgement, clearing account, statement rule, rejected payment, and reversal.

Release-sensitive: Payment approval, bank account management, payment formats, and bank communication differ by edition and activated scope. Never use production credentials or live bank transmission as training proof.

CONFIGURATION WORKBENCH

Connect purchasing history, GR/IR, and clearing

The complete document chain reconciles ordered, received, invoiced, and paid quantities and values with the universal journal.

SPRO / IMG path

Materials Management → Purchasing → Reporting and Analytics

Materials Management → Valuation and Account Assignment → Account Determination

Financial Accounting → General Ledger Accounting → Business Transactions → Open Item Clearing

Financial Accounting → Accounts Receivable and Accounts Payable → Supplier Accounts → Line Items

Materials Management → Valuation and Account Assignment → Account Determination → Verify WRX, BSX, GBB, PRD, KDM, and valuation grouping

Controlling → Product Cost Controlling → Actual Costing/Material Ledger → Basic Settings and Actual Costing, according to approved scope

Transactions and apps

ME23NRead PO history and statuses

MB51 / MMBETrace material documents and stock

MIR4 / FBL1NTrace invoice and supplier open items

MR11Analyze and maintain GR/IR differences under governed policy

FB03 / FAGLL03HTrace accounting documents and G/L line items

OBYC / OMWNTrace transaction keys, valuation grouping, movement account modifiers, and automatic accounts

OMSY / OMX1 / OMX2 / OMX3Inspect MM period and Material Ledger type, activation, and valuation-area assignment

FCML4H_STARTUP or release-specific startupMaterial Ledger productive startup only under an approved irreversible procedure

Configuration and evidence objectsEBANEKKOEKPOEKBEMATDOCRBKPRSEGBKPFACDOCAREGUHREGUPT030T001KT156XCKMLHDMLDOC

Maintain in this order

Define the reconciliation checkpoints and owners for open requisitions, commitments, overdue receipts, invoice blocks, aged GR/IR, due supplier items, and bank clearing.
Record the status and document references expected after every event, including partial receipt, invoice variance, reversal, credit, and final indicators.
Build operational evidence from standard document history and accounting references before introducing custom reporting.
Run the minimum transaction twice—one clean and one controlled exception—and prove both the happy path and the recovery path.
For every tested movement and invoice, identify the transaction key and account modifier, valuation class and grouping, resulting G/L account, currency, price difference, and reversal path.
Confirm mandatory Material Ledger currency and valuation settings for each valuation area. Treat actual costing and productive startup as a separate Finance/Controlling workstream with reconciliation, cutover, close, and rollback constraints.

RUNPR → PO → partial GR → matching invoice → payment; reconcile ME23N, MATDOC, MIR4, FBL1N, and ACDOCA

EXPECTED PROOF

Ordered, received, invoiced, open, and paid quantities and values agree; inventory, GR/IR, supplier liability, tax, and bank clearing are balanced and traceable.

If it fails, check here first

Document chain disagrees: align item references, units, currencies, reversals, cancellations, subsequent debits/credits, and final indicators.
Operational history agrees but FI does not: inspect valuation, tax, exchange rate, price differences, account determination, and document references.
Old exception has no owner: classify whether Requesting, Purchasing, Warehouse, AP, Treasury, Tax, or Finance owns the next business decision.

Release-sensitive: Material Ledger is mandatory in SAP S/4HANA; actual costing is optional. Productive startup can be irreversible and requires a verified recovery and cutover plan. Historical CKMSTART references must be reconciled to the supported startup procedure for the installed release.

GATED EXTENSIONS

Keep advanced MM branches visible without weakening the golden path

Configure these only after the stocked-material spine posts and reconciles. Each branch changes physical ownership, valuation, traceability, or close responsibility.

STOCK TRANSPORT

STO and stock in transit

Configure supplying/receiving plants, STO document and item behavior, shipping data, delivery/checking rules, one-step or two-step movement, confirmation control, valuation, and company-code clearing.

Open extension →SUBCONTRACTING

Components provided to supplier

Control special procurement, subcontracting item behavior, component list and supplier stock, consumption, subsequent adjustment, receipt, invoice, and price differences.

Open extension →RETURNS

Supplier return and commercial correction

Connect return indicator, movement, delivery, replacement or credit, invoice history, reason, output, and remaining exposure.

Open extension →BATCH

Lot identity and selection

Choose batch level, status, number assignment, classification, shelf life, determination strategy, where-used evidence, and cross-application ownership.

Open extension →MATERIAL LEDGER

Mandatory value foundation; optional actual costing

Align ledger type, currencies, valuation areas, productive startup, periods and reconciliation; activate actual costing only as a governed extension.

Open extension →

Full source inventory: Use the normalized MM configuration register to locate all supplied transactions, IMG topics, tables, and release-sensitive references.

TRANSACTIONAL PROOF

One purchase, one reconciled liability and payment

Settings are not evidence. Run the complete chain and reconcile every successor.

Controlled test data

Supplier BP extended to company code and purchasing organization with reconciliation account, payment terms/method, tax, controlled bank data, and no unexplained block
Stock material extended to purchasing, plant, storage, and accounting views with known valuation class, price control, order unit, and no opening stock dependency
Valid source and price, open posting periods, intended inventory/GR-IR/supplier/bank accounts, approved test users, and a non-production payment-media route

01
ME51N and approval
Ten motors, required date, plant, purchasing responsibility, authority, and source readiness are complete and traceable.
02
ME21N and PO approval/output
The PO references approved demand and source; price, terms, tolerances, authority, and supplier communication are explainable.
03
MIGO receipt of nine
Nine units enter stock, one remains open, PO history updates, and inventory debit balances GR/IR credit.
04
MIRO invoice for nine
The invoice matches PO and receipt, clears the received GR/IR value, creates tax and supplier liability, and remains eligible for payment.
05
Controlled MIRO variance for ten
The extra quantity produces the designed tolerance or block and has a governed resolution rather than a weakened control.
06
F110 controlled payment and clearing
The eligible supplier item is selected, approved, posted through the intended bank channel, cleared, and reconciled.

TECHNICAL REFERENCES

Verify against the target release

These SAP product-assistance pages anchor the configuration concepts. The IMG and activated scope in the target system remain authoritative.

READY FOR THE PROJECT?Continue to P2P 505

Apply the workbench inside workshops, testing cycles, cutover decisions, defects, payment controls, and stabilization.

Enter the live project →