Message type: E = Error
Message class: 1J - BCA: Payment Order Dialog
Message number: 635
Message text: Calculated due date based on posting dt &1 must be after 1st coll.date &2
The calculated due date of the account closure SEPA debit order is
before the first collection date of the selected mandate.
The system cannot create the external reference account.
Enter the planned closure date or use a different mandate.
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 1J635 indicates that there is an issue with the calculated due date based on the posting date and the first collection date. Specifically, the error states that the calculated due date must be after the first collection date. This typically occurs in the context of financial transactions, such as billing or accounts receivable.
Cause:
The error is triggered when the system calculates a due date that is earlier than or the same as the first collection date. This can happen due to:
- Incorrect Posting Date: The posting date may be set incorrectly, leading to an early due date.
- Configuration Issues: The settings for payment terms or due date calculations may not be configured correctly.
- Data Entry Errors: Manual entry errors in the transaction data, such as incorrect dates.
Solution:
To resolve this error, you can take the following steps:
Check Posting Date: Verify the posting date in the transaction. Ensure that it is set correctly and is later than the first collection date.
Review First Collection Date: Check the first collection date to ensure it is set correctly. If it is incorrect, update it to the appropriate date.
Adjust Payment Terms: If the payment terms are causing the issue, review and adjust them as necessary. Ensure that the payment terms align with the expected due dates.
Recalculate Due Date: If changes are made to the posting date or first collection date, recalculate the due date to ensure it reflects the correct values.
Consult Configuration: If the issue persists, consult with your SAP configuration team to review the settings related to due date calculations and payment terms.
Test in a Sandbox: If possible, replicate the issue in a test environment to understand the root cause without affecting production data.
Related Information:
FB60
(Enter Incoming Invoice) or F-28
(Post Incoming Payments) to check the relevant entries.By following these steps, you should be able to identify and resolve the cause of the error message 1J635 in your SAP system.
1J634 Mandate &1 is not valid on due date &2 based on planned closure date &3
What causes this issue? The system has identified the mandate as invalid. This ...
1J633 Mandate &1 is not valid on planned closure date &2
What causes this issue? The system has identified the mandate as invalid. This ...
1J636 SDD checks use posting date &1 as planned closure date not entered
What causes this issue? The system has identified that the planned closure date...
1J637 Mandate checks use posting date &1 as planned closure date not entered
What causes this issue? The system has identified that the planned closure date...
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.