How To Fix 1J657 - Error in calculating next run date and due date for subsequent run

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 657

• Message text: Error in calculating next run date and due date for subsequent run

What causes this issue?

An error occurred when the system determined the next run date and the
next due date in the execution of a recurring SEPA direct debit order.
The next run date and next due date are calculated in the implementation
of the BAdI BKK_STOR_SDD_COMPUTE_DATE, in the CALC_NEXT_DUE_DATE_RUN
method. If the implementation returns the output parameter E_RETURN and
this is not 0, or appends any errors to E_TAB_MESSAGES, then the error
occurred in the calculation logic in the above implementation.

System Response

Although the current execution of the recurring SEPA direct debit order
is possible without errors, the system cannot determine the next run
date. This means that the system rolls the current execution back.

How to fix this error?

Change the next run date for the standing order in the dialog mode and
ensure that the next run date is between the earliest and latest posting
date of the due date.

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message 1J657 - Error in calculating next run date and due date for subsequent run ?

  The SAP error message 1J657 indicates that there is an issue with calculating the next run date and the due date for a subsequent run in a scheduling or job processing context. This error typically arises in scenarios involving background jobs, scheduling of tasks, or periodic processing in SAP systems.
  Causes:
  
  Incorrect Configuration: The scheduling parameters or configuration settings for the job may be incorrect or incomplete.
  Missing Data: Required data for the job or task may be missing, leading to an inability to calculate the next run date.
  Date Format Issues: There may be issues with the date format or the system's date settings.
  Calendar Settings: The calendar settings used for scheduling may not be properly defined or may conflict with the job's requirements.
  System Time Zone: The system's time zone settings may not align with the expected time zone for the job scheduling.
  Job Dependencies: If the job is dependent on other jobs or processes, and those are not completed or have errors, it may affect the scheduling.
  
  Solutions:
  
  Check Job Configuration: Review the configuration settings for the job in transaction codes like SM37 (Job Monitoring) or SM36 (Define Background Job). Ensure that all parameters are correctly set.
  Verify Required Data: Ensure that all necessary data for the job is available and correctly entered in the system.
  Review Date Formats: Check the date formats in the system settings and ensure they are consistent with the expected formats for the job.
  Examine Calendar Settings: Look into the calendar settings used for the job. Ensure that they are correctly defined and do not conflict with the job's scheduling.
  Check System Time Zone: Verify the system's time zone settings and ensure they are correctly configured for the job's requirements.
  Job Dependencies: If the job has dependencies, ensure that all prerequisite jobs have been completed successfully without errors.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM37 (Job Monitoring), SM36 (Define Background Job), and SM21 (System Log) to troubleshoot and monitor jobs.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP's support portal can provide additional insights and solutions.
  Documentation: Review SAP documentation related to job scheduling and background processing for best practices and troubleshooting steps.
  
  If the issue persists after checking the above points, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.