How To Fix FKKMDC002 - Request for partner &1 (origin &2, change type &3) simulated

FKKMDC002 - Overview

• Message type: E = Error

• Message class: FKKMDC - Requests for Change to Master Data

• Message number: 002

• Message text: Request for partner &1 (origin &2, change type &3) simulated

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 FKKMDC002 - Request for partner &1 (origin &2, change type &3) simulated ?

  The SAP error message FKKMDC002 typically relates to issues in the Contract Accounts Receivable and Payable (FI-CA) module, specifically when dealing with partner data. This message indicates that a request for a partner (customer or vendor) has been simulated but not executed. Here’s a breakdown of the cause, potential solutions, and related information:
  
  Cause:
  
  Simulation Mode: The error indicates that the system is in simulation mode, meaning that the changes to the partner data are not being executed but rather simulated. This can happen if the transaction is set to simulate changes instead of applying them.
  Change Type: The change type specified in the message may not be valid for the operation being performed, or the system may not allow the change due to certain conditions.
  Data Inconsistencies: There may be inconsistencies or missing data in the partner master records that prevent the system from processing the request.
  Authorization Issues: The user may not have