How To Fix EPIC_BANK_COMM116 - Cannot get output table result; list type differs from Customizing

EPIC_BANK_COMM116 - Overview

• Message type: E = Error

• Message class: EPIC_BANK_COMM - Message Class for BACO PROG

• Message number: 116

• Message text: Cannot get output table result; list type differs from Customizing

What causes this issue?

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

System Response

The system has tried to process a response from your bank, but the
results differ from the Customizing settings that the system needs to
display the results.

How to fix this error?

Procedure for System Administrators

Check that you have entered the correct table output structure for this
bank communication type in the
<DS:SIMG.EPIC_C_BCDV>Define Bank Communication Details</> Customizing
activity.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message EPIC_BANK_COMM116 - Cannot get output table result; list type differs from Customizing ?

  The SAP error message EPIC_BANK_COMM116 indicates that there is a mismatch between the expected output table structure and the actual structure defined in the Customizing settings. This error typically arises in the context of bank communication or payment processing, where the system expects a certain format for the output data but receives a different one.
  
  Cause:
  
  Mismatch in Data Structure: The output table structure defined in the Customizing settings does not match the structure of the data being processed. This could be due to changes in the data model or updates in the configuration.
  Incorrect Customizing Settings: The settings in the Customizing transaction (such as transaction code OBPM1 for bank communication) may not be correctly configured to match the expected output.
  Version Compatibility: If there have been recent updates or changes to the SAP system, the output format may have changed, leading to this error.
  Data Type Issues: The data types of the fields in