How To Fix >4585 - Notification of outgoing payments is not supported

SAP Error Message - Details

• Message type: E = Error

• Message class: >4 - SAP File Transfer Protocol

• Message number: 585

• Message text: Notification of outgoing payments is not supported

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message >4585 - Notification of outgoing payments is not supported ?

  The SAP error message "4585 Notification of outgoing payments is not supported" typically occurs in the context of payment processing within the SAP system, particularly when dealing with outgoing payments. This error indicates that the system is unable to process a notification for outgoing payments due to certain restrictions or configurations.
  Cause:
  
  Configuration Issues: The error may arise if the payment method or the configuration for outgoing payments is not set up correctly in the system.
  Payment Method Restrictions: Certain payment methods may not support notifications for outgoing payments. For example, if a payment method is configured to not allow notifications, this error will occur.
  Document Type Limitations: The document type associated with the payment may not support notifications.
  System Settings: The settings in the payment program or the financial accounting module may not be configured to handle notifications for outgoing payments.
  
  Solution:
  
  
  Check Payment Method Configuration:
  
  Go to the configuration settings for payment methods in the SAP system (Transaction code: OBPM1).
  Ensure that the payment method you are using is configured to allow notifications for outgoing payments.
  
  
  
  Review Document Type Settings:
  
  Check the document type associated with the payment. Ensure that it is set up correctly to support notifications.
  You can review document type settings in the configuration (Transaction code: OBA7).
  
  
  
  Adjust Payment Program Settings:
  
  Review the settings of the payment program (Transaction code: F110) to ensure that it is configured to handle notifications appropriately.
  Make sure that the parameters for the payment run are set correctly.
  
  
  
  Consult SAP Notes:
  
  Check for any relevant SAP Notes that may address this specific error. SAP Notes often provide patches or configuration changes that can resolve known issues.
  
  
  
  Testing:
  
  After making any changes, perform a test run of the payment process to see if the error persists.
  
  
  
  Consult with SAP Support:
  
  If the issue continues after checking the configurations and settings, consider reaching out to SAP support for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as F110 (Automatic Payment Transactions), OBPM1 (Payment Methods in Country), and OBA7 (Document Types).
  SAP Documentation: Review SAP documentation related to payment processing and configuration for more detailed guidance.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.