How To Fix WG218 - Purchase orders could not be bundled, number range & does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: WG - Messages for store order and investment buy

• Message number: 218

• Message text: Purchase orders could not be bundled, number range & does not exist

What causes this issue?

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

System Response

How to fix this error?

Contact your system administrator.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message WG218 - Purchase orders could not be bundled, number range & does not exist ?

  The SAP error message:
  WG218 Purchase orders could not be bundled, number range & does not exist
  typically occurs in the context of purchase order (PO) number range assignment and bundling processes, such as when using transaction codes or functions that bundle multiple POs for printing, output, or processing.
  
  Cause
  
  Number range interval for purchase orders does not exist or is not maintained: The system tries to assign or reference a PO number from a number range interval that is either missing or not properly configured.
  Number range object for purchase orders is not defined or incorrectly maintained: The number range object (usually EINKBELEG for purchase documents) might not have intervals defined for the relevant document type or purchasing organization.
  Bundling logic references a number range that is not available: When bundling POs for output, the system attempts to group POs based on number ranges, but the required number range interval is missing.
  Customizing or configuration inconsistency: The PO document type or number range assignment in SPRO (IMG) might be incomplete or inconsistent.
  
  
  Solution
  
  
  Check and maintain number ranges for purchase orders:
  
  Go to transaction SNRO (Number Range Objects).
  Enter the number range object for purchase orders, typically EINKBELEG.
  Check if number range intervals exist and are valid for the relevant document types.
  If missing, create or extend number range intervals ensuring they cover the required number ranges.
  
  
  
  Verify PO document type and number range assignment:
  
  Use transaction OMWN or navigate via SPRO:
  
  Materials Management -> Purchasing -> Purchase Order -> Define Document Types
  
  
  Check that the PO document type is assigned to a valid number range interval.
  
  
  
  Check bundling configuration:
  
  If bundling is done via output management or a custom program, verify that the logic correctly references existing number ranges.
  Ensure that the number range intervals used in bundling are consistent with those maintained in SNRO.
  
  
  
  Re-run the bundling process after corrections.
  
  
  If the problem persists, check for OSS notes or patches:
  
  Sometimes, specific SAP versions have bugs related to number range handling in PO bundling.
  Search SAP Support Portal for notes related to message WG218.
  
  
  
  
  Related Information
  
  Number Range Object for Purchase Orders: EINKBELEG
  Transaction Codes:
  
  SNRO - Number Range Object Maintenance
  OMWN - Assign Number Ranges to Document Types
  ME21N / ME22N - Create/Change Purchase Order
  
  
  SPRO Path for PO Number Range:
  
  Materials Management -> Purchasing -> Purchase Order -> Define Document Types
  
  
  Bundling in SAP MM:
  
  Bundling is used to group multiple POs for output or processing.
  Bundling logic depends on number ranges and document types.
  
  
  
  
  Summary
  
  
  
  Aspect
  Details
  
  
  
  
  Error Message
  WG218 Purchase orders could not be bundled, number range & does not exist
  
  
  Cause
  Missing or incorrect number range intervals for purchase orders
  
  
  Solution
  Maintain number ranges in SNRO for object EINKBELEG, verify PO document type assignment
  
  
  Related TCodes
  SNRO, OMWN, ME21N, ME22N
  
  
  Additional
  Check bundling configuration and SAP Notes if issue persists
  
  
  
  
  If you provide the exact scenario or transaction where this error occurs, I can help with more specific steps.