How To Fix PZ220 - Number range for payment requests is full

SAP Error Message - Details

• Message type: E = Error

• Message class: PZ - Messages: Payment program for payment requests

• Message number: 220

• Message text: Number range for payment requests is full

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 PZ220 - Number range for payment requests is full ?

  The SAP error message PZ220 indicates that the number range for payment requests is full. This typically occurs when the system has exhausted all available numbers in the defined number range for creating new payment requests. Here’s a breakdown of the cause, solution, and related information for this error:
  Cause:
  
  Exhausted Number Range: The number range defined for payment requests has been completely used up. This can happen if the number range is not sufficiently large to accommodate the volume of payment requests being generated.
  Configuration Issues: The number range may not be properly configured, or the intervals may not be set correctly.
  Archiving: If old payment requests are not archived, the number range may fill up quickly.
  
  Solution:
  
  
  Extend the Number Range:
  
  Go to the transaction code SNRO (Number Range Objects).
  Find the number range object related to payment requests (usually F_PAYREQ or similar).
  Check the current intervals and extend the number range by adding new intervals or increasing the upper limit of the existing interval.
  
  
  
  Create New Number Range:
  
  If extending the existing number range is not feasible, consider creating a new number range for payment requests.
  Ensure that the new number range is properly assigned to the relevant payment request configuration.
  
  
  
  Check Configuration:
  
  Verify the configuration settings for payment requests in the relevant customizing transaction (e.g., SPRO).
  Ensure that the number range is correctly assigned to the payment request type.
  
  
  
  Archiving Old Data:
  
  If applicable, consider archiving old payment requests to free up space in the number range.
  Use the archiving functionality in SAP to manage historical data.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or consult with your SAP Basis or functional team for best practices regarding number range management.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SNRO: Manage number ranges.
  SPRO: Access the SAP Reference IMG for configuration.
  
  
  
  SAP Notes: Check for any relevant SAP Notes that may provide additional guidance or fixes related to number range issues.
  
  
  User Authorization: Ensure that you have the necessary authorizations to make changes to number ranges and configurations.
  
  
  Testing: After making changes, perform testing to ensure that new payment requests can be created without encountering the error.
  
  
  By following these steps, you should be able to resolve the PZ220 error and ensure that your payment request processing continues smoothly.