How To Fix FTE_FIEB001 - Run &1 &2 doesnt exist in REGUH

SAP Error Message - Details

• Message type: E = Error

• Message class: FTE_FIEB - Bank Statement Formats Messages

• Message number: 001

• Message text: Run &1 &2 doesnt exist in REGUH

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 FTE_FIEB001 - Run &1 &2 doesnt exist in REGUH ?

  The SAP error message FTE_FIEB001 indicates that a specific run (identified by the parameters &1 and &2) does not exist in the REGUH table. The REGUH table is used in SAP to store information about payment runs, and this error typically arises when there is an attempt to access a payment run that has not been created or has been deleted.
  Causes:
  
  Non-existent Payment Run: The specified payment run (identified by the run number and company code) does not exist in the REGUH table.
  Incorrect Parameters: The parameters passed to the function or transaction may be incorrect, leading to a search for a non-existent run.
  Deletion of Payment Run: The payment run may have been deleted after it was created, which would remove its entry from the REGUH table.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to view the payment run, leading to the perception that it does not exist.
  
  Solutions:
  
  Verify Parameters: Check the parameters (&1 and &2) being used to ensure they are correct. Make sure you are using the correct run number and company code.
  Check REGUH Table: Use transaction SE11 or SE16 to view the REGUH table and confirm whether the specified run exists. If it does not, you may need to create a new payment run.
  Recreate Payment Run: If the payment run was deleted or never created, you may need to recreate it using the appropriate transaction (e.g., F110 for automatic payment transactions).
  Check User Authorizations: Ensure that the user has the necessary authorizations to access the payment run data. If not, contact your SAP security administrator to grant the required permissions.
  Consult Logs: Check the application logs (transaction SLG1) for any additional error messages or information that might provide more context about the issue.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as F110 (Automatic Payment Transactions) and F111 (Manual Payment Transactions).
  SAP Notes: Search for SAP Notes related to the error message for any known issues or patches that may address the problem.
  Documentation: Review SAP documentation on payment processing and the REGUH table for a better understanding of how payment runs are managed within the system.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP support team or reach out to SAP support for further assistance.