S/4HANA Purchasing Configuration: Release Strategy, Info Records, Source List, Quota, Contracts & ERS – Full Hands‑On Guide | Part 21 | FreeLearning365

 

Day 6 – Purchasing Configuration: Release Strategy, Info Records, Source Determination & ERS

Functional Consultant Track – Part 21

Welcome to Day 6 of your S/4HANA functional consultant journey. Yesterday you laid the MM foundation – enterprise structure, plants, storage locations, material types, movement types, and the legendary OBYC account determination. Today we climb higher into the strategic purchasing cockpit. This is where procurement governance becomes tangible: who can approve what, how do we lock in prices with vendors, how do we split business between suppliers, and how do we eliminate manual invoice processing. If Day 5 was about making sure goods movements post correctly, Day 6 is about making sure they happen with the right supplier, at the right price, under the right approvals, and with zero avoidable manual work.

Our client GlobalTech is growing fast and procurement is becoming chaotic. The CFO demands: (1) all purchase orders above $50,000 require a two‑level approval, (2) critical raw materials must come only from approved vendors on a source list, (3) packaging material demand should be split 60/40 between two strategic suppliers, (4) blanket contracts for steel must be in place to lock prices for the year, and (5) for frequent, planned deliveries, the system should automatically create the invoice upon goods receipt so no AP clerk ever touches it. Your job: configure all of this using SAP’s classic purchasing tools, explain the classification‑based release strategy, the difference between source list and quota, and the mechanics of Evaluated Receipt Settlement. By the end of this 20,000‑word hands‑on guide, you’ll have built a fully governed procurement environment.

1. Release Strategy with Classification – Approval Workflows That Work

Release strategy is the process of requiring approval (release) before a purchase requisition (PR) or purchase order (PO) can be converted or sent to the vendor. SAP delivers two main methods: (a) classification‑based release (standard, flexible, widely used) and (b) workflow‑based release via SAP Business Workflow. The classification approach is still king in many implementations because it’s configuration‑driven, not development‑heavy, and can be set up entirely in SPRO without ABAP coding.

1.1 The Classification Concept – Characteristics, Classes, and Release Conditions

You create characteristics (e.g., “PO value”, “Purchasing Group”) and combine them into a class. When a PR or PO is saved, the system evaluates the values of those fields against the class’s criteria. If the document falls into a release‑relevant combination, it is blocked and must be released step‑by‑step according to the release strategy defined in the class. The release strategy consists of release groups, release codes, and a release indicator.

Let’s build GlobalTech’s PO release strategy:

• Requirement: Purchase orders over 50,000 USD must be approved by the Purchasing Manager (release code M1), then by the CFO (release code M2).
• Requirement: Any PO for purchasing group PG1 (raw materials) over 20,000 USD needs the raw materials team lead (release code M3) first.

1.2 Step‑by‑Step Configuration

SPRO path: Materials Management → Purchasing → Purchase Order → Release Procedure for Purchase Orders → Define Release Procedure for Purchase Orders (transaction SPRO, or directly OLME → IMG structure). We'll work through the wizard‑like SPRO steps.

1.2.1 Define Characteristics (CT04)

Transaction CT04 (Characteristics). Create:

• ZPO_VALUE – PO Net Order Value. Data type: Currency, currency field: WAERS (document currency). Assign to table CEKKO (field GNETW) so that it reads the PO net value.
• ZPO_PG – Purchasing Group. Data type: CHAR 3, table CEKKO, field EKGRP.

We also need a characteristic for document type? Not necessary – we can filter by class assignment. But for completeness, we could add ZPO_DOC_TYPE if needed.

1.2.2 Define Class (CL02)

Transaction CL02. Create class ZPO_RELEASE of class type 032 (for purchasing). Assign characteristics ZPO_VALUE and ZPO_PG. In the class, the “Status” must be released.

1.2.3 Define Release Group

SPRO: Release Procedure for Purchase Orders → Define Release Group. Create release group Z1 (PO Standard Release). Assign class ZPO_RELEASE to it. This links the classification to the release procedure.

1.2.4 Define Release Codes

Release codes are the approval steps. Create:

• M1 – Purchasing Manager, responsible for first level.
• M2 – CFO, final release.
• M3 – Raw Materials Lead.

For each, you can assign a user ID or a job (via workflow). In classification, it’s often user‑based. For our example, assign your own user to all codes for testing, or create test users.

1.2.5 Define Release Indicators

Indicators show whether a document is blocked (A), released (B), etc. Standard ones: 1 (blocked), 2 (released). We’ll use standard.

1.2.6 Define Release Strategy

Create strategy ZPO_STRAT within release group Z1. Set:

• Release conditions: specify which combination of characteristics triggers the strategy. Click on “Classification” and enter the selection: ZPO_VALUE >= 50000 USD AND ZPO_PG = (any) – but we want two strategies, one for general high value, one for PG1 > 20k. So we define two strategies: ZPO_STRAT1 for general high value >50k, ZPO_STRAT2 for PG1 >20k.

For ZPO_STRAT1, set condition: ZPO_VALUE >= 50,000. For ZPO_STRAT2, condition: ZPO_PG = 'PG1' AND ZPO_VALUE >= 20,000.

After defining the strategies, assign the release codes in sequence. For ZPO_STRAT1:

• Release step 1: code M1 (Purchasing Manager)
• Release step 2: code M2 (CFO)

For ZPO_STRAT2:

• Release step 1: code M3 (Raw Materials Lead)
• Release step 2: code M1 (Purchasing Manager)

Set release prerequisites: step 2 requires step 1 completed. Also set “workflow” flag if desired, but for manual release we skip.

1.2.7 Activate and Test

Create a purchase order (ME21N) for 60,000 USD for any material. Save. The system automatically applies strategy ZPO_STRAT1 and blocks the PO (release indicator 1). A message “Release required” appears. Use transaction ME28 (Release Purchase Order) to view blocked POs. Select the PO, click “Release”. The screen shows the release steps; you can release step by step as the assigned users. Once fully released, the PO can be outputted.

Test a PO for 25,000 USD with purchasing group PG1. The PO gets ZPO_STRAT2 – first release M3, then M1. Works perfectly. This is pure classification magic – no ABAP, fully configurable.

Insight: Classification release strategies can also use fields like material group, vendor, plant. In S/4HANA, you can still use this method, but many customers are moving to Flexible Workflow (SAP S/4HANA for Procurement) which is Fiori‑driven. However, classic classification is still widely supported and tested.

2. Purchasing Info Records – The Memory of Prices and Conditions

An info record is a master data link between a material and a vendor. It stores the last purchase order price, the order unit, the planned delivery time, and any conditions (e.g., discounts, surcharges). When you create a purchase order for that material‑vendor combination, the system automatically copies the price and conditions from the info record, saving time and ensuring pricing consistency.

2.1 Info Record Types

Standard info record (purchasing organization data), pipeline info record, consignment, subcontracting. GlobalTech will use standard info records for all regular raw materials and trading goods.

2.2 Create Info Record (ME11)

Transaction ME11. Enter vendor “USSUP01”, material “RAW01”, purchasing organization PU01, plant GT01. The info record category is “Standard”.

Enter data:

• General data: vendor material number (if any), quality score.
• Purchasing organization data: planned delivery time 5 days, purchasing group PG1, order unit KG (same as material base unit).
• Conditions: gross price 9.80 USD per KG (standard price), with a freight condition 0.20 USD per KG (so total 10.00 USD). The net price is calculated. Also add a discount condition “SKTO” 2% for payment within 10 days.

Save. The info record number is generated. Now create a purchase order (ME21N) for RAW01 with vendor USSUP01. As soon as you enter vendor and material, the price 9.80 USD appears, and the freight and discount conditions are automatically proposed. The PO net price becomes 9.80 – 0.196 (2% discount) + 0.20 freight = 9.804. This demonstrates the power of info records – they drive accurate purchase pricing.

2.3 Info Record Price History

If you update the info record with a new price (ME12), the old price is retained in the “Price History” tab. For auditors, this is gold – they can see all price changes over time. To view the history, use ME13 (display info record) and click the “Conditions” history button. This ensures transparency in procurement.

Best Practice: Always create info records for regular suppliers and materials. It prevents buyers from manually entering wrong prices and speeds up PO creation. Also, use the “Automatic PO” flag in the info record to allow ERS (more later).

3. Source List and Quota Arrangement – Controlling the Supply Base

When multiple vendors can supply a material, you need to control which ones are authorised (source list) and in what proportion (quota arrangement). Source list is a mandatory requirement for many industries (e.g., automotive) and ensures procurement compliance.

3.1 Source List (ME01 / ME05)

Transaction ME01 (Maintain Source List). For material “PACK01” (packaging material), plant GT01, we define:

• Vendor VEND1, valid from today to 31.12.2025, source list record number 1. Fixed source indicator: yes (meaning MRP will only use this source if no quota).
• Vendor VEND2, also valid, record 2.

In the source list, you can also set the “MRP relevant” flag, which tells the material requirements planning run to consider these vendors for automatic purchase requisition creation. If a source list exists and MRP is run, the system will only create procurement proposals for sources in the list. This is crucial: without a source list entry, the material cannot be procured automatically.

To view the source list, use ME03 (display). You can also maintain sources for specific periods, allowing vendor rotation.

3.2 Quota Arrangement (MEQ1)

Quota arrangement divides the total procurement quantity among multiple sources over a period. It’s like a “split”. GlobalTech wants 60% of packaging from VEND1 and 40% from VEND2.

Transaction MEQ1. Enter material PACK01, plant GT01. Create quota:

• Vendor VEND1, quota 60, minimum quantity 100, maximum quantity 500,000 (optional).
• Vendor VEND2, quota 40, same min/max.

The quota rating is calculated as (allocated quantity + quota base quantity) / quota. When MRP runs, it checks the current quota rating for each vendor and assigns the next purchase requisition to the vendor with the lowest quota rating, thus maintaining the split. For a demand of 1,000 units, the system will create a PR for 600 to VEND1 and 400 to VEND2, provided the lot sizes match. If a minimum lot size is set, the split may vary.

Test this: set up a material, assign quota, then run MRP (MD02). You’ll see purchase requisitions generated for each vendor according to the quota. The source list must also exist for the vendors.

Important: The source list and quota arrangement are independent but complementary. Source list says “who is allowed”, quota says “how much to each”. If a vendor is not in the source list but in the quota, MRP might still generate a PR? No, MRP checks source list first (if flagged as mandatory). So both must be consistent.

4. Outline Agreements – Contracts and Scheduling Agreements

Outline agreements are long‑term purchasing agreements against which you create purchase orders (for contracts) or direct delivery schedules (for scheduling agreements). They lock in terms and conditions, prices, and quantities, providing strategic procurement leverage.

4.1 Contracts (ME31K – Quantity Contract, ME31L – Value Contract)

GlobalTech negotiates a quantity contract for steel coils “STEEL01” with vendor STEELSUP: 1,000 tons over one year at a fixed price. Use transaction ME31K (create quantity contract). Enter:

• Agreement type: MK (quantity contract).
• Vendor, purchasing organization, plant.
• Validity period: 01.01.2025 – 31.12.2025.
• Target quantity: 1,000 tons (unit T).
• Price: 800 USD per ton (in conditions).

Now, whenever the buyer needs steel, they create a release order (a normal PO) with reference to the contract via ME21N, using “Create with reference” and entering the contract number. The system copies the price and updates the released quantity. The buyer cannot order more than the contract’s target quantity (unless overdelivery tolerance is configured).

Value contract (ME31L) works similarly but uses a total value limit (e.g., 500,000 USD). This is useful for services or maintenance procurement where quantities are difficult to define.

4.2 Scheduling Agreements (ME31L with LP Type)

A scheduling agreement is like a contract but with predefined delivery dates and quantities. It’s used when you have steady demand, e.g., daily deliveries. GlobalTech uses a scheduling agreement for packaging materials with vendor VEND1: 100 units every Monday.

Transaction ME31L (Create Scheduling Agreement). Choose agreement type “LP”. Enter vendor, material, plant. Then create a delivery schedule via ME38 (Maintain Delivery Schedule) or directly in the agreement. Enter dates and quantities (e.g., every Monday, 100 units). When the goods arrive, the vendor sends an ASN (advanced shipping notification) or you post a goods receipt directly referencing the scheduling agreement. No purchase order is needed – the scheduling agreement is the call‑off document.

In S/4HANA, scheduling agreements can be integrated with supplier collaboration via Supply Chain Collaboration or Ariba Network, but the backend configuration remains the same.

4.3 Outline Agreement Release and Monitoring

You can monitor released vs target quantities in ME33K (display contract) or ME33L (scheduling agreement). The system shows a consumption bar. When the contract nears expiry or the quantity is close to target, the buyer can negotiate an extension.

Best Practice: Use contracts for high‑value, infrequent purchases; use scheduling agreements for repetitive, just‑in‑time deliveries. Never mix them up – using a scheduling agreement for a one‑time buy complicates the process.

5. Evaluated Receipt Settlement (ERS) – Invoices Without Paper

ERS is SAP’s method of automatically creating an invoice document upon goods receipt, without waiting for the vendor to send a paper invoice. It’s the enabler of true touchless procure‑to‑pay. The system uses the purchase order and goods receipt data to calculate the invoice amount and generates it in the background.

5.1 How ERS Works

ERS works only for purchase orders where the goods receipt has been posted and the invoice is expected to match exactly the PO price. No price or quantity variances are automatically handled. The invoice is generated with reference to the goods receipt, and it posts as an FI document clearing the GR/IR account and crediting the vendor. No manual MIRO is required.

5.2 Prerequisites and Configuration

Step 1: In the vendor master (transaction MK02), under “Purchasing data” → “Control data”, check the box “ERS vendor”. Also, the vendor must have a complete bank master for payment (but that’s F110).

Step 2: In the purchasing info record (ME12) or the purchase order itself, the “ERS” flag must be set (field “Automatic evaluation” on the delivery tab). In the info record, you can mark it as default.

Step 3: The purchase order must have “Goods receipt‑based invoice verification” (GR‑based IV) set. Actually, ERS automatically uses the GR quantity as the invoice quantity, so GR‑based IV is inherent. But to block manual invoices before goods receipt, you must set the “GR‑Based IV” flag in the vendor master or PO. We’ll cover that next.

Step 4: Run the ERS program: transaction MRKO (Automatic Settlement) or MIR4 for single documents. Usually, MRKO is scheduled in background. It selects all open goods receipt items for ERS‑relevant PO/vendors and creates the invoice documents.

5.3 Hands‑On ERS Test

Set up vendor “AUTO_VEND” as ERS vendor. Create PO for 100 units of RAW01 at 10 USD. Post goods receipt for 100 units in MIGO. Then run MRKO. The system creates an invoice document; check in MIR4 (display invoice) – it’s posted, GR/IR cleared, vendor credited. The FI entry: debit GR/IR 30000100, credit vendor 30000010. No manual intervention.

Exception: If the invoice price should differ from the PO price, ERS cannot handle it. You’d have to manually process the invoice in MIRO. That’s why ERS is used for long‑term, stable pricing arrangements – exactly the contracts and scheduling agreements we configured.

6. Goods Receipt‑Based Invoice Verification Toggle – Control the Cash Outflow

GR‑based invoice verification ensures that an invoice cannot be posted unless the corresponding goods have been received. This prevents paying for undelivered goods. It’s a simple but powerful control.

6.1 Setting GR‑Based IV

It can be set at multiple levels:

• In the vendor master (MK02, purchasing data): check “GR‑Based IV” – applies to all POs for that vendor.
• In the purchase order (ME21N, item detail, Invoice tab): “GR‑Based IV” checkbox. This overrides the vendor setting.
• In the info record: used as default for POs.

GlobalTech sets GR‑Based IV for all foreign vendors to reduce risk. So vendor FORSUP02 (Germany) has the flag in the vendor master. If someone tries to post an invoice (MIRO) for a PO before goods receipt, the system throws error “GR‑based IV: Goods receipt required”. Once MIGO is posted, the invoice can be entered.

6.2 Interaction with ERS

ERS inherently respects GR‑based IV because it only creates invoices for goods receipt lines that are not yet invoiced. So if GR‑based IV is active, ERS works perfectly – it generates the invoice only after GR.

7. Real‑World Scenario – A Full Procurement Cycle with Governance

Let’s simulate a day in GlobalTech’s procurement team to see all the configuration pieces clicking together.

Morning: The production planner creates a purchase requisition (PR) for 200 KG of RAW01 (net value 2,000 USD). Because the value is under 20,000, no release strategy is triggered. The buyer converts the PR to a PO in ME21N. The PO automatically populates price 9.80 USD from the info record with vendor USSUP01.

Mid‑day: The plant manager urgently needs a special machine part from a new vendor. They create a PR for 55,000 USD. Upon saving, classification triggers release strategy ZPO_STRAT1: blocked. The purchasing manager (M1) reviews and releases using ME28. Then the CFO (M2) releases. The PO is now ready for output.

Afternoon: The packaging buyer runs MRP for PACK01. The system generates two PRs: one for VEND1 (600 units) and one for VEND2 (400 units) based on the quota arrangement. The buyer converts both to POs. Goods receipt is posted for VEND1’s shipment, and because VEND1 is set as ERS, the system automatically creates an invoice via MRKO at midnight. No AP clerk touches it.

End of month: The contract for steel has 200 tons released; the buyer checks ME33K to see remaining target. The scheduling agreement with VEND1 for packaging is updated for the next month’s delivery schedule via ME38. Everything is under control, auditable, and efficient.

8. Best Practices, Pitfalls, and Alternatives

Best Practices:

• Keep release strategies simple. Start with a maximum of 2‑3 levels. Overly complex strategies lead to approval bottlenecks and users bypassing them by splitting POs.
• Always maintain info records for regular suppliers. They serve as a price audit trail and are a prerequisite for ERS and effective source list control.
• Use source list as a mandatory control to prevent maverick buying. In the material master (MRP view) or in the plant parameters, you can set “Source list required”. This forces MRP to only create procurement proposals for sources in the list.
• Quota arrangements require careful monitoring. A vendor with a high quota but poor delivery performance can still get orders; consider combining with “maximum value” or vendor evaluation to temporarily block them.
• For ERS, run MRKO daily as a background job but include a test mode variant first to alert the AP team of any pricing mismatches before live posting.
• Never set GR‑based IV on all vendors blindly. Some service vendors deliver no physical goods; you must be able to invoice based on contract or time sheet. Use it only for physical goods with clear receipt.

Common Pitfalls:

• Release strategy conditions defined incorrectly: using ‘>’ instead of ‘>=’ might leave exact boundary values unreleased. Always test boundary cases.
• Info record prices expire (validity dates). If a PO is created after the info record validity end, the system doesn’t pull the price – buyer gets a warning and must enter manually. Maintain info record validity aligned with contract periods.
• Source list and quota arrangement are not automatically synced. If you add a new vendor to the quota but forget to add to the source list, MRP will ignore the quota and may not generate proposals. Use ME05 to generate source list entries from quota?
• ERS without proper tolerance configuration can create incorrect invoices. Always set invoice value tolerance in the vendor master or via OMIS so that small variations block the automatic invoice.

Alternatives:

• Instead of classic classification release, you can use SAP Business Workflow with custom rules – it’s more flexible but requires ABAP knowledge and workflow admin.
• For strategic sourcing and auctions, consider SAP Ariba Sourcing integrated with S/4HANA. Outline agreements can be created from Ariba contracts.
• If ERS is not feasible due to frequent price changes, use “Invoice Verification in the Background” (transaction MIR7) or a third‑party OCR solution with automatic PO matching.
• In S/4HANA, Central Procurement Hub allows centralised source list and quota across multiple backend ERP systems, which is beyond our scope but good to know.

9. Conclusion – Procurement Governance Mastered

Day 6 has transformed you into a purchasing configuration expert. You can now design and implement classification‑based release strategies that enforce company policies, build rich info records that drive accurate pricing, lock down the supply base with source lists and quota arrangements, create outline agreements that secure long‑term vendor relationships, and automate invoice processing with ERS and GR‑based IV controls. This is the configuration that separates a transactional buyer from a strategic procurement consultant.

Tomorrow, on Day 7 (Part 22), we move deeper into inventory management and valuation – split valuation, price control (standard vs moving average), GR/IR clearing management, consignment, subcontracting, and warehouse management basics. You’ll learn how to value inventory differently for different purposes and handle complex special stocks. The MM saga continues – don’t miss it.

@FreeLearning365 – Tech Partner @techbook24