How To Fix 26197 - The "Change completed" indicator is not set for any status

26197 - Overview

• Message type: E = Error

• Message class: 26 - Dokumentenverwaltung

• Message number: 197

• Message text: The "Change completed" indicator is not set for any status

What causes this issue?

Before you can release an engineering change order (ECO) for subsequent
applications, changes to all change objects (such as bills of material,
routings, and documents) must be complete and released.
The status of a document determines whether a document is <zh>complete
</> in this sense. If you set a document status that has the
<DS:DE.FRTAE>Complete for engineering change mgmt</> indicator set in
Customizing, the system reads the document as <ZH>released</> for
engineering change management purposes.

System Response

How to fix this error?

No status for the document type you are using has the
<DS:DE.FRTAE>Complete for engineering change mgmt</> indicator, so
this warning message appears.
If you want to assign documents of this document type to an ECO, define
a status that has this indicator. Otherwise you will not be able to
release ECOs that contain documents of this document type.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 26197 - The "Change completed" indicator is not set for any status ?

  The SAP error message 26197, which states "The 'Change completed' indicator is not set for any status," typically occurs in the context of change management or status management within SAP systems, particularly in modules like SAP Project System (PS) or SAP Change Request Management (ChaRM).
  
  Cause:
  This error usually arises when a user attempts to perform an action that requires a specific status to be marked as "Change completed," but no such status has been defined or set in the system. This can happen due to:
  
  Missing Configuration: The status profile may not have been properly configured to include a "Change completed" status.
  Incorrect Status Transition: The workflow or process may not have been followed correctly, leading to a situation where the system expects a status to be set but it is not.
  User Authorization: The user may not have the necessary permissions to set the status, leading to the inability to mark changes as