How To Fix WG068 - Collective processing number could not be generated

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 068

• Message text: Collective processing number could not be generated

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message WG068 - Collective processing number could not be generated ?

  The SAP error message WG068: "Collective processing number could not be generated" typically occurs in the context of workflow or collective processing in SAP, especially related to goods movements, delivery processing, or collective purchase order processing.
  
  Cause:
  The error WG068 indicates that SAP was unable to generate a collective processing number (also called a collective number or collective document number) during a collective processing run. This number is used to group multiple documents or items for batch processing.
  Common causes include:
  
  
  Number Range Issues:
  
  The number range object assigned for the collective processing number is either not defined, exhausted, or incorrectly configured.
  The number range interval might be missing or not extended.
  
  
  
  Configuration Problems:
  
  The collective processing number range object is not properly assigned in the customizing settings.
  Missing or incorrect settings in transaction codes related to collective processing (e.g., delivery processing, goods movement).
  
  
  
  Authorization Issues:
  
  The user executing the process does not have authorization to create or use the number range.
  
  
  
  System or Custom Code Errors:
  
  Custom enhancements or user exits might interfere with number generation.
  System inconsistencies or database locks.
  
  
  
  
  Solution:
  
  
  Check Number Range Configuration:
  
  Use transaction SNRO or SNWN to check the number range object related to collective processing numbers.
  Identify the number range object used for collective processing (e.g., WGNUM or similar).
  Verify that the number range interval exists and has available numbers.
  If exhausted, extend the number range interval.
  
  
  
  Verify Customizing Settings:
  
  Go to the relevant IMG path depending on the process (e.g., Logistics Execution ? Shipping ? Deliveries ? Define Number Ranges for Deliveries).
  Ensure the number range object is correctly assigned to the collective processing function.
  
  
  
  Check Authorizations:
  
  Verify that the user has the necessary authorizations to create collective processing numbers.
  Check authorization objects related to number range maintenance and document creation.
  
  
  
  Review Logs and Dumps:
  
  Check system logs (SM21), short dumps (ST22), and application logs (SLG1) for related errors.
  Look for any custom code or user exits that might affect number generation.
  
  
  
  Test Number Generation:
  
  Try to manually generate a collective processing number or simulate the process in a test environment.
  
  
  
  SAP Notes and Support:
  
  Search for SAP Notes related to WG068 for any known bugs or patches.
  If the problem persists, consider raising a support ticket with SAP.
  
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SNRO – Number Range Objects
  SNWN – Number Range Maintenance
  VL01N / VL02N – Delivery creation/change (if related to delivery collective processing)
  ME41 / ME42 – Purchase requisition collective processing (if related)
  SM21, ST22, SLG1 – System and application logs
  
  
  
  Number Range Object Examples:
  
  WGNUM – Often used for collective processing numbers in logistics.
  VBRK – Billing document number range (different context but similar concept).
  
  
  
  IMG Path Examples:
  
  Logistics Execution ? Shipping ? Deliveries ? Define Number Ranges for Deliveries
  Materials Management ? Purchasing ? Purchase Order ? Define Number Ranges
  
  
  
  
  Summary:
  
  
  
  Aspect
  Details
  
  
  
  
  Error Message
  WG068: Collective processing number could not be generated
  
  
  Cause
  Number range missing, exhausted, or misconfigured for collective processing number
  
  
  Solution
  Check and extend number range intervals; verify customizing and authorizations
  
  
  Related Tcodes
  SNRO, SNWN, VL01N, ME41, SM21, ST22, SLG1
  
  
  Additional
  Review SAP Notes; check for custom code interference
  
  
  
  
  If you provide the exact transaction or process where this error occurs, I can give more tailored advice.