How To Fix OE990 - Ranking of TAS Relevance fields not maintained

SAP Error Message - Details

• Message type: E = Error

• Message class: OE - IS-Oil: ITA/TPI messages

• Message number: 990

• Message text: Ranking of TAS Relevance fields not maintained

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 OE990 - Ranking of TAS Relevance fields not maintained ?

  The SAP error message "OE990 Ranking of TAS Relevance fields not maintained" typically occurs in the context of the SAP system's handling of Tax Accounting System (TAS) relevance fields. This error indicates that the system is unable to determine the ranking of the TAS relevance fields, which is necessary for processing certain transactions or reports.
  Cause:
  
  Missing Configuration: The ranking of TAS relevance fields has not been properly configured in the system. This can happen if the necessary settings were not completed during the initial setup or if changes were made to the configuration without updating the ranking.
  Inconsistent Data: There may be inconsistencies or missing entries in the relevant configuration tables that define how TAS relevance fields should be ranked.
  Transport Issues: If the configuration was transported from one system to another (e.g., from development to production), there may have been issues during the transport process that led to incomplete or missing settings.
  
  Solution:
  
  
  Check Configuration: 
  
  Navigate to the relevant configuration settings in the SAP system. This is typically found in the IMG (Implementation Guide) under Financial Accounting (FI) or Tax Accounting.
  Ensure that the TAS relevance fields are properly defined and that their rankings are maintained.
  You may need to consult with your SAP FI consultant or system administrator to verify the settings.
  
  
  
  Maintain Ranking:
  
  If the ranking is missing, you will need to maintain it. This usually involves defining the order of importance for the TAS relevance fields in the configuration settings.
  Use transaction codes like SPRO to access the configuration settings and make the necessary adjustments.
  
  
  
  Check for Transport Issues:
  
  If the configuration was recently transported, check the transport logs for any errors or warnings that may indicate issues with the transport.
  If necessary, re-transport the configuration or manually adjust the settings in the target system.
  
  
  
  Testing: 
  
  After making the necessary changes, perform tests to ensure that the error no longer occurs and that the system behaves as expected.
  
  
  
  Related Information:
  
  Documentation: Refer to SAP documentation or help guides related to Tax Accounting System configuration for detailed steps on maintaining TAS relevance fields.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  If the issue persists after following these steps, it may be beneficial to reach out to SAP support for further assistance.