Purchase Order Template in Sap

DOCUMENT CONTROL BLOCK

• Document ID: SOP-SAP-MM-4024
• Effective Date: October 24, 2023
• Version: 4.2
• Review Cadence: Annual / Post-Upgrade
• Owner: Julian Vance, Chief Operations Architect, Template Registry

---

1. Executive Summary & Scope

1.1 Purpose

This Standard Operating Procedure (SOP) defines the institutional-grade lifecycle for generating, validating, and executing a Purchase Order (PO) template within the SAP Materials Management (MM) module. It ensures compliance with Sarbanes-Oxley (SOX) controls, internal procurement policies, and 3-way matching financial standards.

1.2 Scope

This procedure applies to all operational units, procurement specialists, and supply chain administrators utilizing SAP S/4HANA or SAP ECC 6.0. It covers the creation of ad-hoc POs, the deployment of recurring PO templates via Transaction Code (T-Code) ME21N, and downstream release strategies. Excluded from this scope are service-entry sheet executions and blanket purchase agreements governed by SAP MM-SRV.

---

2. Prerequisites & Required Tools

2.1 Technical & Software Requirements

• System Access: SAP GUI for Windows/Java (v7.70 or higher) or SAP Fiori Launchpad.
• Security Roles & Authorization Objects:
  • M_BEST_EKO (Purchasing Organization authorization)
  • M_BEST_EKG (Purchasing Group authorization)
  • M_BEST_BSA (Document Type authorization)
• Master Data Prerequisites: Vendor Master Record (active status, correct reconciliation account), Material Master (MM03) or valid account assignment category, and Info Records / Pricing Conditions (ME11).

2.2 Compliance & Documentation Standards

• Approved Purchase Requisition (PR) with matched budget allocation.
• Delegated Authority (DoA) matrix clearance for the financial threshold.

---

3. Roles & Responsibilities (RACI Matrix)

---

4. Step-by-Step Procedure

Phase 1: Pre-Execution & Template Retrieval (ME21N)

• 1.1 Launch SAP GUI and enter T-Code ME21N (Create Purchase Order).
• 1.2 Set the Document Type to standard (NB) or custom institutional template type (e.g., ZDOM, ZIMP) in the document header dropdown.
• 1.3 Verify the Purchasing Organization, Purchasing Group, and Company Code match the legal entity boundaries.
• 1.4 If utilizing a recurring template, select the Document Overview On icon, navigate to the Purchase Requisitions or My Purchase Orders variant, and select the designated template baseline.

Phase 2: Header & Vendor Data Population

• 2.1 Enter the alphanumeric Vendor Account Number in the Header Vendor field (or search via F4 help based on Tax Jurisdiction / DUNS number).
• 2.2 Validate that the payment terms (e.g., NT30) and Incorterms (e.g., FOB, CIF) prepopulated from the Vendor Master or Info Record align with the commercial contract.
• 2.3 Access the Header Texts tab to input mandatory audit justification strings (e.g., project reference numbers, capital expenditure IDs).

Phase 3: Item Level & Account Assignment Structuring

• 3.1 Input Line Item details: Material Number, Order Quantity, and Delivery Date.
• 3.2 Ensure the Net Price auto-populates from the valid Info Record; perform manual override strictly with supervisory authorization and document pricing variance.
• 3.3 Designate the Account Assignment Category (e.g., K for Cost Center, F for Internal Order, A for Asset) and Tax Code (e.g., V1, I0).
• 3.4 Populate the corresponding Account Assignment tab with the correct GL Account, Cost Center, or WBS Element to prevent downstream invoice block conditions.

Phase 4: Verification, Release Strategy & Save

• 4.1 Click the Check button (Ctrl + S inside the check interface) at the top toolbar to execute structural, master data, and inventory validation routines.
• 4.2 Review the lower system message pane to ensure zero error logs (red indicators). Address any warning messages (yellow indicators) regarding price variances or delivery dates.
• 4.3 Click the Save button. Record the generated system-assigned 10-digit PO number (beginning with 45...) for tracking.
• 4.4 Verify in T-Code ME23N that the workflow status reflects the correct Release Strategy tier pending authorization.

---

5. Quality Assurance & Verification

5.1 Key Metric Thresholds

• First-Time Match Rate: $\ge 98%$ of created POs must pass accounting verification without manual intervention.
• Release Cycle Time: Standard PO release must execute within $\le 4$ business hours from creation.

5.2 Common Operational Pitfalls

• Expired Info Records: Using outdated pricing conditions resulting in invoice blocks during 3-way match.
• Incorrect Tax Mapping: Failing to apply jurisdiction-specific tax codes (MWSKZ), triggering compliance audits.

5.3 Audit Checklist

• PO pricing matches signed master contract or quotation.
• Account assignment accurately reflects the requesting business unit's OPEX/CAPEX budget.
• Document includes required attachment (Quotations, SOW) uploaded via SAP Generic Object Services (GOS).

---

6. Troubleshooting FAQ

Q1: The system returns error message "ME629 - Purchasing info record not found" during item entry. What is the immediate operational remedy?

A: This occurs when no active pricing link exists between the specified Vendor, Material, and Purchasing Organization.

1. Verify the material number and vendor account ID.
2. If correct, coordinate with the Master Data team to establish the Info Record via T-Code ME11 with current pricing conditions.
3. Alternatively, enter the net price manually at the PO line-item level if organizational policy permits ad-hoc pricing for non-catalog items.

Q2: The PO status is stuck at "Release Incomplete" (Status Code 01) and will not transmit to the vendor. How do I resolve this?

A: This indicates the PO has triggered a value-based or attribute-based Release Strategy workflow.

1. Navigate to T-Code ME23N, select the Header -> Release Strategy tab.
2. Identify the pending Release Codes (e.g., R1, R2).
3. Confirm that the threshold criteria (total net order value) have been met, and route the approval to the designated approver's SAP Business Workplace (SBWP) inbox, or execute the release directly if holding authority via T-Code ME28.