When a company shifts from ad hoc, one off buying to strategic, long term procurement, they need binding frameworks with their suppliers. In SAP MM, these long term purchasing arrangements are known as Outline Agreements. They act as the master negotiation documents that define prices, conditions, and overarching rules for a specific material or service over a set period. SAP provides two distinct types of Outline Agreements: the Purchase Contract and the Scheduling Agreement. Understanding the fundamental differences between the two, and precisely when to use which, is a critical skill for any SAP functional consultant configuring source determination in S/4HANA.
What is a Purchase Contract?
A Purchase Contract is a long term agreement with a vendor to supply materials or provide services. The contract establishes the agreed upon price, conditions, and validity period, but crucially, it does not specify exact delivery dates or individual order quantities immediately. It is an umbrella agreement.
Types of Purchase Contracts
SAP MM standard functionality supports two primary variations of standard contracts. Create contracts using ME31K and maintain them with ME32K.
- Value Contracts (WK): A Value Contract is negotiated based on the total monetary amount. For example, your company agrees to purchase 500,000 dollars worth of office supplies from a vendor over the next two years. The exact quantity of individual pens, paper, or chairs doesn't matter, as long as the total value drawn against the contract does not exceed the agreed limit.
- Quantity Contracts (MK): A Quantity Contract is negotiated based on the total number of units. For example, your company agrees to buy 10,000 tons of raw steel from a supplier over the next 12 months. The total monetary value fluctuates based on the negotiated standard price, but the contract is fulfilled once the 10k tons are consumed.
How Contracts are Executed
Because a contract lacks specific delivery dates, it requires a secondary document to trigger a physical shipment. This is called a Release Order. A Release Order is essentially a standard Purchase Order (PO) created with reference to the existing contract. When the PO references the contract, the system automatically pulls the negotiated price and conditions from the parent document and updates the contract's "Release Documentation" to track how much value or quantity has been consumed.
What is a Scheduling Agreement?
A Scheduling Agreement is also a long term outline agreement with a vendor. However, unlike a contract, a Scheduling Agreement is specifically designed for highly repetitive, predictable manufacturing or consumption environments. It completely eliminates the need to create individual Purchase Orders. Create scheduling agreements using ME31L and maintain them with ME32L.
The Core Mechanism
Instead of issuing a new PO every time you need stock, you create a single Scheduling Agreement document. This document acts as the master record. Then, you generate Delivery Schedules (also called Schedule Lines). These schedules explicitly tell the vendor exactly how many units to deliver on specific dates or times (e.g., Deliver 100 units next Monday, 150 units on Tuesday, 200 units on Wednesday).
These schedule lines can be generated manually by a buyer or, more efficiently, generated automatically by the Material Requirements Planning (MRP) run. When MRP detects a shortage based on the production plan, it instantly creates a new schedule line directly against the Scheduling Agreement, cutting out the PR to PO conversion step entirely.
Types of Scheduling Agreements
There are two primary document types utilized in modern implementations:
- Standard Scheduling Agreement (LP): Used for standard, manual scheduling where schedule lines are created and transmitted to the vendor.
- Scheduling Agreement with Release Documentation (LPA): This is the advanced, vastly superior method utilized in the automotive and high tech industries. The schedule lines generated internally by MRP (or the buyer) are not instantly valid for the vendor. They must be formally "Released" using transaction
ME84to generate Forecast (FRC) or Just In Time (JIT) delivery schedules. This provides crucial control, allowing the buyer to review the MRP output before committing it to the supplier.
Head to Head Comparison
To summarize the technical and procedural differences between the two agreements, refer to the matrix below:
| Feature | Purchase Contract (MK/WK) | Scheduling Agreement (LP/LPA) |
|---|---|---|
| Execution Document | Requires creating separate Release Orders (Purchase Orders) | Never requires POs. Uses Schedule Lines natively |
| MRP Integration | MRP generates Purchase Requisitions, which must be manually or semi automatically converted to POs against the contract | MRP generates Schedule Lines directly against the agreement instantly |
| Goods Receipt Processing | GR is posted against the referenced Release Order (PO number) | GR is posted directly against the Scheduling Agreement document number |
| Ideal Material Types | Non stock items, indirect procurement, services, highly variable usage materials | High volume, highly predictable raw materials, direct manufacturing components, JIT scenarios |
| Database Volume | Higher volume, as every delivery requires a new PO header and line items in the database table EKKO/EKPO | Lower volume, as deliveries simply add lines to existing schedule tables (EKET), saving massive database space |
Contract vs. Scheduling Agreement at a Glance
Purchase Contract
- Created with
ME31K, maintained withME32K - Requires Release Orders (POs) for every delivery
- Best for indirect, variable, or service procurement
- MRP creates Purchase Requisitions that must be converted
- Higher database footprint (EKKO/EKPO tables)
- Two variants: Value Contract (WK) and Quantity Contract (MK)
Scheduling Agreement
- Created with
ME31L, maintained withME32L - No POs needed - deliveries driven by schedule lines
- Best for high-volume, repetitive direct manufacturing
- MRP writes schedule lines directly against the agreement
- Lower database footprint, because no separate PO document is created for each delivery (schedule lines are stored in EKET; the scheduling agreement itself is an EKKO/EKPO document)
- Two variants: Standard (LP) and with Release Docs (LPA)
When to Use Which: Real World Scenarios
The choice between a contract and a scheduling agreement fundamentally dictates how the procurement department operates. A consultant must guide the business to the optimal choice based on their supply chain velocity.
Scenario 1: Office Supplies Procurement
Your company needs printer paper, toner, and basic IT accessories. Demand is erratic and unpredictable across fifty different cost centers. You negotiate a massive discount with a national supplier for a total spend of half a million dollars.
Recommendation: Value Contract (WK). The exact delivery dates and exact quantities of specific items are unknown. Whenever a department needs a new laptop or a box of paper, they create a PR, which the buyer converts into a Release PO against the Value Contract, slowly consuming the total negotiated value.
Scenario 2: Automotive Assembly Plant
An automotive factory produces 1000 cars per day. Each car requires four tires from a specific supplier. The factory floor has zero warehouse space for tires. The tires must arrive at the loading dock precisely 4 hours before they are needed on the assembly line.
Recommendation: Scheduling Agreement with Release Docs (LPA). Creating four thousand Purchase Orders a day would crash the system and bury the buyers in administrative paperwork. Instead, the MRP run evaluates the daily production schedule, generates schedule lines for the exact number of tires needed down to the hour, and automatically transmits a JIT release to the supplier guaranteeing the delivery timeline.
Scenario 3: Strategic Raw Material Sourcing
A chemical plant secures an agreement to buy 50,000 liters of a base chemical over the year to lock in a volatile market price. They have massive storage silos, so precise delivery times matter less than securing the total volume.
Recommendation: Quantity Contract (MK). The procurement team can issue Release Orders (POs) in large, bulk shipments whenever silo capacity opens up, gradually consuming the 50,000 liter limit while benefiting from the locked in price condition.
S/4HANA Modernizations
While the fundamental logic behind these two documents remains unchanged from the ECC era, SAP S/4HANA has drastically improved the user experience. The introduction of specific SAP Fiori apps like Manage Purchase Contracts and Manage Scheduling Agreements provides embedded analytics. Buyers can now visually see contract consumption graphs on their dashboards in real time, alerting them when a quantity contract is nearing 90% completion so they can proactively renegotiate the agreement before operations halt.
Key Takeaway
Use a Purchase Contract when demand is variable, deliveries are irregular, or the procurement covers services and indirect materials. Use a Scheduling Agreement when demand is repetitive and predictable, and eliminating the PO creation step will reduce administrative overhead. Understanding these two foundational documents allows an SAP professional to design an elegant, efficient source determination matrix that accelerates procurement velocity while minimizing administrative overhead.
