# SAP Purchase Requisition Approval Form Template

> Source: https://netray.co/tools/sap-purchase-requisition-approval-form-template
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

An approval form that mirrors the fields of an SAP purchase requisition so approvers see what they release in ME54N.

## Category

sap

## Erp

SAP S/4HANA

## Audience

- Buyer
- Requester
- SAP MM consultant
- Procurement manager

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Company name

**Key:** company

**Type:** text

**Default:** Acme Precision Ltd

#### PR number

**Key:** pr_no

**Type:** text

**Default:** 10004582

#### Request date

**Key:** date

**Type:** date

**Default:** 2026-10-20

#### Requester

**Key:** requester

**Type:** text

**Default:** A. Singh, Maintenance

#### Plant

**Key:** plant

**Type:** text

**Default:** 1000

#### Purchasing group

**Key:** purch_group

**Type:** text

**Default:** P01

#### Account assignment category

**Key:** acct_assign

**Type:** select

**Options:**

- K cost center
- F production order
- P project (WBS)
- A asset
- U unknown
- Blank (stock item)

**Default:** K cost center

#### Cost center, order, WBS or asset

**Key:** cost_obj

**Type:** text

**Default:** CC-4410

#### Material or short text

**Key:** material

**Type:** text

**Default:** Spindle bearing set, 7014 angular contact

#### Quantity and UoM

**Key:** qty

**Type:** text

**Default:** 4 EA

#### Delivery date

**Key:** delivery_date

**Type:** date

**Default:** 2026-11-15

#### Estimated total value

**Key:** est_value

**Type:** text

**Default:** 1,860.00 USD

#### Desired vendor

**Key:** vendor

**Type:** text

**Default:** Northline Bearings (vendor 100245)

#### Business justification

**Key:** justification

**Type:** textarea

**Default:** Replacement for spindle on machine M-14 which shows rising vibration. Planned downtime window is 16 November.

**Blocks:**

#### Purchase Requisition Approval

**Body:** Company: {{company}}
PR number: {{pr_no}}
Request date: {{date}}
Requester: {{requester}}
Plant: {{plant}}
Purchasing group: {{purch_group}}

#### Line Details

**Table:**

**Columns:**

- Field
- Value

**Rows:**

**0:** Account assignment

**1:** {{acct_assign}}

**0:** Cost object

**1:** {{cost_obj}}

**0:** Material / short text

**1:** {{material}}

**0:** Quantity

**1:** {{qty}}

**0:** Delivery date

**1:** {{delivery_date}}

**0:** Estimated value

**1:** {{est_value}}

**0:** Desired vendor

**1:** {{vendor}}

#### Justification

**Body:** {{justification}}

#### Approval Routing

**Table:**

**Columns:**

- Approver
- Release code
- Decision
- Date

**Rows:**

**0:** Cost center owner

**0:** Department head

**0:** Finance (if above limit)

**0:** Procurement

#### Approvals

**Signatures:**

- Requester
- Approver 1
- Approver 2
- Procurement

**Notes:** Release codes and value limits come from your release strategy configuration. This form is a paper or PDF companion, not a replacement for release in ME54N or the Manage Purchase Requisitions app.

## Content

**Intro:** Many plants still circulate a PDF or Word approval alongside the SAP purchase requisition, especially for capital items or non-stock purchases. This template captures the same fields an approver sees in the requisition so the paper trail and the system record agree.

**Sections:**

#### How to use the form

**Body:** Enter the requisition number after you create it in ME51N or the Fiori app, then fill in the account assignment category and the cost object. Add a clear justification: what is being bought, why now and what happens if it is late. The routing table lists approvers and release codes so reviewers know which code they hold. Export to PDF for email approval or to Word if your process needs edits. Keep the justification short enough that an approver can decide without opening SAP.

#### Fields that matter in SAP

**Body:** Account assignment category decides which cost object is mandatory: K needs a cost center, F a production order, P a WBS element, A an asset. Items with no account assignment are stock or consumable items replenished by MRP or by hand. The purchasing group routes the requisition to a buyer, and the delivery date drives expediting. A desired vendor or fixed source from the source list can short-circuit sourcing, while a blank vendor leaves the buyer to run an RFQ.

#### Release strategies and thresholds

**Body:** A requisition release strategy typically depends on a characteristic such as total value, account assignment category or purchasing group. Release codes are assigned to approvers, and the strategy defines the order of release. Items with a release strategy cannot be converted to a PO until fully released. Write the expected approvers on the form so the requester does not wait on someone who is not in the chain, and confirm limits with your SAP team rather than guessing.

#### Common mistakes

**Body:** Requesters pick unknown account assignment to get past the screen and leave finance to correct it later. Free-text lines without a material or material group make spend analysis nearly impossible, so always give a material group. Delivery dates set to the day of creation produce permanent exceptions. Splitting one purchase into several small requisitions to dodge an approval threshold is also a control failure that auditors look for.

**Cta:** If approvals stall in your release strategy, Netray can build a read-only view of open requisitions by approver and age.

**Faq:**

#### What is the SAP transaction to create a purchase requisition?

**Answer:** ME51N creates a requisition in classic SAP GUI. In S/4HANA the Manage Purchase Requisitions and Create Purchase Requisition Fiori apps cover the same function. ME54N releases a requisition and ME53N displays it.

#### Why can a requisition not be converted to a purchase order?

**Answer:** Common reasons are an incomplete release strategy, a missing source of supply, a blocked material or vendor, or a requisition already assigned to another document. Check the release status on the item first.

#### Do I need an approval form if SAP has a release strategy?

**Answer:** Not necessarily. If your release strategy already covers the approvals, the form adds little. It helps where policy requires signed justification, or where some approvers do not work in SAP.

#### Which account assignment category should I use?

**Answer:** Use K for costs that belong to a cost center, F for a production or maintenance order, P for a project, A for an asset and blank for stock items. Avoid U unless your policy allows it, since finance must assign the cost later.

## Search terms

sap purchase requisition form, purchase requisition approval template, sap me51n fields, sap pr approval form excel, purchase requisition format sap, sap pr release request, requisition justification template

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json