How To Fix BNK_COM_CORE035 - No Reguh entries found for the Item &1 in Batch &2

SAP Error Message - Details

• Message type: E = Error

• Message class: BNK_COM_CORE - Messages related to the core and application of Bank Comm

• Message number: 035

• Message text: No Reguh entries found for the Item &1 in Batch &2

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 BNK_COM_CORE035 - No Reguh entries found for the Item &1 in Batch &2 ?

  The SAP error message BNK_COM_CORE035 indicates that there are no regulatory entries found for a specific item in a given batch. This error typically arises in the context of financial transactions, particularly in banking or compliance-related processes where regulatory data is required for certain items.
  Cause:
  
  
  Missing Regulatory Data: The most common cause of this error is that the regulatory entries for the specified item and batch are not maintained in the system. This could be due to:
  
  Data not being uploaded or configured correctly.
  The item or batch not being set up in the regulatory framework.
  Changes in regulations that have not been reflected in the system.
  
  
  
  Incorrect Item or Batch Number: The item or batch number provided in the transaction may be incorrect or does not exist in the system.
  
  
  Configuration Issues: There may be issues with the configuration of the regulatory framework in SAP, leading to the system not being able to find the necessary entries.
  
  
  Solution:
  
  
  Check Regulatory Entries: Verify if the regulatory entries for the specified item and batch exist in the system. You can do this by:
  
  Navigating to the relevant transaction or table where regulatory data is maintained.
  Ensuring that the item and batch are correctly set up.
  
  
  
  Correct Item/Batch Number: Double-check the item and batch numbers you are using in the transaction. Ensure they are correct and exist in the system.
  
  
  Update Regulatory Data: If the regulatory entries are missing, you may need to create or update them. This could involve:
  
  Consulting with your compliance or regulatory team to ensure that the correct data is being used.
  Using the appropriate transaction codes to maintain regulatory data.
  
  
  
  Configuration Review: If the issue persists, review the configuration settings related to regulatory compliance in SAP. This may involve:
  
  Checking the settings in the relevant customizing transactions.
  Ensuring that all necessary regulatory frameworks are activated and configured correctly.
  
  
  
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance on maintaining regulatory entries for your version of SAP.
  
  
  Contact SAP Support: If you are unable to resolve the issue, consider reaching out to SAP support for assistance, especially if this is a recurring problem.
  
  
  Related Information:
  
  
  Transaction Codes: Familiarize yourself with relevant transaction codes that may help in maintaining regulatory data, such as:
  
  OBD2: For maintaining regulatory data.
  SE11: To check the data dictionary for relevant tables.
  
  
  
  SAP Notes: Check for any SAP Notes related to this error message, as they may provide specific fixes or updates.
  
  
  User Roles and Authorizations: Ensure that the user executing the transaction has the necessary authorizations to view and maintain regulatory entries.
  
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.