How To Fix FICASEPA_EMSG023 - External transaction & not maintained in TFK028G for returns

SAP Error Message - Details

• Message type: E = Error

• Message class: FICASEPA_EMSG - Error Message for Status report SEPA XML

• Message number: 023

• Message text: External transaction & not maintained in TFK028G for returns

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 FICASEPA_EMSG023 - External transaction & not maintained in TFK028G for returns ?

  The SAP error message FICASEPA_EMSG023 indicates that an external transaction code is not maintained in the table TFK028G for returns. This error typically arises in the context of electronic bank statement processing, particularly when dealing with SEPA (Single Euro Payments Area) transactions.
  Cause:
  The error occurs when the system attempts to process a return transaction (like a returned direct debit) but cannot find the corresponding external transaction code in the configuration table TFK028G. This table is used to map external transaction codes to internal transaction types in SAP.
  Solution:
  To resolve this error, you need to maintain the external transaction code in the TFK028G table. Here are the steps to do this:
  
  
  Access the TFK028G Table:
  
  Use transaction code SE16N or SE11 to access the table TFK028G.
  
  
  
  Check Existing Entries:
  
  Look for the external transaction code that is causing the error. If it does not exist, you will need to create a new entry.
  
  
  
  Create a New Entry:
  
  If the external transaction code is missing, you can add it by following these steps:
  
  Click on the "New Entries" button.
  Enter the required details:
  
  External Transaction Code: The code that is causing the error.
  Transaction Type: The corresponding internal transaction type that should be used for processing.
  Other relevant fields as required.
  
  
  Save your changes.
  
  
  
  
  
  Test the Changes:
  
  After maintaining the entry, try to reprocess the transaction that caused the error to see if the issue is resolved.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with the relevant transaction codes for managing bank statements and SEPA transactions, such as FF67 (for manual bank statement processing) and FF.5 (for electronic bank statement processing).
  Documentation: Review SAP documentation or help files related to electronic bank statement processing and SEPA configuration for additional context and best practices.
  Authorization: Ensure you have the necessary authorizations to make changes to the configuration tables in SAP.
  
  If the issue persists after making the necessary changes, consider consulting with your SAP support team or a functional consultant who specializes in financial accounting and bank statement processing.