How To Fix 1J673 - The latest due date for posting date &1 can be &2

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 673

• Message text: The latest due date for posting date &1 can be &2

What causes this issue?

The latest due date for a given posting date of a SEPA direct debit
order is based on the settings in Customizing activity
<DS:SIMG.BA-CA-V_TBKK_SDDDAYS>Define Processing Time for SEPA Orders
</>:
<ZH>Latest due date = posting date + maximum number of calendar days
before the due date.</>
The due date of a payment order must be on or before the latest due
date.

System Response

The system cannot post the SEPA direct debit order.

How to fix this error?

Create the SEPA direct debit order according to the processing time
defined in Customizing.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 1J673 - The latest due date for posting date &1 can be &2 ?

  The SAP error message 1J673 indicates that there is a restriction on the posting date you are trying to use for a transaction. Specifically, it means that the latest due date for the specified posting date is beyond the allowed limit set in the system.
  Cause:
  This error typically occurs due to one of the following reasons:
  
  Posting Period Closure: The posting period for the specified date may be closed, preventing any further postings.
  Configuration Settings: The system may have specific settings that restrict posting to certain dates, such as fiscal year-end restrictions or other financial controls.
  Document Type Restrictions: Certain document types may have specific posting date restrictions based on company policies or configurations.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Posting Period:
  
  Go to the transaction code OB52 (Change Posting Periods) to check if the posting period for the date you are trying to use is open. If it is closed, you may need to open it or use a different posting date.
  
  
  
  Review Configuration:
  
  Check the configuration settings in the Financial Accounting (FI) module to see if there are any restrictions on posting dates. This can be done through transaction codes like SPRO (SAP Reference IMG) and navigating to the relevant sections.
  
  
  
  Consult with Finance Team:
  
  If you are unsure about the posting date or the implications of changing it, consult with your finance or accounting team to ensure compliance with company policies.
  
  
  
  Use a Valid Posting Date:
  
  If the date you are trying to use is not valid, consider using a different date that falls within the allowed posting periods.
  
  
  
  Check Document Type Settings:
  
  If the error is related to a specific document type, review the settings for that document type to ensure it allows postings for the date in question.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OB52 (for posting periods), SPRO (for configuration), and FB01 (for posting documents).
  SAP Notes: Check SAP Notes for any known issues or updates related to this error message.
  User Authorization: Ensure that you have the necessary authorizations to post documents in the specified period.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.