How To Fix EPIC_BANK_COMM115 - Cannot get output table result; structure not maintained in Customizing

SAP Error Message - Details

• Message type: E = Error

• Message class: EPIC_BANK_COMM - Message Class for BACO PROG

• Message number: 115

• Message text: Cannot get output table result; structure not maintained in Customizing

What causes this issue?

The system has tried to process a response from your bank, but the
system cannot find the Customizing settings needed to display the
results.

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?

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_COMM115 - Cannot get output table result; structure not maintained in Customizing ?

  The SAP error message EPIC_BANK_COMM115 indicates that there is an issue with the output table structure not being maintained in the Customizing settings for the bank communication module. This error typically arises when the system is unable to retrieve the necessary output table structure for processing bank communication data.
  Cause:
  
  Missing Customizing Settings: The output table structure required for the bank communication process has not been defined or maintained in the Customizing settings.
  Incorrect Configuration: There may be incorrect or incomplete configuration settings related to bank communication in the SAP system.
  Transport Issues: If the configuration was recently transported from another system, it may not have been properly set up in the target system.
  Version Mismatch: The version of the bank communication module may not be compatible with the current configuration.
  
  Solution:
  
  
  Check Customizing Settings:
  
  Navigate to the relevant Customizing transaction (usually in SPRO) for bank communication.
  Ensure that the output table structure is defined and maintained correctly.
  Look for the specific settings related to the output format you are trying to use.
  
  
  
  Maintain Output Table Structure:
  
  If the output table structure is missing, you may need to create or maintain it. This can involve defining the fields and their data types that are required for the output.
  
  
  
  Review Configuration:
  
  Go through the configuration steps for bank communication to ensure that all necessary settings are completed.
  Check for any documentation or guidelines provided by SAP for the specific version you are using.
  
  
  
  Transport Requests:
  
  If the issue arose after a transport, check the transport logs to ensure that all necessary objects were included and correctly imported.
  If needed, re-import the transport request or manually adjust the settings in the target system.
  
  
  
  Consult SAP Notes:
  
  Search for relevant SAP Notes that may address this specific error message. SAP frequently releases notes that provide fixes or workarounds for known issues.
  
  
  
  Testing:
  
  After making changes, perform tests to ensure that the output table is now being generated correctly without errors.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SPRO (Customizing), SE11 (Data Dictionary), and SE80 (Object Navigator) for checking and maintaining table structures.
  Documentation: Review SAP documentation related to bank communication and output processing for additional insights and best practices.
  Support: If the issue persists, consider reaching out to SAP support or consulting with a technical expert who specializes in SAP bank communication.
  
  By following these steps, you should be able to resolve the EPIC_BANK_COMM115 error and ensure that the output table structure is properly maintained in your SAP system.