How To Fix IST_EBS300 - No unique entry in IST_EBS_POI_SYST using combination &1/&2/&3/&4

IST_EBS300 - Overview

• Message type: E = Error

• Message class: IST_EBS - Interface Between IS-T and External Billing System

• Message number: 300

• Message text: No unique entry in IST_EBS_POI_SYST using combination &1/&2/&3/&4

What causes this issue?

There is no entry, or more than one entry in the IST_EBS_POI_SYST
Customizing table (<DS:SIMG.IST_IF_POISYST>Maintain Settings for
Selection of Open Items
</>) for the current IDoc.
Either the control record of the IDoc is faulty, or the entry was not
maintained.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Check that IST_EBS_POI_SYST was maintained correctly in the following
IMG activity: <DS:SIMG.IST_IF_TOISIST>Configure Settings for Document
Transfer</>.
If it was maintained correctly, then the control record in the IDoc is
faulty.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message IST_EBS300 - No unique entry in IST_EBS_POI_SYST using combination &1/&2/&3/&4 ?

  The SAP error message IST_EBS300 indicates that there is no unique entry found in the database table IST_EBS_POI_SYST for the specified combination of parameters. This error typically arises in the context of Electronic Bank Statement (EBS) processing, where the system is trying to find a unique entry for a specific payment or transaction.
  
  Cause:
  The error can occur due to several reasons:
  
  Duplicate Entries: There may be multiple entries in the IST_EBS_POI_SYST table that match the provided combination of parameters (e.g., company code, document number, fiscal year, etc.), leading to ambiguity.
  Missing Configuration: The necessary configuration for the payment method or bank account may not be set up correctly, resulting in the system being unable to find a unique match.
  Data Integrity Issues: There may be data integrity issues in the database, such as incorrect or incomplete entries.
  
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check for Duplicates:
  
  Use transaction SE11 or SE16 to view