How To Fix KI398 - The recovery indicator is being re-derived

SAP Error Message - Details

• Message type: E = Error

• Message class: KI -

• Message number: 398

• Message text: The recovery indicator is being re-derived

<ZK>&CAUSE&</>
The account assignment was changed.

System Response

The system re-derives the recovery indicator, even though this was
previously set manually.

How to fix this error?

If the recovery indicator was set manually before account assignment,
you can now check the derivation results, if necessary, overwrite it
manually.
<ZU>Exception:</>
If you are in multiple account assignment for a purchase order, or
purchase requisition, the system automatically overwrites all manual
changes to the recovery indicator by re-deriving it.
<ZK>Manual entry of the recovery indicator is not included in multiple
account assignment</>.
Note
You can control the way this message is issued, according to user.
For more information, see the Implementation Guide (IMG) under General
Controlling,
<DS:SIMG.SIMG_CFMENUORK3OBA5>Change Message Control</>
(If required, create or maintain message no. 398 for work area "KI")
If you do not enter a user, the change applies to all users.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message KI398 - The recovery indicator is being re-derived ?

  The SAP error message KI398, which states "The recovery indicator is being re-derived," typically occurs in the context of controlling (CO) and profitability analysis (CO-PA) modules. This message indicates that the system is attempting to re-derive the recovery indicator for a particular cost object or transaction, but it is encountering issues.
  Cause:
  
  Missing Configuration: The recovery indicator may not be properly configured in the system. This can happen if the necessary settings for cost allocation or profitability analysis are not in place.
  Data Inconsistencies: There may be inconsistencies in the data that prevent the system from correctly deriving the recovery indicator. This could be due to missing or incorrect master data.
  Transaction Errors: The error may arise during the posting of transactions that involve cost allocations or profitability analysis, where the system cannot determine the correct recovery indicator.
  Changes in Master Data: If there have been recent changes to master data (like cost centers, internal orders, etc.), it may lead to issues in deriving the recovery indicator.
  
  Solution:
  
  Check Configuration: Review the configuration settings for the recovery indicator in the controlling area. Ensure that all necessary settings are correctly defined.
  Validate Master Data: Check the relevant master data for the cost objects involved. Ensure that all required fields are filled out correctly and that there are no inconsistencies.
  Review Transaction Data: Look at the specific transactions that triggered the error. Ensure that they are correctly posted and that all necessary information is available.
  Re-run the Derivation: If the issue is temporary, you may try to re-run the derivation process for the recovery indicator. This can sometimes resolve transient issues.
  Consult Documentation: Refer to SAP documentation or notes related to the KI398 error message for any specific guidance or patches that may address the issue.
  Contact SAP Support: If the problem persists, consider reaching out to SAP support for assistance. They may provide insights based on the specific configuration and data in your system.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as KSB1 (Cost Centers: Actual Line Items) or KE5Z (CO-PA: Display Line Items) to analyze the data related to the error.
  SAP Notes: Search for SAP Notes related to KI398 in the SAP Support Portal, as there may be specific fixes or recommendations provided by SAP.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the root cause of the KI398 error and implement a solution to resolve it.