How To Fix 1G593 - Account &1 &2 not selected as accrual dt &3 = GL transfer dt &4

SAP Error Message - Details

• Message type: E = Error

• Message class: 1G - BKK: Konditionen

• Message number: 593

• Message text: Account &1 &2 not selected as accrual dt &3 = GL transfer dt &4

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 1G593 - Account &1 &2 not selected as accrual dt &3 = GL transfer dt &4 ?

  The SAP error message 1G593 indicates that a specific account (denoted by &1 and &2) is not selected for accrual processing for the given dates (accrual date &3 and GL transfer date &4). This error typically arises during the execution of financial transactions, particularly in the context of accrual accounting.
  Cause:
  
  Account Configuration: The account in question may not be configured to allow accruals. This could be due to settings in the account master data or in the configuration of the financial module.
  Posting Period: The posting period for the accrual may not be open, or the dates provided may not align with the allowed posting periods.
  Transaction Type: The transaction type being used may not be compatible with accruals for the specified account.
  Missing Accruals: The system may not have been set up to recognize the account for accruals, which could be due to missing configuration in the relevant financial settings.
  
  Solution:
  
  
  Check Account Configuration:
  
  Go to the account master data and verify that the account is set up for accruals. This can be done in transaction code FS00 (G/L Account Master Record).
  Ensure that the account is marked for accruals in the relevant settings.
  
  
  
  Review Posting Periods:
  
  Check the posting periods in transaction code OB52 to ensure that the periods for the accrual date and GL transfer date are open.
  Make sure that the dates you are trying to post to are valid and within the allowed posting periods.
  
  
  
  Transaction Type Validation:
  
  Ensure that the transaction type being used is appropriate for the account and that it supports accruals.
  
  
  
  Configuration Settings:
  
  Review the configuration settings for accruals in the Financial Accounting (FI) module. This may involve checking the settings in SPRO (SAP Reference IMG) under Financial Accounting > General Ledger Accounting > Periodic Processing > Accruals.
  
  
  
  Consult Documentation:
  
  If the issue persists, consult SAP documentation or reach out to your SAP support team for further assistance. They may provide insights specific to your system configuration.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  FS00: G/L Account Master Record
  OB52: Open and Close Posting Periods
  SPRO: SAP Reference IMG for configuration settings
  
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  Testing: After making any changes, perform a test transaction to ensure that the error no longer occurs.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.