How To Fix R$147 - G/L account always required - item with date &1

SAP Error Message - Details

• Message type: E = Error

• Message class: R$ -

• Message number: 147

• Message text: G/L account always required - item with date &1

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 R$147 - G/L account always required - item with date &1 ?

  The SAP error message R$147 "G/L account always required - item with date &1" typically occurs when you are trying to post a transaction in SAP that requires a General Ledger (G/L) account, but the system cannot find a valid G/L account for the transaction. This error is common in various financial transactions, such as journal entries, invoice postings, or other accounting-related activities.
  Cause:
  
  Missing G/L Account: The most common cause is that the G/L account is not specified in the transaction. This can happen if the account is not maintained in the relevant master data or if the account is not assigned to the transaction type you are trying to post.
  Incorrect Configuration: The configuration settings for the document type or posting area may not be set up correctly, leading to the requirement for a G/L account not being met.
  Posting Date Issues: The date specified in the error message may relate to a period that is closed or not open for posting, which can also lead to issues with G/L account determination.
  Account Determination Issues: If the system is unable to determine the correct G/L account based on the configuration (e.g., account determination settings), this error can occur.
  
  Solution:
  
  Check G/L Account: Ensure that a valid G/L account is specified in the transaction. If you are using a specific transaction code, make sure that the G/L account is correctly entered in the relevant field.
  Review Master Data: Verify that the G/L account exists in the system and is active. Check the account's status and ensure it is not blocked or inactive.
  Configuration Settings: Review the configuration settings for the document type and posting area. Ensure that the settings allow for the posting of the transaction type you are attempting.
  Posting Period: Check the posting period to ensure that it is open for the date specified in the error message. If the period is closed, you may need to open it or post to a different period.
  Account Determination: If applicable, review the account determination settings in the configuration to ensure that the system can correctly determine the G/L account based on the transaction type and other criteria.
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like FS00 (G/L Account Master Data), OB52 (Open and Close Posting Periods), or SPRO (SAP Reference IMG) to access configuration settings.
  Documentation: Refer to SAP documentation or help files for more detailed information on G/L account postings and error messages.
  Support: If the issue persists, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.