How To Fix /PRA/ACCOUNTING105 - Account ID not found in SKB1 table

/PRA/ACCOUNTING105 - Overview

• Message type: E = Error

• Message class: /PRA/ACCOUNTING -

• Message number: 105

• Message text: Account ID not found in SKB1 table

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.

/PRA/ACCOUNTING105 - Details

• The SAP error message /PRA/ACCOUNTING105 Account ID not found in SKB1 table typically indicates that the system is unable to find the specified account ID in the SKB1 table, which is the table that stores the G/L account master data for company codes.
  
  Cause:
  
  Non-Existent Account ID: The account ID you are trying to access or use does not exist in the SKB1 table for the specified company code.
  Incorrect Company Code: The account ID may exist, but it is not assigned to the company code you are working with.
  Data Deletion: The account may have been deleted or marked for deletion in the system.
  Authorization Issues: The user may not have the necessary authorizations to view or access the account ID.
  
  Configuration Issues: There may be issues with the configuration of the G/L accounts in the system.
  
  
  Solution:
  
  Verify Account ID: Check if the account ID you are using is correct. Ensure that there are no typos