Message type: E = Error
Message class: 1J - BCA: Payment Order Dialog
Message number: 661
Message text: Backdated posting is not allowed for SEPA direct debit orders
The posting date of a SEPA direct debit order cannot be before the
transaction posting date of the bank area. Only current posting dates
are allowed for SEPA direct debit orders.
The system cannot create, postprocess, or release a backdated SEPA
direct debit order.,,
Change the date to the current posting 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 1J661 indicates that backdated postings are not allowed for SEPA (Single Euro Payments Area) direct debit orders. This error typically arises when a user attempts to post a SEPA direct debit transaction with a posting date that is earlier than the current date or the date allowed by the system.
Cause:
- Backdated Posting Attempt: The primary cause of this error is an attempt to process a SEPA direct debit order with a posting date that is in the past.
- System Configuration: The system may be configured to prevent backdated postings for compliance reasons, as SEPA regulations require that direct debit transactions be processed on or after the effective date.
- Payment Run Settings: The settings in the payment run may not allow for backdated transactions.
Solution:
- Change Posting Date: Ensure that the posting date for the SEPA direct debit order is set to the current date or a future date. This can be done in the transaction where the direct debit is being processed.
- Review Payment Run Configuration: Check the configuration settings for the payment run in SAP. Ensure that the settings allow for the intended posting dates.
- Consult Documentation: Review SAP documentation or guidelines related to SEPA direct debit processing to ensure compliance with the required posting dates.
- User Training: Provide training to users on the correct procedures for entering SEPA direct debit orders to avoid future errors.
Related Information:
By addressing the posting date and ensuring compliance with SEPA regulations, you should be able to resolve the error message 1J661 effectively.
1J660 Latest posting date could not be determined for due date &1
What causes this issue? This error may have any one of the following reasons: T...
1J659 The reference variable for BAdI & was not instantiated
Self-Explanatory Message Since SAP believes that this specific error message is ...
1J662 System calculated next run date for &1 and due date for &2
Self-Explanatory Message Since SAP believes that this specific error message is ...
1J663 BIC and IBAN mandatory for recipient identification in SEPA direct debits
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.