How To Fix FTI325 - Price found is older than 999 days for security &1 on &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FTI - Treasury Information System

• Message number: 325

• Message text: Price found is older than 999 days for security &1 on &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 FTI325 - Price found is older than 999 days for security &1 on &2 ?

  The SAP error message FTI325 indicates that the price for a specific security (denoted as &1) is older than 999 days on a specific date (denoted as &2). This error typically arises in the context of financial transactions, particularly when dealing with securities pricing in SAP's Financial Accounting (FI) or Treasury modules.
  Cause:
  
  Outdated Pricing Data: The primary cause of this error is that the system is trying to retrieve a price for a security that has not been updated in the system for over 999 days. This can happen if the security is not actively traded or if the pricing data has not been maintained properly.
  Data Maintenance Issues: There may be issues with the data maintenance processes, such as missing updates or incorrect data entry.
  Configuration Settings: The system may have specific settings that limit the age of price data that can be used for transactions.
  
  Solution:
  
  
  Update Pricing Data: The most straightforward solution is to update the pricing data for the affected security. This can be done by:
  
  Manually entering the latest price for the security in the system.
  Importing updated pricing data from a reliable source if your organization has a process for this.
  
  
  
  Check Data Maintenance Procedures: Review the procedures in place for maintaining security prices. Ensure that there is a regular update process to keep the pricing data current.
  
  
  Review Configuration Settings: Check the configuration settings in SAP related to price data validity. If necessary, adjust the settings to allow for older prices to be used, but be cautious as this may have implications for data accuracy.
  
  
  Consult with Financial Analysts: If the security is not actively traded, consult with financial analysts or relevant stakeholders to determine if the security should still be included in the system or if it should be marked as inactive.
  
  
  Use Alternative Pricing Sources: If the security is no longer actively traded, consider using alternative pricing sources or methodologies to value the security.
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes such as SE38 (ABAP Editor) or SE11 (Data Dictionary) to check the underlying data or reports related to securities pricing.
  Documentation: Refer to SAP documentation or help files for more detailed information on managing securities and pricing data.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance on handling outdated pricing data.
  
  By following these steps, you should be able to resolve the FTI325 error and ensure that your pricing data for securities is up to date.