# SAP PO Example: Sample Purchase Order Format and Document Types (NB, FO, UB)

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

## Short answer

A sample SAP purchase order layout with header, item and delivery data, plus a quick reference of PO document types such as NB, FO and UB.

## Category

sap

## Erp

SAP S/4HANA

## Audience

- Buyer
- SAP MM consultant
- Procurement analyst

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Buying company

**Key:** company

**Type:** text

**Default:** Acme Precision Ltd

#### PO number

**Key:** po_no

**Type:** text

**Default:** 4500012345

#### PO document type

**Key:** doc_type

**Type:** select

**Options:**

- NB Standard PO
- FO Framework order
- UB Stock transport order

**Default:** NB Standard PO

#### Document date

**Key:** po_date

**Type:** date

**Default:** 2026-10-20

#### Vendor

**Key:** vendor

**Type:** text

**Default:** 100234 Northern Steel Supply GmbH

#### Purchasing org / group

**Key:** purch_org

**Type:** text

**Default:** 1000 / 001

#### Plant and storage location

**Key:** plant

**Type:** text

**Default:** 1100 / 0001

#### Material and short text

**Key:** material

**Type:** text

**Default:** RM-AL6061-25 Aluminium bar 6061 T6 25mm

#### Order quantity and unit

**Key:** qty

**Type:** text

**Default:** 500 KG

#### Net price per unit

**Key:** price

**Type:** text

**Default:** 4.85 EUR per 1 KG

#### Delivery date

**Key:** delivery_date

**Type:** date

**Default:** 2026-11-12

#### Payment terms and Incoterms

**Key:** payment_terms

**Type:** text

**Default:** ZB30 net 30 days, FCA Hamburg

**Blocks:**

#### Purchase Order {{po_no}}

**Body:** Buyer: {{company}}
Document type: {{doc_type}}
Document date: {{po_date}}
Vendor: {{vendor}}
Purchasing organisation / group: {{purch_org}}
Payment terms and Incoterms: {{payment_terms}}

#### Item overview (as in ME21N item overview)

**Table:**

**Columns:**

- Item
- Material / short text
- Quantity
- Net price
- Plant / SLoc
- Delivery date

**Rows:**

**0:** 00010

**1:** {{material}}

**2:** {{qty}}

**3:** {{price}}

**4:** {{plant}}

**5:** {{delivery_date}}

#### Typical item detail tabs

**Table:**

**Columns:**

- Tab
- What it holds

**Rows:**

**0:** Material data

**1:** Material group, vendor material number, info record

**0:** Quantities / weights

**1:** Order unit, conversion, scheduled quantity

**0:** Delivery schedule

**1:** Delivery date, quantity, statistical date

**0:** Delivery

**1:** Over and under delivery tolerances, GR indicator, unlimited delivery

**0:** Invoice

**1:** Tax code, invoice receipt and GR-based invoice verification flags

**0:** Conditions

**1:** Net price, discounts, freight, from the pricing procedure

**0:** Account assignment

**1:** Cost center, order or asset for non-stock items

**0:** Confirmations

**1:** Vendor order acknowledgement, inbound delivery control

#### Common PO document types in standard SAP

**Table:**

**Columns:**

- Type
- Name
- Typical use

**Rows:**

**0:** NB

**1:** Standard purchase order

**2:** Regular external purchasing

**0:** FO

**1:** Framework order

**2:** Open order with validity period and limit, called off by releases

**0:** UB

**1:** Stock transport order

**2:** Transfer of stock between plants of the same company code

**0:** MK

**1:** Quantity contract (outline agreement)

**2:** Agreed total quantity over a period, referenced by POs

**0:** WK

**1:** Value contract (outline agreement)

**2:** Agreed total value over a period

**0:** LP

**1:** Scheduling agreement

**2:** Repeat deliveries with delivery schedule lines

#### Approvals

**Signatures:**

- Buyer
- Approver (release strategy)
- Vendor acknowledgement

**Notes:** This is a sample layout, not your printed form. The actual PO printout is controlled by output type NEU (or your copy), the form (SAPscript, Smartform or Adobe) and output determination. Document types and number ranges are configurable, so confirm yours in customizing for purchasing document types. Types shown are SAP standard delivered values.

## Content

**Intro:** This page gives you a realistic SAP purchase order example: the header, the item overview as you see it in ME21N, the item detail tabs, and the standard document types NB, FO and UB. Edit the fields to produce a clean sample for training, a specification or a test case.

**Sections:**

#### How to use the example

**Body:** Choose the document type, enter vendor, plant, material and price, then export to PDF or Word. Use the result as a test data sheet for user acceptance, as a training handout, or as the sample behind a PO form requirement. The item detail table lists the tabs where each field sits, which helps when you explain to a vendor or an auditor where a value comes from.

**Bullets:**

- Header: vendor, purchasing org, group, payment terms, Incoterms
- Item: material, quantity, price, plant, delivery date
- Conditions: price and surcharges from the pricing procedure

#### SAP PO format and structure

**Body:** A purchasing document has a header with data valid for all items, and one or more items, each with its own schedule lines and conditions. The document type controls number range, field selection and which item categories are allowed. Printing is separate from the document: the output type and form decide the layout the vendor receives. That is why two companies can have very different PO printouts from the same underlying data.

#### Document types compared

**Body:** NB is the default for external purchases. FO is used when you place an open order against a limit and call it off later. UB creates a stock transport order and drives a movement between plants, so it needs supplying plant and a delivery route. Outline agreements (MK, WK, LP) are not POs themselves but are referenced by them, and scheduling agreements use their own schedule line release flow.

#### Common mistakes

**Body:** Teams often use NB for stock transfers and then fight with tax and billing, when UB would give the right flow. Another mistake is setting tolerances only in the vendor master and forgetting that item-level values override them. Finally, a PO that looks right on screen can print wrong because output conditions were not maintained for that purchasing organisation.

**Cta:** Netray can add a private AI assistant on your own servers that lets buyers ask for open POs, delivery dates and price history from SAP in plain language, read-only and with the query shown.

**Faq:**

#### What is the standard SAP PO document type?

**Answer:** NB is the standard purchase order document type in SAP delivered customizing. FO is the framework order and UB is the stock transport order. Your system may add custom types with Z names.

#### Which transaction creates a purchase order?

**Answer:** ME21N is the standard transaction for creating a purchase order in both ECC and S/4HANA. ME22N changes and ME23N displays. In S/4HANA you can also use the Fiori app for managing purchase orders.

#### Where is the PO print layout configured?

**Answer:** Output determination for purchasing is set up with output types (NEU for the PO is the SAP standard) and a form. Maintain conditions in NACE for application EF, or the output management configuration in S/4HANA.

#### Is a contract the same as a PO?

**Answer:** No. A contract (MK or WK) is a long term agreement with a validity period and a target quantity or value. POs then reference it so that price and terms are taken automatically. Contract release orders consume the contract target.

## Search terms

sap po example, sap po format, sap mm order types, sap purchase order sample, sap po document types, nb fo ub sap, sap purchase order layout, me21n purchase order fields

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