1J635 - Calculated due date based on posting dt &1 must be after 1st coll.date &2

Start a new search

SAP Error Message - Details

  • 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

  • Show details Hide details
  • What causes this issue?

    The calculated due date of the account closure SEPA debit order is
    before the first collection date of the selected mandate.

    System Response

    The system cannot create the external reference account.

    How to fix this error?

    Enter the planned closure date or use a different mandate.

    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.


AnswerBot

  • What is the cause and solution for SAP error message 1J635 - Calculated due date based on posting dt &1 must be after 1st coll.date &2 ?

    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:

    1. Incorrect Posting Date: The posting date may be set incorrectly, leading to an early due date.
    2. Configuration Issues: The settings for payment terms or due date calculations may not be configured correctly.
    3. 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:

    1. Check Posting Date: Verify the posting date in the transaction. Ensure that it is set correctly and is later than the first collection date.

    2. 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.

    3. 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.

    4. 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.

    5. Consult Configuration: If the issue persists, consult with your SAP configuration team to review the settings related to due date calculations and payment terms.

    6. Test in a Sandbox: If possible, replicate the issue in a test environment to understand the root cause without affecting production data.

    Related Information:

    • Transaction Codes: You may need to use transaction codes like FB60 (Enter Incoming Invoice) or F-28 (Post Incoming Payments) to check the relevant entries.
    • SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance.
    • Documentation: Review SAP documentation related to payment processing and due date calculations for further insights.

    By following these steps, you should be able to identify and resolve the cause of the error message 1J635 in your SAP system.

  • AnswerBot is an artificial intelligence solution provided by tomco.ai.
    Disclaimer

Related SAP Error Messages

Click the links below to see the following related messages:


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.