How To Fix >1065 - Final character &1/card type &2/company code &3 locked

SAP Error Message - Details

• Message type: E = Error

• Message class: >1 - Shockwave SAPGUI message handling

• Message number: 065

• Message text: Final character &1/card type &2/company code &3 locked

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 >1065 - Final character &1/card type &2/company code &3 locked ?

  The SAP error message 1065 indicates that a specific character (or account) is locked for a particular card type and company code. This typically occurs in the context of financial transactions or master data management, where certain accounts or characters are restricted from being used due to various reasons, such as data integrity, compliance, or administrative controls.
  Cause:
  
  
  Account Locking: The account or character you are trying to access is locked for the specified card type and company code. This could be due to:
  
  Administrative actions (e.g., the account was intentionally locked by a user).
  Data integrity checks that prevent the use of certain accounts.
  The account being in a closed period or being marked for deletion.
  
  
  
  Configuration Issues: There may be configuration settings in the system that restrict access to certain accounts based on specific criteria.
  
  
  User Permissions: The user attempting to access the account may not have the necessary permissions to unlock or use the account.
  
  
  Solution:
  
  
  Unlock the Account: If you have the necessary permissions, you can unlock the account by:
  
  Navigating to the relevant transaction (e.g., FS00 for G/L accounts) and checking the status of the account.
  If the account is locked, you can unlock it by changing the status in the account settings.
  
  
  
  Check Configuration: Review the configuration settings related to account locking in your SAP system. This may involve checking the settings in the Financial Accounting (FI) module or consulting with your SAP administrator.
  
  
  User Permissions: Ensure that the user has the appropriate permissions to access the account. This may involve checking user roles and authorizations in the SAP system.
  
  
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance on handling locked accounts and the implications of unlocking them.
  
  
  Contact Support: If you are unable to resolve the issue, consider reaching out to your SAP support team or consulting with SAP support for further assistance.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FS00 (G/L Account Master Data), OB52 (Open and Close Posting Periods), and SU01 (User Maintenance) for managing accounts and user permissions.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Audit and Compliance: Be aware of the implications of unlocking accounts, especially in regulated environments, as it may affect financial reporting and compliance.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.