1J660 - Latest posting date could not be determined for due date &1

SAP Error Message - Details

• Message type: E = Error

• Message class: 1J - BCA: Payment Order Dialog

• Message number: 660

• Message text: Latest posting date could not be determined for due date &1

What causes this issue?

This error may have any one of the following reasons:
The calculated earliest posting date (EPD) is not allowed to be after
the latest posting date (LPD). Based on the Customizing settings, the
system calculates the EPD and LPD for a particular due date as as
follows:
EPD = due date - maximum number of calendar days before the due date
LPD = due date - minimum number of interbank working days before the
due date for the first run
LPD = due date - minimum number of interbank working days before the
due date for the subsequent run
There may be a calendar error defined for the calendar. In Customizing
for <ZK>Bank Customer Accounts (IS-B-BCA)</>, choose <LS>Account
Management -> SEPA -></>
<DS:SIMG.SIMG_BA-CA-TBKKSEPA_RCV>Define SEPA Properties for Recipient
Transaction Types</>.

System Response

The system cannot post the SEPA direct debit order (either one-time or
recurring).

How to fix this error?

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

AnswerBot

• What is the cause and solution for SAP error message 1J660 - Latest posting date could not be determined for due date &1 ?

  The SAP error message 1J660 ("Latest posting date could not be determined for due date &1") typically occurs in the context of financial transactions, particularly when dealing with payment processing or accounting entries. This error indicates that the system is unable to determine the latest posting date for a specific due date, which can hinder the processing of financial documents.
  Causes:
  
  Missing Configuration: The posting periods may not be properly configured in the system, leading to the inability to determine valid posting dates.
  Closed Posting Periods: The posting period for the due date in question may be closed, preventing any postings from being made.
  Incorrect Date Settings: The due date may fall outside the range of allowed posting dates, either due to system settings or user input errors.
  Authorization Issues: The user may not have the necessary authorizations to post in the specified period.
  System Errors: There may be a temporary issue or bug in the SAP system that is causing the error.
  
  Solutions:
  
  
  Check Posting Periods: Verify the configuration of posting periods in the system. Ensure that the relevant periods are open for posting.
  
  Transaction Code: OB52 (to check and maintain posting periods).
  
  
  
  Review Due Date: Ensure that the due date being processed is valid and falls within an open posting period.
  
  
  Adjust Date Settings: If the due date is incorrect, adjust it to a valid date that falls within an open posting period.
  
  
  User Authorizations: Check if the user has the necessary authorizations to post in the relevant period. If not, contact your SAP security administrator to grant the required permissions.
  
  
  Consult SAP Notes: Look for any relevant SAP Notes or updates that may address this specific error. Sometimes, there are known issues that have been documented by SAP.
  
  
  System Restart: If the issue seems to be a temporary glitch, restarting the SAP system or the relevant application may resolve the problem.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like FB60 (Enter Incoming Invoice), F-28 (Post Incoming Payments), and FBL1N (Vendor Line Item Display) as they may be relevant to the context in which the error occurs.
  SAP Support: If the issue persists after trying the above solutions, consider reaching out to SAP support for further assistance.
  Documentation: Review SAP documentation related to financial postings and period management for additional insights.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.