How to Generate a PO Automatically in SAP: Step-by-Step Guide

Creating purchase orders manually in SAP can become time-consuming when procurement teams process a large number of purchase requisitions. SAP supports automatic purchase order creation from eligible purchase requisitions, but the process depends on correct master data, source-of-supply determination, purchasing configuration, and automation settings.

There is also an important point to understand first:

SAP does not generally create a PO directly from a Sales Order in a standard third-party process. In third-party processing, the Sales Order can trigger a Purchase Requisition, which is then processed into a Purchase Order. SAP documents that a third-party item in a sales order can automatically create a purchase requisition, after which the PO is created from the requisition. 

This guide explains the process, prerequisites, SAP transaction options, automatic scheduling, common errors, and where AI-powered procurement tools such as ZYNO can make the overall workflow smarter.

SAP Automatic PO Creation: Quick Workflow

The basic process looks like this:

Sales Order / Purchase Requirement

              ↓

       Purchase Requisition

              ↓

    Source of Supply Determination

              ↓

     Validation & Approval

              ↓

 Automatic PO Creation Job

              ↓

        Purchase Order

              ↓

       Supplier Dispatch

              ↓

       Goods Receipt

              ↓

     Invoice Verification

For a normal procurement scenario, the process starts with a Purchase Requisition (PR). For third-party sales processing, a Sales Order can create the PR automatically. SAP's documentation confirms that third-party sales order items can generate corresponding purchase requisition items.

Step 1: Create or Trigger the Purchase Requisition

The first step is to have a valid Purchase Requisition.

A PR can originate from several business processes, including:

• Employee purchase requirements
• Material planning
• Inventory replenishment
• Production requirements
• Third-party sales orders
• Service requirements
• Other configured procurement processes

In third-party processing, when a suitable third-party item is entered in the Sales Order, SAP automatically creates the related purchase requisition. The PR contains information such as:

• Material or service
• Quantity
• Required delivery date
• Plant
• Purchasing group
• Account assignment
• Source information where applicable

Important distinction

If your question is "How do I create a PO from a Sales Order in SAP?", the more accurate workflow is:

Sales Order → Purchase Requisition → Purchase Order

rather than:

Sales Order → Purchase Order

Step 2: Make Sure the Vendor Can Be Determined

SAP needs to know where the requested material or service should be purchased from.

This is where source determination becomes important.

Depending on the scenario, SAP can use purchasing information such as:

• Supplier/vendor master data
• Purchasing info records
• Source lists
• Contracts
• Scheduling agreements
• Other configured sources of supply

SAP's current documentation states that a purchase requisition must have an assigned source of supply for certain PO creation processes. 

If SAP cannot determine an eligible source, automatic PO creation may not work as expected.

Step 3: Maintain the Required Master Data

Automatic PO creation is only as reliable as the underlying master data.

Check that the relevant information is maintained for:

Material or Product

Make sure the material has the necessary purchasing information.

Supplier

The supplier should have the appropriate purchasing organization information.

Purchasing Information

Maintain relevant purchasing info records and source-of-supply information where required.

SAP's automatic PO creation scenarios explicitly require master data such as material, supplier, and purchasing information.

This is one of the most common reasons an automatic PO process fails.

Bad master data = bad automation

Step 4: Check the Automatic PO Configuration

For automatic PO creation, SAP needs to be configured to permit the relevant purchasing process.

The exact configuration depends on your SAP version, deployment model, purchasing scenario, and business process.

The goal is to ensure that eligible purchase requisitions can be converted into purchase orders automatically rather than requiring a buyer to process each one manually.

For older SAP GUI-based processes, ME59N is associated with automatic creation of purchase orders from requisitions. SAP documentation identifies ME59N as the transaction for automatic PO creation from requisitions.

Step 5: Check the Purchase Requisition for Eligibility

Not every PR should automatically become a PO.

Before automatic conversion, check whether:

• A valid source of supply is assigned
• The requisition is not blocked
• Required purchasing data is available
• The item is eligible for PO creation
• Approval requirements have been satisfied
• Relevant contracts or source records are valid

SAP's current S/4HANA documentation states that PO creation from a PR requires conditions such as an assigned source of supply and an unblocked requisition item.

This is why simply activating automation does not mean every PR will instantly become a PO.

Step 6: Use ME59N for Automatic PO Creation

In SAP environments where ME59N is applicable, buyers can use it to process eligible purchase requisitions and create purchase orders automatically.

The basic concept is:

Purchase Requisition → Automatic PO Processing → Purchase Order

ME59N is particularly useful when you want to process multiple eligible requisitions rather than manually creating each PO individually. SAP documentation specifically identifies ME59N for automatic PO creation from requisitions.

However, modern SAP S/4HANA environments also provide Fiori-based approaches for scheduled purchasing jobs.

Step 7: Automate PO Creation with a Scheduled Job in SAP S/4HANA

For current SAP S/4HANA procurement workflows, SAP provides the Schedule Purchasing Jobs - Advanced app.

The relevant job template is:

Automatic Creation of Purchase Orders from Requisitions

SAP's documented procedure is:

1. Open Schedule Purchasing Jobs - Advanced
2. Select Create
3. Choose the automatic PO creation job template
4. Define the scheduling options
5. Select relevant parameters
6. Schedule the job
7. Let SAP process eligible purchase requisitions
8. Review the resulting purchase orders

SAP confirms that the scheduled job automatically converts eligible purchase requisitions into purchase orders. 

You can also configure the job to run on a recurring basis rather than requiring someone to manually initiate the process every time.

Step 8: Review the Generated Purchase Order

After the automatic job finishes, check the generated PO.

Verify:

• Supplier
• Material/service
• Quantity
• Price
• Delivery date
• Plant/location
• Account assignment
• Contract/source
• Terms and conditions

SAP provides job results that allow the purchaser to review the generated PO after automatic processing.

Automation should reduce manual work, but organizations should still define appropriate controls for exceptions and high-value purchases.

Step 9: Send the PO to the Supplier

Once the PO has been created and released according to your workflow, it can be communicated to the supplier through the configured output channel.

Depending on the SAP environment, supplier communication can use mechanisms such as:

• Email
• EDI
• Supplier networks
• Integrated procurement platforms
• Other configured output channels

The exact method depends on your SAP configuration and supplier integration.

Step 10: Complete the Procurement Cycle

Creating the PO is not the end of procurement.

The complete process usually continues:

PR

 ↓

PO

 ↓

Supplier Confirmation

 ↓

Goods / Service Delivery

 ↓

Goods Receipt / GRN

 ↓

Invoice

 ↓

PO + GRN + Invoice Matching

 ↓

Payment

This is where three-way matching becomes important.

The organization can compare:

Purchase Order + Goods Receipt + Supplier Invoice

to identify issues such as:

• Quantity mismatch
• Price mismatch
• Duplicate invoice
• Incorrect tax
• Missing receipt
• Invoice exceeding PO value

Can AI Make Automatic PO Creation Smarter?

Yes, but there is an important distinction.

Traditional SAP automation primarily automates the conversion and processing of eligible procurement documents according to configured rules. AI can add intelligence earlier in the process.

For example:

Employee Requirement

        ↓

AI Understands Requirement

        ↓

Purchase Requisition

        ↓

AI Supplier Recommendation

        ↓

Budget & Policy Validation

        ↓

Approval

        ↓

Automatic PO Creation

        ↓

GRN

        ↓

Invoice Matching

This can address a problem that simple PO automation does not solve:

How do you create the right PR in the first place?

Common Problems When Automatic PO Creation Does Not Work

If SAP is not creating the PO automatically, check these areas first:

1. No Source of Supply

SAP cannot determine which supplier should receive the order.

2. Incomplete Master Data

Supplier, material, info record, or purchasing data may be missing.

3. PR Is Blocked

A blocked or otherwise ineligible requisition cannot proceed through the configured automatic process.

4. Approval Is Pending

The PR may still be waiting for the required release or approval.

5. Configuration Issue

The relevant automatic PO creation settings or purchasing configuration may not be active.

6. Contract or Source Is Invalid

A previously valid source of supply may have expired or no longer meet the conditions.

7. Incorrect Job Parameters

In S/4HANA, the scheduled purchasing job must be configured with the appropriate selection parameters and recurrence settings.

SAP Automatic PO Creation vs AI Procurement Automation

Final Takeaway

If your goal is simply to automatically convert eligible Purchase Requisitions into Purchase Orders in SAP, the key is to maintain the required master data, establish a valid source of supply, configure the relevant purchasing settings, and use the appropriate automatic PO creation process. In current SAP S/4HANA, the Schedule Purchasing Jobs - Advanced app provides a documented job for automatically converting purchase requisitions into purchase orders. 

If the bigger objective is to make procurement intelligent from the beginning, the workflow needs to go beyond PO creation.

That's where AI becomes valuable.

Instead of starting with a manually created PR, an AI procurement platform such as ZYNO Procurement Software can start with the employee's natural-language requirement, create the PR, recommend suitable suppliers, validate budget and policy, route approval, and then convert the approved request into a PO.

In short: SAP can automate the PO. AI can help automate the decision and workflow that leads to the PO.

FAQs

How can I automatically create a PO in SAP?

You can automate PO creation from eligible purchase requisitions by maintaining the required master data and source of supply, configuring the purchasing process, and using the appropriate automatic PO creation functionality. In SAP S/4HANA, the Schedule Purchasing Jobs - Advanced app includes an Automatic Creation of Purchase Orders from Requisitions job template. 

What is the T-code for automatic PO creation in SAP?

ME59N is the SAP transaction associated with automatic creation of purchase orders from purchase requisitions in applicable SAP environments.

Can SAP create a PO directly from a Sales Order?

In a standard third-party processing scenario, SAP first creates a Purchase Requisition from the relevant Sales Order item. The PR is then processed into a Purchase Order. 

Why is SAP not creating my PO automatically?

Common causes include missing source-of-supply information, incomplete master data, blocked or unapproved requisitions, invalid purchasing information, or incorrect automation configuration.

Can AI automatically create a purchase requisition?

Yes. ZYNO AI Intake, for example, can interpret natural-language purchasing requirements and generate a structured purchase requisition while recommending suppliers, validating budgets, and routing the request for approval. 

Can ZYNO generate a PO automatically?

Yes. ZYNO states that its automated purchase order system can convert an approved purchase request into a PO while carrying vendor, pricing, and item information into the order. 

Is ZYNO an alternative to SAP automatic PO creation?

It is better to position ZYNO as an AI-powered procurement automation platform, not simply as an alternative SAP transaction. Its value is in automating the broader workflow around procurement intake, supplier recommendation, approvals, PO creation, GRN, invoice processing, and spend visibility.

What is the difference between PR and PO in SAP?

A Purchase Requisition is an internal request to procure goods or services. A Purchase Order is the formal purchasing document issued to the supplier. The PR generally precedes the PO in the procurement workflow.