How To Fix F0901 - Enter CRNO for DME file since an automic number is not desired

SAP Error Message - Details

• Message type: E = Error

• Message class: F0 - FI batch program messages

• Message number: 901

• Message text: Enter CRNO for DME file since an automic number is not desired

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 F0901 - Enter CRNO for DME file since an automic number is not desired ?

  The SAP error message F0901 indicates that when generating a DME (Data Medium Exchange) file, the system requires a specific "CRNO" (Check Number) to be entered, as it cannot automatically generate one. This typically occurs in the context of payment processing, where the DME file is used to facilitate electronic payments.
  Cause:
  The error arises because the system is configured to not automatically generate a check number (CRNO) for the DME file. This can happen due to various reasons, such as:
  
  Configuration Settings: The payment method or the DME configuration may be set to require manual entry of the check number.
  Missing Data: The necessary data for generating a check number might be missing or incorrectly configured in the payment run.
  Customizations: There may be custom developments or enhancements in the SAP system that affect how check numbers are generated.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Payment Method Configuration:
  
  Go to the configuration settings for the payment method used in the payment run.
  Ensure that the settings allow for automatic generation of check numbers if that is desired.
  
  
  
  Manual Entry:
  
  If the system is configured to require a manual entry, you will need to enter a valid check number (CRNO) when prompted.
  
  
  
  Review DME Configuration:
  
  Check the DME configuration in transaction FBZP (Payment Program Configuration) to ensure that the settings are correct and that the system is set up to generate check numbers as needed.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or help files related to DME file generation and payment processing for any specific requirements or settings that may need to be adjusted.
  
  
  
  Check for Custom Code:
  
  If there are any custom developments in your SAP environment, review them to ensure they are not interfering with the standard DME processing.
  
  
  
  Testing:
  
  After making any changes, perform a test payment run to ensure that the issue is resolved and that the DME file can be generated without errors.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FBZ0 (Payment Run), FBZP (Payment Program Configuration), and F110 (Automatic Payment Transactions).
  SAP Notes: Check for any SAP Notes related to DME processing and error F0901 for additional guidance or patches that may address known issues.
  User Exits and BAdIs: If your organization uses user exits or BAdIs for payment processing, review them to ensure they are functioning as intended.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or reach out to SAP support for further assistance.