How To Fix FKKORDER142 - Standing request &1 with due date &2 processed in simulation run

SAP Error Message - Details

• Message type: E = Error

• Message class: FKKORDER - Messages for Request

• Message number: 142

• Message text: Standing request &1 with due date &2 processed in simulation run

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 FKKORDER142 - Standing request &1 with due date &2 processed in simulation run ?

  The SAP error message FKKORDER142 indicates that a standing request (recurring payment) has been processed in a simulation run rather than in a live run. This typically occurs in the context of the Contract Accounts Receivable and Payable (FI-CA) module, where standing requests are used to automate recurring payments.
  Cause:
  
  Simulation Mode: The system is set to run in simulation mode, which means that it will not post any actual transactions but will instead simulate the processing of the standing request.
  Configuration Settings: The configuration for the payment run may be set to simulate mode, which is often used for testing purposes.
  User Authorization: The user may not have the necessary authorization to execute the payment run in live mode.
  
  Solution:
  
  
  Check Payment Run Configuration:
  
  Go to the transaction for the payment run (e.g., F110) and check the settings. Ensure that the "Simulate" option is not selected if you want to execute the payment run for real.
  
  
  
  Execute in Live Mode:
  
  If you are running a payment run, ensure that you select the option to execute it in live mode rather than simulation mode.
  
  
  
  User Authorization:
  
  Verify that the user executing the payment run has the necessary authorizations to perform live transactions. If not, contact your SAP security administrator to adjust the user roles.
  
  
  
  Review Logs:
  
  Check the logs for the payment run to see if there are any additional messages or warnings that could provide more context about why the run was processed in simulation.
  
  
  
  Testing:
  
  If you are testing the payment run, it is normal for it to be in simulation mode. Ensure that you switch to live mode when you are ready to process actual payments.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as F110 (Automatic Payment Transactions) and FKK_ORDER (for managing standing requests).
  Documentation: Refer to SAP Help documentation for detailed information on configuring and executing payment runs in FI-CA.
  Support: If the issue persists, consider reaching out to SAP support or your internal SAP support team for further assistance.
  
  By following these steps, you should be able to resolve the FKKORDER142 error and successfully process your standing requests.