How To Fix 5Z173 - Sequential number will be proposed

SAP Error Message - Details

• Message type: E = Error

• Message class: 5Z - IS-HR/PSG Public Sector Payroll - Germany

• Message number: 173

• Message text: Sequential number will be proposed

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 5Z173 - Sequential number will be proposed ?

  The SAP error message 5Z173, which states "Sequential number will be proposed," typically occurs in the context of document processing, particularly when dealing with sequential number ranges for documents such as invoices, purchase orders, or other transactional records. This message indicates that the system is unable to find a valid number from the defined number range and will propose a new sequential number instead.
  Cause:
  
  Number Range Exhaustion: The defined number range for the document type has been exhausted, meaning all available numbers have been used.
  Configuration Issues: The number range may not be properly configured in the system, or the number range object may not be assigned correctly to the document type.
  Authorization Issues: The user may not have the necessary authorizations to access or use the defined number range.
  Document Type Settings: The document type settings may not allow for the use of the existing number range, leading to the proposal of a new number.
  
  Solution:
  
  
  Check Number Range Configuration:
  
  Go to the transaction code SNRO (Number Range Objects) and check the configuration for the relevant number range object.
  Ensure that the number range is defined correctly and that there are available numbers in the range.
  
  
  
  Extend Number Range:
  
  If the number range is exhausted, you may need to extend it. This can be done in the same SNRO transaction by adjusting the upper limit of the number range.
  
  
  
  Review Document Type Settings:
  
  Check the configuration of the document type in transaction code OBA7 (for financial documents) or the relevant configuration transaction for your document type.
  Ensure that the document type is linked to the correct number range.
  
  
  
  User Authorizations:
  
  Verify that the user has the necessary authorizations to access and use the number range. This can be checked in transaction code SU01 (User Maintenance).
  
  
  
  Consult with SAP Basis or Functional Team:
  
  If you are unable to resolve the issue, it may be necessary to consult with your SAP Basis or functional team for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: SNRO (Number Range Objects), OBA7 (Document Type Configuration), SU01 (User Maintenance).
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to number ranges and error messages.
  Documentation: Review SAP documentation related to number range management for more detailed guidance on configuration and troubleshooting.
  
  By following these steps, you should be able to identify the cause of the error message 5Z173 and implement the appropriate solution.