How To Fix KQ142 - Status no. of status FNBL must be lower than that of status TECO

KQ142 - Overview

• Message type: E = Error

• Message class: KQ - Error Messages for Customizing Product Costing

• Message number: 142

• Message text: Status no. of status FNBL must be lower than that of status TECO

What causes this issue?

The valuation method for <DS:GLOS.results_analysis>results analysis</>
or for the calculation of <DS:GLOS.work_in_process>work in process</>
(WIP) is selected through the status of the order or project. If more
than one status is set for the order or project when you perform
results analysis or <DS:GLOS.WIP_calculation>WIP calculation</>, the
system uses the status numbers to select the valuation method.
In your case, you entered a status number for the status <ZH>Final
billing</> that is higher than or the same as the status number for the
status <ZH>Technically completed</>. However, the user sets the status
Final billing <ZH>before</> the status Technically completed.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Check the status number for the status <ZH>Technically completed</> and
change the status number of the status <ZH>Final billing</>.

Error message extract from SAP system. Copyright SAP SE.

KQ142 - Details

• The SAP error message KQ142, which states "Status no. of status FNBL must be lower than that of status TECO," typically occurs in the context of project management or production order processing within SAP. This error indicates that there is a status conflict between the statuses assigned to a project or order.
  
  Cause:
  
  Status Hierarchy Violation: In SAP, statuses are often assigned a hierarchy. The status "FNBL" (Final Billing) is expected to have a lower status number than "TECO" (Technically Completed). If the system detects that the status number for FNBL is not lower than that for TECO, it triggers this error.
  Incorrect Status Assignment: The statuses may have been incorrectly assigned or updated in the system, leading to this conflict.
  
  Configuration Issues: There may be issues in the configuration of status profiles in the system, which define the allowed status transitions.
  
  
  Solution:
  
  Check Status Assignment: Review the status assignments for the project or order in