Message type: E = Error
Message class: 1J - BCA: Payment Order Dialog
Message number: 653
Message text: Next run date &1 is after the latest posting date &2
The latest posting date for the SEPA direct debit order is based on the
due date and the minimum number of interbank working days (specified for
a one-time payment order in Customizing activity
<DS:SIMG.BA-CA-V_TBKK_SDDDAYS>Define Processing Time for SEPA Orders
</>):
<ZH>Latest posting date = due date - minimum number of interbank working
days before the due date for one-time payment orders</>
If the SEPA direct debit order is part of a recurring series (standing
order) and the first run has already been executed, then the latest
posting date is as follows (specified for a subsequent payment order in
the above Customizing activity):
<ZH>Latest posting date = due date - minimum number of interbank working
days before the due date for subsequent run.</>
The next run date of a standing order during creation or execution must
always be on or before the latest posting date.
The system cannot create or execute a recurring SEPA direct debit order.
Do one of the following:
Specify a later due date so that the latest posting date is on or after
the next run date.
Specify an earlier date for the next run so that the latest posting date
is on or after the next run date.
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.
The SAP error message 1J653 indicates that there is a scheduling issue with a job or process in the system. Specifically, it means that the next run date of a scheduled job (denoted as &1) is set to occur after the latest posting date (denoted as &2). This can happen in various contexts, such as when dealing with financial postings, batch jobs, or other scheduled processes.
Cause:
- Posting Period Configuration: The posting period may be closed or restricted, preventing any postings after the latest allowed date.
- Job Scheduling: The job or process is scheduled to run at a time that is not valid due to the current configuration of posting periods.
- Incorrect Date Settings: The next run date for the job may have been set incorrectly, either manually or through a configuration error.
Solution:
Check Posting Periods:
- Navigate to the transaction code OB52 (or the relevant configuration for your version) to check the posting periods.
- Ensure that the posting period is open for the date you are trying to run the job.
Adjust Job Scheduling:
- Review the job scheduling settings in transaction SM37 (for job monitoring) or SM36 (for job scheduling).
- Modify the next run date of the job to ensure it falls within an open posting period.
Update Configuration:
- If necessary, update the configuration settings for the job or process to align with the current posting periods.
Consult Documentation:
- Review any relevant documentation or guidelines for the specific job or process to ensure compliance with posting rules.
Contact Support:
- If the issue persists, consider reaching out to your SAP support team or consulting SAP Notes for any known issues related to this error message.
Related Information:
Transaction Codes:
SAP Notes: Check SAP Notes for any updates or patches that may address this issue.
User Roles: Ensure that the user has the necessary authorizations to change job schedules and posting periods.
By following these steps, you should be able to resolve the error message 1J653 and ensure that your scheduled jobs run successfully within the allowed posting periods.
1J652 The SEPA direct debit order cannot be posted until &1
What causes this issue? The earliest date on which the system can post the SEPA...
1J651 Earliest posting date &1 is after latest posting date &2
What causes this issue? Either the settings in Customizing are incorrect, or th...
1J654 Next run date &1 before the earliest posting date &2
What causes this issue? The earliest date on which the system can post or execu...
1J655 Due date &1 cannot be before posting date &2
Self-Explanatory Message Since SAP believes that this specific error message is ...
SAP messages fall into 3 different categories: Error messages
(message type = E), Warnings (W) or Informational (I) messages.
An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.
Click on this link to search all SAP messages.