How To Fix FR322 - G/L account & not created in company code &

SAP Error Message - Details

• Message type: E = Error

• Message class: FR - Messages for FI Reporting

• Message number: 322

• Message text: G/L account & not created in company code &

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 FR322 - G/L account & not created in company code & ?

  The SAP error message FR322 indicates that a General Ledger (G/L) account has not been created for a specific company code. This error typically arises when you attempt to post a transaction to a G/L account that is not defined for the specified company code in the system.
  Cause:
  
  Missing G/L Account: The G/L account you are trying to use has not been created in the specified company code.
  Incorrect Company Code: The transaction may be referencing the wrong company code.
  Account Group Settings: The account group associated with the G/L account may not allow the creation of accounts in the specified company code.
  Data Migration Issues: If data was migrated from another system, the G/L accounts may not have been properly set up in the new environment.
  
  Solution:
  
  
  Create the G/L Account:
  
  Navigate to the transaction code FS00 (G/L Account Master Record).
  Enter the required details, including the company code and the G/L account number.
  Ensure that all necessary fields are filled out correctly and save the record.
  
  
  
  Check Company Code:
  
  Verify that you are using the correct company code in your transaction. You can check this in the transaction you are trying to execute.
  
  
  
  Review Account Group Settings:
  
  Check the account group settings to ensure that the G/L account can be created for the specified company code. You can do this in transaction code OBD4 (Define Account Groups).
  
  
  
  Consult with Your SAP Administrator:
  
  If you do not have the necessary permissions to create G/L accounts, contact your SAP administrator or finance team to assist with the creation.
  
  
  
  Check for Data Migration Issues:
  
  If this issue arose after a data migration, review the migration process to ensure that all necessary G/L accounts were created in the target system.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  FS00: Create/Change G/L Account Master Record
  OBD4: Define Account Groups
  OBY6: Define Company Code
  
  
  Documentation: Refer to SAP Help documentation for detailed steps on creating G/L accounts and managing company codes.
  User Roles: Ensure that the user has the appropriate roles and authorizations to create or modify G/L accounts.
  
  By following these steps, you should be able to resolve the FR322 error and successfully post your transactions.