How To Fix WN120 - No standard accounts exist for chart of accounts & in company code &

SAP Error Message - Details

• Message type: E = Error

• Message class: WN - Plant master data maintenance (integrated)

• Message number: 120

• Message text: No standard accounts exist for chart of accounts & 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 WN120 - No standard accounts exist for chart of accounts & in company code & ?

  The SAP error message WN120 indicates that there are no standard accounts defined for the specified chart of accounts and company code. This error typically occurs when you are trying to perform a transaction that requires standard accounts, such as posting a financial document, but the system cannot find the necessary account definitions.
  Cause:
  
  Missing Standard Accounts: The standard accounts for the specified chart of accounts and company code have not been created or configured.
  Incorrect Configuration: The chart of accounts may not be properly assigned to the company code.
  Data Migration Issues: If data was migrated from another system, the standard accounts may not have been included in the migration.
  Customizations: Custom configurations or modifications may have inadvertently removed or altered the standard accounts.
  
  Solution:
  To resolve the WN120 error, you can follow these steps:
  
  
  Check Chart of Accounts Assignment:
  
  Go to the transaction code OBY6 (or navigate through the menu: SPRO > Financial Accounting > General Ledger > Master Data > G/L Accounts > Prepare G/L Account Creation).
  Ensure that the chart of accounts is correctly assigned to the company code.
  
  
  
  Create Standard Accounts:
  
  Use transaction code FS00 to create the necessary standard accounts.
  Ensure that you create the accounts with the correct account type (e.g., balance sheet, P&L) and assign them to the appropriate chart of accounts.
  
  
  
  Review Account Group Settings:
  
  Check the account group settings to ensure that the necessary account groups are defined and linked to the chart of accounts.
  
  
  
  Check for Data Migration Issues:
  
  If you recently migrated data, verify that all necessary accounts were included in the migration process. You may need to re-import or create missing accounts.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or consult with your SAP support team for specific guidelines related to your version and configuration.
  
  
  
  Testing:
  
  After making the necessary changes, perform a test transaction to ensure that the error has been resolved.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  OBY6: Assign Chart of Accounts to Company Code
  FS00: Create/Change G/L Account
  OBD4: Define Account Groups
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  User Roles: Ensure that you have the necessary authorizations to create or modify G/L accounts.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis or functional team for further investigation.