How To Fix FI_AGING_PROTOCOL090 - System error; CPU date missing

SAP Error Message - Details

• Message type: E = Error

• Message class: FI_AGING_PROTOCOL - The message text is used in logging during aging run

• Message number: 090

• Message text: System error; CPU date missing

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 FI_AGING_PROTOCOL090 - System error; CPU date missing ?

  The SAP error message "FI_AGING_PROTOCOL090 System error; CPU date missing" typically indicates that there is a problem with the configuration or data related to the aging protocol in the Financial Accounting (FI) module. This error suggests that the system is unable to find the necessary CPU date, which is essential for processing aging reports or protocols.
  Causes:
  
  Missing Configuration: The CPU date may not be set up correctly in the system configuration.
  Data Inconsistency: There may be inconsistencies in the data that the aging protocol relies on, such as missing or incorrect entries in the relevant tables.
  System Issues: There could be underlying system issues, such as database problems or issues with the application server.
  User Authorization: The user may not have the necessary authorizations to access the required data.
  
  Solutions:
  
  
  Check Configuration:
  
  Verify the configuration settings for the aging protocol in the SAP system. Ensure that all necessary parameters are correctly set.
  Check the settings in transaction codes like OAA3 (for asset accounting) or other relevant configuration transactions.
  
  
  
  Review Data:
  
  Check the relevant tables for missing or incorrect entries. You can use transaction codes like SE16 or SE11 to view the data in the tables related to aging protocols.
  Ensure that all necessary data is populated and that there are no gaps.
  
  
  
  System Check:
  
  Perform a system check to ensure that there are no underlying issues with the database or application server.
  Check the system logs (transaction SM21) for any related errors or warnings that could provide more context.
  
  
  
  User Authorization:
  
  Ensure that the user encountering the error has the necessary authorizations to access the aging protocol and related data.
  
  
  
  Consult SAP Notes:
  
  Search for relevant SAP Notes in the SAP Support Portal that may address this specific error. There may be patches or updates available that resolve the issue.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP Support for further assistance. Provide them with detailed information about the error, including any relevant logs or screenshots.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  SE16: Data Browser
  SE11: Data Dictionary
  SM21: System Log
  OAA3: Asset Accounting Configuration
  
  
  Documentation: Review SAP documentation related to the FI module and aging protocols for additional insights and best practices.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution.