Why did a Purchase Requisition (PR) split into multiple Purchase Orders (POs), or why did a change order create a new order number and cancel the original order number?

On the PR's History tab, find the history entry that refers to the PR splitting into a new PO or the PO cancellation, and click View Details to confirm why this happened.

For all types of POs, your site aggregates line items that meet all of the following conditions:

• Line items come from the same supplier location
• Line items have the same shipping address, if SplitOrderOnShipTo is set to No in the supplier location master data
• Line items have the same billing address
• Line items are all catalog items, or line items are all non-catalog items (can be disabled via customization)
• Line items are punchout items with the same header
• Line items are part of the same contract (different versions of the same contract are still considered the same contract)
• Any additional order-splitting criteria that your company has requested (via customization)

SAP variant sites also have the following considerations:

• Whether a line item requires a limit order item category split (can be disabled via customization)
• Whether line items all have the same currency
• Whether line items have the same purchase org value
• Whether line items have the same purchase group value (can be disabled via customization)

For change orders, a new PO will always be created if any of the following apply:

• ChangeOrderRestrictions is set to 1 in the supplier location master data
• Whether the supplier location's preferred ordering method changed between requisition versions (for example, from Electronic Ordering to Printing).
  • Exception: a new PO is not created when the order method is changed from Printing to Electronic ordering.

For Purchasing Card (PCard) orders the following additional conditions apply for aggregating line items:

• Line items have the same line-item split accounting (this requirement can be disabled through the Application.Procure.PreventPCardOrdersSplittingBasedOnAccounting parameter)
• Line items have the same PCard number
• Line items have the same transaction number
• Line items have the same transaction date

Please note that if a field that is marked to be a split order field has null value, this field will always cause a split between line items on the same version or for the same line item on different versions.

If you require a customization based on the applicable use case above, refer to What is the current process for customization requests?

A punchout header refers to a single punchout session. When a purchasing user punches out, puts an item in a cart, and punches back in, that is one session.
If they punch back out again, then that is a separate session which will have a different header, so the system will split that new session's items into a separate PO.

Purchasing > Purchase Orders