How To Fix FTI213 - No aggregation information exists for issuer &1 for date &2

FTI213 - Overview

• Message type: E = Error

• Message class: FTI - Treasury Information System

• Message number: 213

• Message text: No aggregation information exists for issuer &1 for date &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 FTI213 - No aggregation information exists for issuer &1 for date &2 ?

  The SAP error message FTI213, which states "No aggregation information exists for issuer &1 for date &2," typically occurs in the context of financial transactions, particularly when dealing with financial instruments or securities in SAP's Financial Services (FS) module. This error indicates that the system cannot find the necessary aggregation data for a specific issuer on a given date.
  
  Cause:
  
  Missing Aggregation Data: The most common cause of this error is that the aggregation data for the specified issuer and date has not been created or is missing in the system.
  Incorrect Date: The date specified may not have any aggregation data available, possibly due to the data not being processed or updated for that date.
  
  Configuration Issues: There may be configuration issues in the system that prevent the aggregation data from being generated or stored correctly.
  Data Migration Issues: If data was recently migrated or imported into the system, there may have been issues