How To Fix FINS_ACDOC_CUST364 - List of company codes and ledgers checked:

SAP Error Message - Details

• Message type: E = Error

• Message class: FINS_ACDOC_CUST - Unified Journal Entry - Customizing

• Message number: 364

• Message text: List of company codes and ledgers checked:

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 FINS_ACDOC_CUST364 - List of company codes and ledgers checked: ?

  The SAP error message FINS_ACDOC_CUST364 typically indicates an issue related to the configuration of company codes and ledgers in the context of Financial Accounting (FI) and Controlling (CO) modules. This error often arises when there is a mismatch or inconsistency in the settings for company codes and ledgers, particularly when trying to post documents or execute financial transactions.
  Cause:
  
  Missing Configuration: The company code or ledger may not be properly configured in the system.
  Inconsistent Settings: There may be inconsistencies between the company code and the ledgers that are assigned to it.
  Inactive Ledger: The ledger you are trying to use may not be active for the specified company code.
  Authorization Issues: The user may not have the necessary authorizations to access the specified company code or ledger.
  Data Migration Issues: If data was migrated from another system, there may be discrepancies in the configuration.
  
  Solution:
  
  
  Check Configuration:
  
  Go to the configuration settings in SAP (Transaction Code: SPRO).
  Navigate to Financial Accounting (FI) > General Ledger Accounting > Master Data > G/L Accounts > Prepare G/L Account Creation.
  Ensure that the company code and ledger are correctly configured and linked.
  
  
  
  Verify Ledger Activation:
  
  Check if the ledger is active for the company code in the configuration settings.
  Use Transaction Code: OB22 to review the settings for ledgers and ensure they are correctly assigned to the company codes.
  
  
  
  Review Authorizations:
  
  Ensure that the user has the necessary authorizations to post to the specified company code and ledger.
  Check the user roles and profiles in Transaction Code: SU01.
  
  
  
  Check for Inconsistencies:
  
  Review the settings for the company code and ledger to ensure there are no inconsistencies.
  Use Transaction Code: FAGL3 to check the ledger settings.
  
  
  
  Consult SAP Notes:
  
  Search for relevant SAP Notes in the SAP Support Portal that may address this specific error message or provide additional troubleshooting steps.
  
  
  
  Testing:
  
  After making the necessary changes, perform a test transaction to ensure that the error no longer occurs.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SPRO (Customizing), OB22 (Ledger Settings), and SU01 (User Maintenance).
  SAP Documentation: Refer to SAP Help documentation for detailed information on configuring company codes and ledgers.
  SAP Community: Engage with the SAP Community forums for insights and solutions from other users who may have encountered similar issues.
  
  If the problem persists after following these steps, it may be beneficial to consult with your SAP Basis or FI/CO functional team for further investigation.