Unit 7: Advanced Transactions in Procurement
Power users in purchasing, the warehouse and accounts payable mostly work with the "Enjoy" single-screen SAP GUI transactions ME51N, ME21N, MIGO and MIRO. This unit explains their screen areas and productivity features, plus contracts, source lists and automatic PO generation.
Lesson 1 · Maintaining a Purchasing Contract
After this lesson you can
- Explain the structure of a contract and the difference between quantity and value contracts
- Create contract release orders and read the release documentation
Key concepts
An outline agreement is a longer-term arrangement with a supplier, valid for a period and a total quantity or value, on fixed terms. Its two forms are the contract and the scheduling agreement. A contract has a normal header/item structure:
| Level | Content |
|---|---|
| Header | Supplier, agreement type, purchasing organization/group, validity period, target value (value contract), header conditions |
| Item | Material (or material group with item category M/W), target quantity, price/conditions, texts, optionally plant. No delivery dates or quantities per delivery. |
If an item has no plant, it is valid for all plants of the purchasing organization; such a contract without plant at item level is called a central contract (ERP central contract). Contracts can be created without reference, or with reference to a quotation, a purchase requisition or another contract.
Contract types
| Type | Agreement type | Fulfilled when |
|---|---|---|
| Quantity contract | MK | The target quantity per item has been called off through release orders |
| Value contract | WK | The total value of all release orders reaches the target value in the header |
Release orders and release documentation
Concrete quantities and dates are communicated by contract release orders – normal POs that reference the contract item. If a contract item is assigned as the source of supply in a PR, the PO created from it automatically becomes a release order. Each release order updates the item's release documentation (release order number, PO date, quantity, value), which is the basis for contract monitoring: in ME33K select the item and choose Item › Statistics › Release Documentation.
System steps
- ME31K: enter supplier, agreement type
MKorWK, agreement date, purchasing organization and group, validity end. - Enter items with material, target quantity, net price (and plant, if not central); for
WKenter the target value in the header. - Save; change with ME32K, display with ME33K.
- Create release orders in ME21N referencing the contract (or via PR conversion).
- Report on contracts with ME3N (by number), ME3L (by supplier), ME3M (by material); Fiori Manage Purchase Contracts.
SPRO › Materials Management › Purchasing › Contract › Define Document Types
In SAP S/4HANA the Fiori app Manage Purchase Contracts supports creation, approval by flexible workflow and monitoring of consumption; contracts can also be created centrally across systems via SAP S/4HANA Central Procurement (central purchase contracts), which is distinct from the ERP "central contract" without plant.
- Mandatory for a quantity contract: supplier, agreement type
MK, purchasing organization (and group, validity). Total value only forWK; delivery date and plant belong to the release order. - Release documentation is updated automatically.
- A contract without plant on item = central contract, valid for all plants of the purchasing organization.
Lesson 2 · Creating a Purchase Requisition with Source Determination
After this lesson you can
- Maintain the source list and the source list requirement
- Work efficiently with ME51N: screen areas, account assignment, status, templates
Source list
The source list manages sources of supply per material and plant. Each entry is valid for a period and points to a supplier (optionally a specific outline agreement item). Source list entries are evaluated in automatic source determination in purchasing and in MRP.
| Indicator in entry | Effect |
|---|---|
| Fixed | Preferred source in that period (relevant for source determination in purchasing) |
| Blocked | No procurement from this source in that period |
| MRP indicator | Only relevant for MRP sourcing: e.g. MRP may create PRs with this source assigned or schedule lines for a scheduling agreement (see Unit 8) |
A source list requirement means the material may be procured only from sources listed as valid. It can be set per material (purchasing view indicator "Source list") or for the whole plant in Customizing – then every externally procured material of that plant needs source list records.
SPRO › Materials Management › Purchasing › Source List › Define Source List Requirement at Plant Level
Source list maintenance options
- Manually per material and plant: ME01 (maintain), ME03 (display).
- From an outline agreement or info record: Item › Maintain Source List while creating/changing it (not from a PO).
- Automatically: ME05 (collective, for many materials) or ME06 (analyze) – creates one record per info record or agreement item; a preview/simulation is available. In ME01 the individual generation function does the same for one material.
Source determination sequence (overview)
ME51N: single-screen transaction
| Screen area | Content |
|---|---|
| Header | In the PR only a header note and, with overall release, release information (in a PO: supplier, org data, conditions) |
| Item overview | Main item data: account assignment category, item category, material, quantity, delivery date, plant; catalog items via OCI-compliant web catalogs |
| Item detail | Tabs for texts, account assignment, source of supply, status, contact person, valuation |
| Document overview | Lists PRs, POs, contracts etc. for reference |
- Areas open/close individually; the layout is remembered next time. Switch between create and display/change, or jump to another document with Other Purchase Requisition.
- Account assignment: category in the item overview, details on the Account Assignment tab; toggle single ↔ multiple account assignment. In a PR, multiple assignment can distribute the quantity equally and readjusts automatically when the total changes (e.g. 90 chairs over 3 cost centers → 30 each; change to 120 → 40 each). In a PO this automatic equal redistribution does not happen.
- Status tab: processing status (not edited, RFQ created, ordered, outline agreement created) plus the history of follow-on documents (GR, IR).
- Contact person tab: creation indicator – shows whether the PR was created manually or e.g. by MRP.
- Templates: Save as Template / Load from Template for PRs and POs; user-specific or public (public templates require authorization object
M_TEMPLATE). On loading you choose header + items or items only.
- Source list indicators: fixed, blocked, MRP – "Automatic PO" and "source list requirement" are not source list indicators.
- Source list can be maintained manually, automatically, or from agreements/info records – not from POs.
- Source list requirement: material master purchasing view, or plant-wide in Customizing.
- ME51N areas: header, item overview, item detail, document overview.
Lesson 3 · Using Advanced Transaction for Purchase Order Creation
After this lesson you can
- Create a PO with reference using the document overview of ME21N
- Configure selection variants, breakdown and layouts
- Generate POs automatically with ME59N
ME21N basics
ME21N has the same four screen areas as ME51N: header, item overview, item detail and document overview. Personal Settings let each user store default values (e.g. document type, purchasing group, plant) and open the document overview automatically. An embedded help area can be shown while you continue working.
Creating a PO with reference
Referencing a PR, RFQ/quotation or contract copies item data (and header data where available) into the PO – less typing, fewer errors; most fields stay changeable. In the document overview select documents or items and choose Adopt or drag them onto the shopping-cart icon. Double-clicking a PO or PR only displays it (RFQs, contracts and scheduling agreements cannot be displayed by double-click). The PO item stores the reference document and item number. Alternatively type the reference document/item number directly into the item overview.
| Document overview setting | Purpose |
|---|---|
| Selection variant | Which documents to select (supplier, material, creation period …); predefined variants My purchase orders / My purchase requisitions use a period from personal settings. |
| Breakdown | Criteria used to sort/group the selected documents. |
| Layout | Which columns are shown and in which order; user-specific or cross-user layouts, default via Manage Layout. Separate layouts for purchasing documents and for PRs. |
Automatic PO generation (ME59N)
PR items with an assigned source contain everything needed (supplier, price), so the system can convert them without a buyer – regardless of how the PR or the assignment was created.
| Prerequisite | Where |
|---|---|
| Automatic PO indicator | Material master, Purchasing view (plant level) |
| Automatic purchase order indicator | Supplier (BP) purchasing data per purchasing organization |
| Valid source of supply assigned | In the PR item |
- Selection criteria: purchasing group, purchasing organization, MRP controller, supplier, etc.; option to include items with contracts (creates release orders).
- Grouping: e.g. one PO per purchasing group, per plant or per delivery date.
- Errors (blocked supplier, missing account assignment for
U, missing tax code for ERS…) prevent conversion. Option exclude items with errors: POs are created from all correct items, errors listed in the log. Without this option, a PO is only created if all items grouped into it are correct.
- Run ME59N with selection criteria and grouping options; test run first if needed.
- Review the log; correct faulty PRs and rerun, or schedule as a background job.
- ME21N and ME51N share the same screen areas (true).
- Document overview can show POs, PRs, RFQs, contracts, scheduling agreements – not accounting or material documents.
- Breakdown = sorting criteria.
- ME59N prerequisites: Automatic PO in material master and supplier, valid source in the PR item (not header).
Lesson 4 · Using the Advanced Transaction for Goods Receipt
After this lesson you can
- Use the screen areas and settings of MIGO
- Post a GR for a PO into the right stock type and analyse stocks with MMBE
MIGO screen areas
| Area | Content / behaviour |
|---|---|
| Overview tree | Automatically shows your last ten referenced documents (POs, orders, reservations), material documents and held data. It cannot be influenced by the user and is not a search tool (use Search for Document); only material documents can be opened from it for display. |
| Header data | Document and posting date, header text, delivery note, bill of lading, creator; access to the accounting document (FI documents button) after posting. |
| Item overview | All items with quantity, storage location, stock type and the Item OK checkbox. |
| Item detail | Tabs for material, quantity, where (movement type, plant, storage location, stock type), PO data, account assignment, partner. Once an item's detail is open, it can only be changed there. |
Screen layout is retained between sessions. Restart resets the transaction without leaving it. Settings › Default Values stores personal defaults (plant, storage location, movement type, reference). The first selection is the action (goods receipt, goods issue, return delivery, transfer posting, display, cancellation, release GR blocked stock…), then the reference document type and the movement type.
System steps (GR for PO)
- MIGO (menu: Logistics › Materials Management › Inventory Management › Goods Movement › GR for Purchase Order; also MIGO_GR).
- Select action Goods Receipt, reference Purchase Order, check movement type
101. - Enter or search the PO number and execute to copy its open items.
- On the header General tab enter document date and delivery note.
- Set Item OK for delivered items, adjust quantity and storage location / stock type.
- Check and post; cancel later with action Cancellation (movement type
102generated automatically).
Stock types
| Stock type | Available in MRP | Consumption allowed | Transfer to unrestricted |
|---|---|---|---|
| Unrestricted-use | Yes | Yes | – |
| Quality inspection | Yes (configurable) | No | 321 or QM usage decision |
| Blocked | Usually no | No | 343 |
Withdrawals for consumption are only possible from unrestricted-use stock, but scrapping, sampling and inventory differences can be posted from all stock types. A GR for a PO into valuated stock always uses 101; the target stock type is chosen with the stock type indicator on the item. (Separate from these is GR blocked stock, 103, which is not yet valuated stock.)
Stock overview (MMBE)
MMBE shows the stock of one material, totalled per stock type at each org level: client, company code, plant, storage location, and also batches, valuation types and special stocks (e.g. consignment). Display versions define which stock types appear in which column; they are set up in Inventory Management Customizing. Several materials: MB52.
Fiori apps Post Goods Movement, Stock – Single Material and Stock – Multiple Materials complement MIGO/MMBE. Because S/4HANA stock is derived from MATDOC, stock reports run in real time without aggregate tables.
- The MIGO overview tree cannot be selected/controlled by the user (statement "as in ME21N…" is false).
- Before the PO number: action (transaction), reference document type, movement type.
- Stock types: unrestricted-use, quality inspection, blocked – "restricted-use" does not exist.
- GR to all three stock types with
101+ stock type indicator.
Lesson 5 · Using the Advanced Transaction for Invoice Verification
After this lesson you can
- Name the screen areas of MIRO
- Enter an invoice against a PO including multiple references and balance check
MIRO screen areas
| Area | Content |
|---|---|
| Transaction | Invoice, credit memo, subsequent debit, subsequent credit |
| Header data | Invoice date, reference (supplier invoice number), gross amount, tax amount/code, invoicing party, payment terms (tabs Basic data, Payment, Details, Tax …) |
| Assignment (allocation) | Reference to procurement transactions: PO/scheduling agreement, delivery note, bill of lading, supplier, etc. |
| Invoice items | Proposed items to check and adjust; layouts change columns |
| Vendor data | Invoicing party details from the master (shown after entering supplier or PO); branch to master record |
| Balance | Balance and status traffic light: green = can be posted; yellow = posted but blocked for payment |
| PO structure | PO history of the referenced items |
System steps
- Start MIRO (menu: Logistics › Materials Management › Logistics Invoice Verification › Document Entry › Enter Invoice). First time: enter the company code (change later via Edit › Switch Company Code).
- Transaction Invoice; on Basic data enter invoice date, reference, gross amount, tax amount and tax code.
- Choose the assignment type (PO, delivery note …) and enter the document number; for several documents use More Allocation Criteria.
- Compare proposed items with the paper invoice and correct quantity/amount; selected items are posted.
- Check that the balance is zero (arithmetically correct), then post. Display with MIR4; park instead of posting with MIR7 if incomplete.
The Booking OK indicator in MIRO only marks items you have checked/processed. It does not select or deselect items for posting – unlike the Item OK checkbox in MIGO, which does control which items are posted.
- MIRO transactions: invoice, credit memo, subsequent debit, subsequent credit (no "subsequent delivery/adjustment").
- Booking OK = item checked and processed; no effect on posting.
- Zero balance → arithmetically correct; yellow light → blocked for payment.
Unit summary & exam focus
Contracts and source lists prepare automatic sourcing; the Enjoy transactions ME51N/ME21N use a common four-area screen with a powerful document overview; ME59N converts assigned PRs into POs; MIGO and MIRO handle GR and invoice with personal defaults and clear status indicators.
T-codes in this unit
| T-code | Purpose |
|---|---|
| ME31K | Create contract |
| ME32K | Change contract |
| ME33K | Display contract / release documentation |
| ME3N | Outline agreements by number |
| ME3L | Outline agreements by supplier |
| ME3M | Outline agreements by material |
| ME01 | Maintain source list |
| ME03 | Display source list |
| ME05 | Generate source list |
| ME06 | Analyze source list |
| ME51N | Create purchase requisition |
| ME21N | Create purchase order |
| ME59N | Automatic creation of POs from PRs |
| MIGO | Goods movements |
| MIGO_GR | MIGO preset for goods receipt |
| MMBE | Stock overview |
| MB52 | Warehouse stocks of materials |
| MIRO | Enter incoming invoice |
| MIR4 | Display invoice document |
| MIR7 | Park invoice |
Self-check questions
- Which entries are mandatory for a quantity contract?
Answer
Supplier, agreement type MK and purchasing organization (plus purchasing group, validity end). Total value belongs to value contracts; delivery date to release orders. - Which indicators exist in a source list record?
Answer
Fixed, blocked and the MRP indicator. - Can you maintain the source list while creating a PO?
Answer
No – manually, automatically, or from outline agreements/info records only. - What are the prerequisites for ME59N?
Answer
Automatic PO indicator in material master and supplier master, and a valid source of supply assigned to the PR item. - What is the difference between "exclude items with errors" and not excluding them?
Answer
With exclusion, POs are created from all correct items; without it, a PO is created only if every item grouped into it is error-free. - What must be entered in MIGO before the PO number?
Answer
The action (transaction), reference document type and movement type. - From which stock type can material be consumed?
Answer
Only unrestricted-use stock (scrapping/sampling possible from all types). - What does the Booking OK indicator in MIRO mean?
Answer
That the item has been checked and processed; it does not influence whether the item is posted.