How To Fix FQ293 - New G/L account &1 in standing request &2 was derived

SAP Error Message - Details

• Message type: E = Error

• Message class: FQ - Payment Requests and Payment Program

• Message number: 293

• Message text: New G/L account &1 in standing request &2 was derived

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 FQ293 - New G/L account &1 in standing request &2 was derived ?

  The SAP error message FQ293 indicates that a new General Ledger (G/L) account has been derived in a standing request, but it is not recognized or not properly configured in the system. This error typically occurs in the context of financial transactions, particularly when dealing with the New G/L functionality in SAP.
  Cause:
  
  Missing Configuration: The G/L account specified in the error message may not be properly configured in the system. This could be due to missing master data or incorrect settings in the financial accounting configuration.
  Account Derivation Logic: The account derivation logic may not be set up correctly, leading to the system deriving an account that does not exist or is not valid for the transaction.
  Inactive G/L Account: The derived G/L account may be inactive or blocked for postings.
  Authorization Issues: The user may not have the necessary authorizations to access or post to the derived G/L account.
  
  Solution:
  
  
  Check G/L Account Configuration:
  
  Verify that the G/L account mentioned in the error message is created and active in the system.
  Ensure that the account is assigned to the correct chart of accounts and is available for the relevant company code.
  
  
  
  Review Account Derivation Settings:
  
  Check the account determination settings in the configuration (Transaction Code: OBYC or SPRO).
  Ensure that the derivation rules are correctly defined and that they point to valid G/L accounts.
  
  
  
  Activate the G/L Account:
  
  If the G/L account is inactive, activate it in the G/L account master data.
  
  
  
  Check User Authorizations:
  
  Ensure that the user has the necessary authorizations to post to the derived G/L account. This can be checked in the user roles and profiles.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to the specific error message for additional insights or updates.
  
  
  
  Testing:
  
  After making the necessary changes, test the transaction again to see if the error persists.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  OB52 (Open and Close Posting Periods)
  OBYC (Automatic Account Determination)
  FS00 (G/L Account Master Data)
  
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Support: If the issue persists after checking the above points, 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 root cause of the FQ293 error and implement the necessary solutions to resolve it.