How To Fix 1M060 - Old due date, curr. year/no. for int. acct. no. &1, bank area &2: &3,&4

SAP Error Message - Details

• Message type: E = Error

• Message class: 1M - BKK: Abschluß

• Message number: 060

• Message text: Old due date, curr. year/no. for int. acct. no. &1, bank area &2: &3,&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 1M060 - Old due date, curr. year/no. for int. acct. no. &1, bank area &2: &3,&4 ?

  The SAP error message 1M060 typically indicates an issue related to the processing of an internal account in the context of bank accounting. The message suggests that there is an old due date for a transaction that is being processed in the current year, which is not allowed for the specified internal account and bank area.
  Cause:
  
  Old Due Date: The transaction has a due date that is earlier than the current fiscal year, which is not permissible for the specified internal account.
  Configuration Issues: There may be configuration settings in the bank accounting module that restrict transactions with due dates that fall outside of the current fiscal year.
  Data Entry Errors: The due date may have been incorrectly entered during transaction processing.
  
  Solution:
  
  Check Due Date: Review the due date of the transaction that triggered the error. Ensure that it is set to a valid date within the current fiscal year.
  Adjust Transaction: If the due date is indeed old, you may need to adjust the transaction to reflect a valid due date.
  Review Configuration: Check the configuration settings for the internal account and bank area in the SAP system. Ensure that the settings allow for the processing of transactions with due dates in the current year.
  Consult Documentation: Refer to SAP documentation or consult with your SAP support team for specific configuration settings related to bank accounting and internal accounts.
  Transaction Type: Ensure that the transaction type being used is appropriate for the internal account and bank area in question.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error message or provide additional guidance on handling it.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FB50 (General Ledger Account Document Entry) or F-02 (General Posting) to review and correct the entries.
  User Roles: Ensure that the user has the necessary permissions to make changes to the transactions or configurations related to bank accounting.
  
  If the issue persists after following these steps, it may be beneficial to engage with your SAP support team or a consultant who specializes in SAP Financial Accounting (FI) for further assistance.