# SAP MM Contract T-Codes: ME31K, ME32K, ME33K and Release Orders > Source: https://netray.co/erp-help/sap-mm-contract-tcodes-me31k-me32k-me33k-release-orders > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer In SAP MM a contract is an outline agreement with a vendor. ME31K creates it, ME32K changes it, ME33K displays it. A quantity contract (document type MK) caps total quantity, a value contract (WK) caps total value, and purchase orders created in ME21N reference the contract as release orders against it. ## Kind how-to ## System sap ## Erp SAP ECC / S/4HANA ## Module Materials Management / Purchasing / Outline Agreements ## Query sap mm contract tcode ## Alternate Queries - me31k create contract sap - sap quantity contract vs value contract - sap contract release order me21n - me33k display contract ## Applies To SAP ECC 6.0 and S/4HANA on-premise. Document type keys MK and WK are the SAP standard; your system may add custom types. ## Steps ### How to create a contract in ME31K and release against it **Items:** - Open ME31K. Enter the vendor, the agreement type (MK quantity or WK value), purchasing organization, purchasing group and, if prompted, plant. - Enter the validity start and end dates in the header, plus payment terms and Incoterms. These default into every release order. - Add items. For an MK contract enter material, target quantity, net price and plant. For a WK contract enter the target value for the agreement and item descriptions. - Save. The system issues a contract number from the contract number range. - Release the contract if your system uses a release procedure (ME35K for release of contracts). - Create release orders: in ME21N choose the contract through the Document Overview selection (outline agreements) and adopt the item, or reference it from the contract via the follow-on functions. - Monitor consumption in ME33K (release documentation) or with the contract lists ME3N, ME3M and ME3L. ## Sections ### Quantity versus value contracts **Body:** A quantity contract fixes a total target quantity per material at an agreed price. Each release order consumes part of that quantity, and the system can warn or stop you when releases exceed the target. This fits repeat items such as raw material bought at a negotiated price for a year. A value contract fixes a total monetary amount. It is item-level flexible, since each release order can cover different materials or services, and it suits blanket arrangements, MRO or services. Release orders draw down the value rather than a quantity. ### How contracts connect to POs, sourcing and tables **Body:** Contract headers and items are stored in the same tables as purchase orders: EKKO for the header and EKPO for items, distinguished by document category. The consumption record (release documentation) lives in EKAB. A release order is simply a normal PO whose items carry a reference to the contract. For automatic sourcing, maintain a source list (ME01) and quota arrangements as needed. When the contract is valid and the material has a source list entry, MRP can create purchase requisitions assigned to the contract and ME59N can turn them into release orders automatically. **Code:** - ME31K Create contract - ME32K Change contract - ME33K Display contract - ME35K Release (approve) contract - ME3N Contracts by contract number - ME3M Contracts by material - ME3L Contracts by vendor - ME01 Maintain source list - Tables: EKKO, EKPO, EKAB ### Changes, expiry and closing **Body:** Use ME32K to change prices, validity and target values. Price changes only affect new release orders, not those already issued. If a contract is extended, change the validity end date; an expired contract will not default into new POs. To stop further releases, set the deletion indicator or block the contract through ME32K. Check open release orders in ME2N before closing so you do not orphan commitments. ## Pitfalls - Assuming a contract is a PO: it is not sent to the vendor and does not create commitments until release orders exist. - Letting validity dates lapse, which makes the system ignore the contract during source determination. - Using a quantity contract for services, where a value contract is the right fit. - Changing contract price and expecting open POs to update automatically; they keep the old price. - Skipping the source list, so MRP never assigns requisitions to the contract. ## Ai Angle A grounded assistant can tell a buyer 'how much of contract 4600001234 is consumed, which release orders drew it down and when does it expire?' by reading EKKO, EKPO and EKAB with the user's own authorizations. Netray's ERPray layer does this read-only and can run on-prem, so commercial terms stay inside your landscape. ## Faq ### What is the T-code to create a contract in SAP MM? **Answer:** ME31K creates a purchasing contract (outline agreement). ME32K changes it and ME33K displays it. For scheduling agreements, which are a different type of outline agreement, the equivalent transactions are ME31L, ME32L and ME33L. ### What is the difference between a contract and a scheduling agreement? **Answer:** A contract fixes terms and a total quantity or value, but delivery timing comes from individual release orders. A scheduling agreement fixes terms and also carries delivery schedule lines that the vendor receives, so it works like a standing order with dates. ### How do I create a release order against a contract? **Answer:** In ME21N, use the document overview to select the contract and adopt its items, or create the PO with reference to the contract. The PO item then points at the contract, picks up its price and terms, and reduces the remaining target quantity or value. ### How do I see how much of a contract has been used? **Answer:** Display the contract in ME33K and open the release documentation, or use ME3N and related lists. The data comes from the release records in EKAB, so the figures match the POs that reference the contract. ## Search terms sap mm contract tcode, me31k, me32k, me33k, sap quantity contract, sap value contract, sap outline agreement, contract release order sap, sap contract mk wk --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json