How To Fix FKK_PDC057 - G/L account does not exist for short account assignment &1

SAP Error Message - Details

• Message type: E = Error

• Message class: FKK_PDC - FI-CA: Postdated Checks

• Message number: 057

• Message text: G/L account does not exist for short account assignment &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 FKK_PDC057 - G/L account does not exist for short account assignment &1 ?

  The SAP error message FKK_PDC057 indicates that a General Ledger (G/L) account does not exist for a specific short account assignment. This typically occurs in the context of financial transactions, particularly in the area of contract accounts receivable and payable (FI-CA).
  Cause:
  The error can arise due to several reasons:
  
  Missing G/L Account: The G/L account specified in the transaction does not exist in the system for the specified short account assignment.
  Incorrect Configuration: The configuration for the account assignment may not be set up correctly in the system.
  Inactive or Deleted Accounts: The G/L account may have been marked as inactive or deleted in the system.
  Incorrect Account Assignment: The short account assignment used in the transaction may not be valid or may not correspond to any existing G/L account.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check G/L Account Configuration:
  
  Go to the transaction code OB52 to check the validity of the G/L account for the specified period.
  Use transaction code FS00 to verify if the G/L account exists and is active.
  
  
  
  Review Account Assignment:
  
  Check the short account assignment used in the transaction. Ensure that it is correctly configured and corresponds to a valid G/L account.
  You can use transaction code OBYC to review the account determination settings.
  
  
  
  Create or Modify G/L Account:
  
  If the G/L account does not exist, you may need to create it using transaction code FS00.
  If the account exists but is inactive, you can reactivate it.
  
  
  
  Consult Configuration Documentation:
  
  Review the configuration documentation for your specific SAP implementation to ensure that all necessary settings are in place.
  
  
  
  Check for User Exits or Enhancements:
  
  If there are any custom developments or user exits that might affect account determination, review them to ensure they are functioning correctly.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  FS00: Create/Change G/L Account
  OBYC: Automatic Account Determination
  OB52: Change View "Posting Periods": Overview
  
  
  Documentation: Refer to SAP Help documentation for detailed information on account determination and configuration in FI-CA.
  SAP Notes: Check for any relevant SAP Notes that might address known issues related to this error message.
  
  By following these steps, you should be able to identify the cause of the error and implement the necessary solution to resolve it.