Message type: E = Error
Message class: AA - Messages for Asset Accounting
Message number: 595
Message text: Company code &1 locked against changes
Company code &V1& is locked against changes in Asset Accounting.
The system does <ZH>not</> allow <ZH>any</> postings or any master
record changes in this company code due to Customizing settings.
You can make changes again once the lock for this company code has been
removed.
The lock can be removed in Customizing for <LS>Asset Accounting</> under
<DS:SIMG.T093C_LOCK_DC>Lock Company Code Against Changes in Asset
Accounting</>.
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.
The SAP error message AA595, which states "Company code &1 locked against changes," typically occurs when there are restrictions on making changes to a specific company code in the Asset Accounting (AA) module. This can happen for various reasons, such as configuration settings, user authorizations, or ongoing processes that lock the company code.
Causes:
Company Code Locking: The company code may be locked for changes due to specific settings in the system. This can be a result of:
- Year-end closing processes.
- Period-end closing processes.
- Configuration settings that prevent changes during certain periods.
User Authorizations: The user attempting to make changes may not have the necessary authorizations to modify the company code settings.
Ongoing Transactions: There may be ongoing transactions or processes that are currently using the company code, preventing changes.
Solutions:
Check Company Code Status:
- Verify if the company code is locked for changes. This can be checked in the configuration settings of the Asset Accounting module.
- Navigate to the configuration path: SPRO > Financial Accounting > Asset Accounting > Master Data > Company Code > Define Company Code and check the status.
Unlock the Company Code:
- If the company code is locked due to year-end or period-end closing, you may need to wait until those processes are completed.
- If you have the necessary authorizations, you can unlock the company code by changing the settings in the configuration.
Check User Authorizations:
- Ensure that the user has the appropriate authorizations to make changes to the company code. This can be checked with your SAP security team or by reviewing the user roles assigned.
Review Ongoing Processes:
- Check if there are any ongoing transactions or processes that might be locking the company code. This could include open periods in financial accounting or asset transactions that are being processed.
Consult Documentation:
- Refer to SAP documentation or support notes related to error message AA595 for additional context and troubleshooting steps.
Related Information:
OAOA
(for Asset Accounting settings) or OB52
(for open/close posting periods) to check and modify settings related to the company code.By following these steps, you should be able to identify the cause of the error and implement the necessary solutions to resolve it.
Sign up takes 1 minute. 7-day free trial.
AA594 Errors occurred for asset & in fiscal year &
Self-Explanatory Message Since SAP believes that this specific error message is ...
AA593 No authorization for company code &
The system issues an error message and will not allow you to continue with this...
AA596 Specify an area for value transfer
Self-Explanatory Message Since SAP believes that this specific error message is ...
AA597 Area &2 in company code &1 created at asset level
Self-Explanatory Message Since SAP believes that this specific error message is ...
SAP messages fall into 3 different categories: Error messages
(message type = E), Warnings (W) or Informational (I) messages.
An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.
Click on this link to search all SAP messages.