How To Fix ACC_AA320 - Project &1, chart of depreciation &2: Lock company code &3

SAP Error Message - Details

• Message type: E = Error

• Message class: ACC_AA - Message Class for Function Group ACC_AA

• Message number: 320

• Message text: Project &1, chart of depreciation &2: Lock company code &3

What causes this issue?

During the execution phase, you must ensure that no postings can take
place or changes can be made to the asset master records in Asset
Accounting. As soon as you finish the preparatory phase, the system
automatically sets a lock.
The lock however is <ZH>no longer</> active for company code &V3& or
<ZH>not yet</> active.

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?

Make sure that the lock for company code &V3& is set in Customizing for
<LS>Asset Accounting</> under <DS:SIMG.T093C_LOCK_DC>Lock Company Code
Against Changes in Asset Accounting</>.
Note:
If you are in the preparation phase in your Customizing system and have
<ZH>not yet</> finished this, it is <ZH>not yet</> absolutely necessary
that the lock is set.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message ACC_AA320 - Project &1, chart of depreciation &2: Lock company code &3 ?

  The SAP error message ACC_AA320 typically indicates that there is a lock on a company code that is preventing certain actions related to asset accounting, particularly in the context of projects and depreciation. Here’s a breakdown of the cause, potential solutions, and related information for this error:
  Cause:
  
  
  Lock on Company Code: The error suggests that the company code specified in the message is locked for certain operations. This could be due to:
  
  Ongoing financial closing activities (e.g., month-end or year-end closing).
  A user or process has locked the company code for maintenance or other operations.
  Configuration settings that restrict access to the company code.
  
  
  
  Project-Specific Issues: The project mentioned in the error may have specific settings or statuses that are causing the lock.
  
  
  Solution:
  
  
  Check Lock Status:
  
  Use transaction code SM12 to check for any locks on the company code. Look for entries related to the company code in question and identify the user or process that has locked it.
  
  
  
  Release Locks:
  
  If you identify a lock that is no longer needed, you can release it. However, be cautious and ensure that releasing the lock will not disrupt ongoing processes.
  
  
  
  Review Financial Closing Activities:
  
  If the lock is due to financial closing activities, you may need to wait until the closing process is completed. Check with your finance team to understand the timeline for closing activities.
  
  
  
  Check Project Settings:
  
  Review the project settings in the Project System (PS) module to ensure that there are no restrictions or issues that could be causing the lock.
  
  
  
  Consult with SAP Basis Team:
  
  If you are unable to resolve the issue, consult with your SAP Basis team or system administrator. They may have additional tools or insights to help diagnose and resolve the lock.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SM12: To check and manage locks.
  SE11: To view the data dictionary and check table structures related to asset accounting.
  CJ20N: To view and manage project-related data.
  
  
  
  Documentation: Refer to SAP Help documentation for Asset Accounting and Project System for more detailed information on handling locks and project settings.
  
  
  User Roles and Authorizations: Ensure that the user attempting the action has the necessary authorizations to perform operations on the specified company code and project.
  
  
  By following these steps, you should be able to identify the cause of the ACC_AA320 error and take appropriate actions to resolve it.