Do you have any question about this error?
Message type: E = Error
Message class: FKK_SEPA - FI-CA: SEPA Mandate Management
Message number: 076
Message text: Item was automatically selected as not to be notified
Already at the time the receivable was posted, the caller or the
definition of event 0061 specified that this receivable is not to be
pre-notified explicitly. Therefore you cannot change this specification
manually.
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.
FKK_SEPA076
- Item was automatically selected as not to be notified ?The SAP error message FKK_SEPA076 indicates that an item has been automatically selected as "not to be notified" in the context of SEPA (Single Euro Payments Area) payment processing. This typically occurs in the Financial Accounting (FI) module, particularly when dealing with payment runs and notifications related to SEPA transactions.
Cause:
The error message can arise due to several reasons, including:
- Payment Block: The item may have a payment block set, which prevents it from being processed for notification.
- Payment Method Configuration: The payment method used may not be configured to allow notifications for certain items.
- Customer or Vendor Settings: The settings for the customer or vendor involved in the transaction may indicate that notifications should not be sent.
- Document Status: The status of the document (e.g., invoice, credit memo) may not allow for notifications to be sent.
- Custom Logic: There may be custom logic or user exits that automatically set certain items to not be notified based on specific criteria.
Solution:
To resolve the issue, you can take the following steps:
- Check Payment Block: Review the item in question to see if there is a payment block set. If so, remove the block if appropriate.
- Review Payment Method: Ensure that the payment method used for the transaction is configured correctly to allow notifications. This can be checked in the configuration settings for payment methods in SAP.
- Customer/Vendor Settings: Verify the settings for the customer or vendor to ensure that they are set up to receive notifications. This can include checking the master data for any flags that indicate notification preferences.
- Document Status: Check the status of the document to ensure it is eligible for notification. If the document is in a status that does not allow notifications, you may need to change its status.
- Custom Logic Review: If there are any custom developments or user exits in place, review them to see if they are affecting the notification settings for the item.
- Consult Documentation: Refer to SAP documentation or help resources for specific details related to SEPA processing and notifications.
Related Information:
If the issue persists after checking these areas, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in Financial Accounting and SEPA processes.
Get instant SAP help. Start your 7-day free trial now.
FKK_SEPA075
Direct debit pre-notification &1 (bank &2) can no longer be used
What causes this issue? Open direct debit pre-notification &v1& exists for bank &v2& with IBAN &v3&. If the bank details are ...
FKK_SEPA074
IBAN &1 from mandate &2 does not exist in any bank details for partner &3
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FKK_SEPA077
You cannot set automatic status manually
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FKK_SEPA078
Invalid changes to mandate &1 in event 0576
What causes this issue? In event 0576, fields of mandate &V1& were changed that are not allowed to be changed. The ID of the mandate and the ...
Click on this link to search all SAP messages.