PO (Purchase Order) Transaction Code

Purchase Order Transaction Code

Purchase Order Transaction Code: A Purchase Order (PO) Transaction Code in SAP refers to a specific code that allows users to create, modify, or manage purchase orders within the SAP Materials Management (MM) module. Purchase orders are vital documents used in procurement, and these transaction codes provide an efficient way for users to initiate, track, and control the purchasing process. By using the appropriate PO transaction code, users can access the relevant screens and functionalities required to create purchase orders, update order details, check order statuses, and perform other essential tasks related to procurement and supply chain management in the SAP system.

MASS MAINTENANCE T-codes

  • MEMASSPO Mass maintenance of POs
  • MEMASSRQ Mass maintenance of PRs
  • MEMASSSA Mass Maintenance of Scheduling Agreements
  • MEMASSIN Mass Maintenance of info records
  • MEMASSCONTRACT Mass Maintenance of Contracts
  • XK99 Mass Maintenance of vendors

LISTS T-codes

  • ME2L POs by Vendor
  • ME2M POs by material
  • ME2K POs by account assignment
  • ME2C POs by material group
  • ME2B POs by Requirement tracking number
  • ME2N POs by PO number
  • ME2W POs by supplying plant
  • MELB Purchasing documents per purchasing tracking number
  • ME2S Planned / Actual comparison for POs with external services

REPORTING T-codes

  • ME80FN General list of POs
  • ME81N Analysis of PO value
  • ME2A Monitor vendor confirmations (Order acks, inbound deliveries)
  • ME92F Monitor Order acknowledgements for PRs
  • MCE3 PIS – Vendor
  • MCE5 PIS – Material group
  • MCE7 PIS – Material
  • ME6H PIS – Vendor Evaluation (On time delivery, Shipping instructions, qty reliability, shipping notification …)
  • MCW3 Vendor Invoice by Purch Org
  • MCW1 Vendor Payment by org data
  • MCEA Long term planning – Vendor
  • ME1L Info records by vendor
  • ME1M Info records by material
  • MKVZ List of vendors (purchasing)
  • ME65 Vendor evaluation by ranking
  • ME2V Goods receipt forecast (Expected GR for a plant on a particular day)

TRANSACTION DATA T-codes

  • ME21N Create PO
  • VL31N Create inbound delivery
  • ME51N Create purchase requisition
  • ME31K Create Contract
  • ME35K Release from contract
  • VL75 Output for inbound deliveries
  • MIGO Goods receipt
  • MIRO Logistics Invoice Verification
  • ME87 PO history records
  • EXPD Progress tracking for Purchase Orders
  • ME9F Output for POs
  • ME91F Output for PO reminders
  • ME56 Assign PR
  • ME57 Assign PR and process
  • ME58 Create PO from assignment
  • ME59N Create PO automatically from PRs
  • MECCM Send purchasing data from contract to catalog
  • ME3P Set prices (background) on contract
  • ME9K Output for Contracts
  • ME92K Monitor order acknowledgements
  • ME31L Create Scheduling agreement
  • ME38 Maintain delivery schedule for Scheduling Agreement
  • ME9EOutput of Scheduling Agreements
  • ME84 Create scheduling agreement release
  • ME41 Create RFQ
  • ME45 Release RFQ
  • ME47 Create quotation
  • ME47 Price comparison

MASTER DATA T-codes

  • ME11 Create info record
  • ME14 Display changes to Info Records
  • ME15 Flag info record for deletion
  • ME01 Create source list
  • ME04 Source list changes
  • MEQ1 Create quota arrangement
  • MEQ4 Quota arrangement changes
  • MP01 Maintain approved manufacturer parts
  • XK01 Create vendor (Central)
  • XK07 Account group change
  • MK01 Create vendor (purchasing)
  • MK04 Vendor account changes (purchasing)
  • MK05 Block vendor (purchasing)
  • MK06 Flag vendor for deletion
  • MPE1 Create buyer
  • MKH1 Vendor hierarchy
  • ME61 Create vendor evaluation
  • MEK1 Create condition records
  • MEKA Condition record overview

MESSAGES T-codes

  • MN01 Quote
  • MN04 PO
  • MN07 Outline agreement
  • MN10 Scheduling Agreement Delivery Schedule
  • MN24 Inbound delivery
  • Related Posts

    Attachments for SAP XI/PI – ARIBA Invoices sent via PI to S/4HANA

    Integration with SAP systems has never been more intriguing, especially with Ariba, Workday, Concur, Successfactors, Fieldglass, Hybris, and other satellite cloud solution vendors banging on doors every day. 🙂 I…

    Section 16 of CDS: Utilizing Built-In Features in CDS IV

    We have discussed SQL functions, unit/currency conversion functions, and date functions in our Built In Functions in CDS section; however, we did not cover the Time function. We’ll pick up…

    Leave a Reply

    Your email address will not be published. Required fields are marked *

    You Missed

    SAP XI/PI – Invoice Attachment Transfer from ARIBA to VIM

    • By Varad
    • November 8, 2024
    • 2 views
    SAP XI/PI – Invoice Attachment Transfer from ARIBA to VIM

    11 Steps to Include a New Field in an Already-Existing SAP LSMW Batch Input Recording

    • By Varad
    • November 6, 2024
    • 2 views

    Part 23 of ABAP for SAP HANA. How Can AMDP Be Used to Access Database Schema Dynamically?

    • By Varad
    • November 4, 2024
    • 2 views

    S/4HANA VDM 1 Employing CDS Virtual Data Model for Embedded Analytics

    • By Varad
    • November 1, 2024
    • 5 views