How To Fix FAA_MD064 - Company code &1 is in process; please unlock it first

SAP Error Message - Details

• Message type: E = Error

• Message class: FAA_MD - Fixed Asset Master

• Message number: 064

• Message text: Company code &1 is in process; please unlock it first

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message FAA_MD064 - Company code &1 is in process; please unlock it first ?

  The SAP error message FAA_MD064 indicates that a specific company code is currently locked for processing in the Asset Accounting (FI-AA) module. This typically occurs when there are ongoing transactions or processes that are preventing changes or updates to the asset data for that company code.
  Cause:
  
  Ongoing Processes: The company code may be involved in ongoing processes such as asset acquisitions, transfers, or retirements that have not been completed.
  Locking Mechanism: SAP uses a locking mechanism to prevent data inconsistencies. If a user or a background job is currently processing data for that company code, it will be locked.
  User Sessions: Sometimes, a user may have an open session that is holding a lock on the company code.
  
  Solution:
  
  
  Check for Ongoing Processes: 
  
  Review any ongoing transactions related to the company code. You can check transaction codes like AW01N (Asset Explorer) or AS03 (Display Asset) to see if there are any pending transactions.
  
  
  
  Unlock the Company Code:
  
  If you have the necessary authorizations, you can unlock the company code by completing or canceling the ongoing processes.
  If you are unsure about the processes, consult with your SAP administrator or the relevant team to identify and resolve the issue.
  
  
  
  Use Transaction SM12:
  
  You can use transaction SM12 to check for any locks on the company code. This transaction allows you to view and delete locks held by users. Be cautious when deleting locks, as it may affect ongoing processes.
  
  
  
  Check Background Jobs:
  
  Use transaction SM37 to check for any background jobs that might be running and holding locks on the company code. If you find any relevant jobs, you may need to wait for them to complete or consult with the job owner.
  
  
  
  Consult Documentation: 
  
  Review SAP documentation or consult with your SAP support team for specific guidance related to your organization's configuration and processes.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as AW01N, AS03, SM12, and SM37.
  User Roles and Authorizations: Ensure that you have the necessary permissions to view and unlock company codes.
  SAP Notes: Check for any SAP Notes related to this error message for additional troubleshooting steps or patches that may be applicable.
  
  If the issue persists after following these steps, it may be necessary to escalate the matter to your SAP support team for further investigation.