How To Fix BNK_COM_CORE021 - Batch status reference not selected for &1 &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: 021

• Message text: Batch status reference not selected for &1 &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_CORE021 - Batch status reference not selected for &1 &2 ?

  The SAP error message BNK_COM_CORE021 indicates that a batch status reference has not been selected for a specific batch. This error typically occurs in the context of bank communication or payment processing within the SAP system, particularly when dealing with batch processing of financial transactions.
  Cause:
  The error can arise due to several reasons:
  
  Missing Configuration: The batch status reference may not be configured in the system for the specific transaction or batch type you are trying to process.
  Incorrect Batch Input: The batch input data may not have the necessary status reference defined, leading to the system being unable to process the batch.
  Authorization Issues: There may be restrictions or missing authorizations that prevent the selection of the batch status reference.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Configuration:
  
  Navigate to the relevant configuration settings in SAP (usually found in the SPRO transaction).
  Ensure that the batch status references are correctly defined for the relevant transaction types and that they are active.
  
  
  
  Review Batch Input Data:
  
  Verify the data being used for the batch processing. Ensure that the batch input includes the necessary status reference.
  If you are using a custom program or interface, check the logic to ensure it populates the status reference correctly.
  
  
  
  Authorization Check:
  
  Ensure that the user executing the transaction has the necessary authorizations to select and process the batch status reference.
  Consult with your SAP security team if you suspect authorization issues.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to the specific transaction or module you are working with. There may be additional guidance or known issues documented.
  
  
  
  Testing:
  
  After making the necessary changes, perform a test run to ensure that the error no longer occurs and that the batch processes correctly.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FBZP (for payment program configuration) or OBPM1 (for bank master data) that may help in troubleshooting.
  SAP Notes: Check the SAP Support Portal for any notes related to the error message BNK_COM_CORE021. There may be patches or updates that address this issue.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, providing insights or solutions from other users.
  
  If the issue persists after following these steps, consider reaching out to SAP support for further assistance.