How To Fix ACM255 - Upgrade running: Changes in ACM are locked (decision taken by rule &1)

SAP Error Message - Details

• Message type: E = Error

• Message class: ACM - Message-Class for all ACM functions/exceptions

• Message number: 255

• Message text: Upgrade running: Changes in ACM are locked (decision taken by rule &1)

What causes this issue?

An upgrade is currently ongoing.
In this phase, changes performed by code of Access Control Management
must be locked as they interfere with actions performed by the upgrade.
This error message indicates that you have started an ACM action in the
upgrade phase (initial load, activation of artifacts, object repairs).

System Response

The action has been canceled.

How to fix this error?

Wait for the upgrade to be finished.

Procedure for System Administrators

The detection code uses rules.
The following rule is always executed: When the development environment
is not locked against changes, changes are allowed. This rule allows
cleanup activities when during an upgrade, pre-checks (for example the
search for inactive objects) trigger and the upgrade process temporarily
opens the development environment to resolve these obstacles.
Otherwise, the following reasons exist why changes to the access control
management database tables are currently not allowed:
Rule A: The system is currently in upgrade (and none of the rules below
has triggered).
Rule B: The system is currently in ZDO ("Zero Downtime Option") upgrade,
and the current system is the "Bridge-System".
Rule C: The system is currently in upgrade. The current system is the
original system where no more changes are allowed, while in the shadow
system the upgrade process commences.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message ACM255 - Upgrade running: Changes in ACM are locked (decision taken by rule &1) ?

  The SAP error message ACM255 indicates that there are changes in the Activity Cost Management (ACM) module that are currently locked due to a decision taken by a specific rule. This typically occurs during an upgrade or when trying to make changes in the system that are not allowed due to existing locks.
  Cause:
  
  Locked Changes: The error arises when there are changes in the ACM that are locked because of a decision made by a specific rule. This could be due to ongoing processes, such as an upgrade or a transaction that is currently being processed.
  Configuration Issues: There may be configuration settings that prevent changes from being made until certain conditions are met.
  Concurrent Processes: Other users or processes may be accessing or modifying the same data, leading to a lock.
  
  Solution:
  
  Check Locks: Use transaction code SM12 to check for any existing locks on the relevant tables or objects. If you find locks that are no longer needed, you can delete them (ensure that you have the necessary authorizations and that it is safe to do so).
  Review Configuration: Check the configuration settings in the ACM module to ensure that they are set correctly and that there are no restrictions preventing changes.
  Wait for Processes to Complete: If the error is due to concurrent processes, you may need to wait for those processes to complete before attempting to make changes again.
  Consult Documentation: Review SAP documentation or notes related to ACM and the specific rule mentioned in the error message for further insights.
  Contact SAP Support: If the issue persists and you cannot identify the cause, consider reaching out to SAP support for assistance. Provide them with the error message and any relevant details about your system and the actions you were attempting to perform.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM12 (to check locks), SE11 (to view table definitions), and SE80 (to access the object navigator).
  SAP Notes: Search for SAP Notes related to ACM and the specific error message for any patches or updates that may address the issue.
  System Logs: Check system logs (transaction SM21) for any additional error messages or warnings that may provide more context about the issue.
  
  By following these steps, you should be able to diagnose and resolve the ACM255 error in your SAP system.