FMBWB073 - You cannot create a held document starting with &1

SAP Error Message - Details

• Message type: E = Error

• Message class: FMBWB - Budgeting Workbench

• Message number: 073

• Message text: You cannot create a held document starting with &1

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 FMBWB073 - You cannot create a held document starting with &1 ?

  The SAP error message FMBWB073 indicates that you cannot create a held document starting with a specific number (represented by &1). This error typically occurs in the context of financial document processing, particularly when dealing with held documents in the SAP system.
  Cause:
  The error is usually caused by one of the following reasons:
  
  Document Number Range Issue: The document number you are trying to create falls outside the defined number range for held documents. This can happen if the number range is not properly configured or if the number you are trying to use is not allowed.
  Configuration Settings: The system may have specific settings that restrict the creation of held documents based on certain criteria, such as document types or status.
  Authorization Issues: The user may not have the necessary authorizations to create held documents, leading to this error.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Number Range Configuration:
  
  Go to the transaction code SNRO (Number Range Objects) and check the configuration for the number range object related to held documents.
  Ensure that the number range is correctly defined and that the number you are trying to use falls within the allowed range.
  
  
  
  Review Document Type Settings:
  
  Check the configuration for the document type you are using to create the held document. Ensure that it is set up to allow the creation of held documents.
  You can do this in the transaction code OBD4 (Document Types) or OBY6 (Document Type Configuration).
  
  
  
  User Authorizations:
  
  Verify that the user has the necessary authorizations to create held documents. This can be checked in the user roles and profiles assigned to the user.
  
  
  
  Consult SAP Notes:
  
  Check for any relevant SAP Notes that may address this specific error message. Sometimes, there are known issues or patches that can resolve the problem.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance. Provide them with the error message details and any relevant configuration information.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like SNRO, OBD4, and OBY6 for number range and document type configuration.
  SAP Documentation: Review SAP documentation related to financial document processing and held documents for additional insights.
  User Roles: Ensure that user roles are properly assigned and that they include the necessary permissions for document creation.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.