How To Fix FMCJ037 - Document not saved, no number range for company code &

SAP Error Message - Details

• Message type: E = Error

• Message class: FMCJ - IS-PS: Messages for Cash Desk Subsidiary Ledger

• Message number: 037

• Message text: Document not saved, no number range for company code &

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 FMCJ037 - Document not saved, no number range for company code & ?

  The SAP error message FMCJ037, which states "Document not saved, no number range for company code &," typically occurs when you are trying to post a financial document (such as a journal entry) in SAP, but the system cannot find a valid number range for the specified company code. This can happen for various reasons, including configuration issues or missing settings in the number range management.
  Cause:
  
  Missing Number Range: The number range for the specified company code has not been defined or is not active.
  Number Range Assignment: The document type you are trying to use may not be assigned to a number range for the company code.
  Number Range Status: The number range may be set to "not available" or may have been exhausted.
  Configuration Issues: There may be issues in the configuration of the financial document types or company codes.
  
  Solution:
  To resolve the FMCJ037 error, you can follow these steps:
  
  
  Check Number Range Configuration:
  
  Go to transaction code SNRO (Number Range Objects).
  Enter the object name related to the document type you are using (e.g., F_BKPF for accounting documents).
  Check if there is a number range defined for the relevant company code.
  
  
  
  Define Number Range:
  
  If no number range exists, you need to create one.
  Go to transaction code OBA7 (Maintain Number Ranges for Document Types).
  Select the appropriate document type and company code, and define a new number range if necessary.
  
  
  
  Assign Number Range to Document Type:
  
  Ensure that the document type you are using is assigned to the correct number range.
  You can do this in the same transaction (OBA7) by checking the assignment of document types to number ranges.
  
  
  
  Check Number Range Status:
  
  Ensure that the number range is not set to "not available" and that it has sufficient numbers available.
  You can check the status of the number range in transaction code SNUM.
  
  
  
  Test the Configuration:
  
  After making the necessary changes, try to post the document again to see if the error persists.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SNRO: Number Range Objects
  OBA7: Maintain Number Ranges for Document Types
  SNUM: Number Range Management
  
  
  
  Documentation: Refer to SAP Help documentation for detailed information on number range management and configuration.
  
  
  User Roles: Ensure that you have the necessary authorizations to make changes to number ranges and document types.
  
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis or Finance team for further investigation, as there may be additional configuration or system issues at play.