FAP_CMP802 - Payment run (run date: &2; ID: &1) has been scheduled.

SAP Error Message - Details

• Message type: E = Error

• Message class: FAP_CMP - Vendor Manual Payment

• Message number: 802

• Message text: Payment run (run date: &2; ID: &1) has been scheduled.

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 FAP_CMP802 - Payment run (run date: &2; ID: &1) has been scheduled. ?

  The SAP error message FAP_CMP802 indicates that a payment run has been scheduled but has not yet been executed. This message typically appears in the context of the Financial Accounting (FI) module, particularly when dealing with payment processing.
  Cause:
  
  Scheduled Payment Run: The payment run has been scheduled for a future date, which means it is not yet due for execution.
  Configuration Issues: There may be configuration settings that prevent the payment run from being executed immediately.
  User Authorization: The user may not have the necessary authorizations to execute the payment run.
  Technical Issues: There could be underlying technical issues, such as job scheduling problems in the background processing system.
  
  Solution:
  
  Check Payment Run Status: Verify the status of the payment run in the payment run monitor. You can do this by navigating to the transaction code F110 (Automatic Payment Transactions) and checking the scheduled runs.
  Execute Payment Run: If the payment run is scheduled for a future date, you may need to wait until that date or manually execute it if allowed.
  Review Configuration: Ensure that the payment run configuration is set up correctly. Check the parameters and settings in the payment program.
  User Authorization: Confirm that the user has the necessary authorizations to execute payment runs. This may involve checking roles and permissions in the user profile.
  Check Background Jobs: If there are technical issues, check the background job logs (transaction code SM37) to see if there are any errors related to the payment run job.
  Consult Documentation: Refer to SAP documentation or support notes for any specific issues related to the version of SAP you are using.
  
  Related Information:
  
  Transaction Codes: 
  
  F110: For managing automatic payment transactions.
  SM37: For monitoring background jobs.
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to payment runs.
  User Manuals: Review user manuals or training materials for guidance on executing payment runs and troubleshooting common issues.
  
  If the problem persists after following these steps, it may be necessary to consult with your SAP support team or reach out to SAP support for further assistance.