How To Fix FQM_CORE017 - BADI implementation: Origin transaction was created (&1)

FQM_CORE017 - Overview

• Message type: E = Error

• Message class: FQM_CORE - Financial Quantity Management: Core Messages

• Message number: 017

• Message text: BADI implementation: Origin transaction was created (&1)

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 FQM_CORE017 - BADI implementation: Origin transaction was created (&1) ?

  The SAP error message FQM_CORE017 typically relates to issues with the implementation of a Business Add-In (BADI) in the context of Financial Supply Chain Management (FSCM) or similar financial modules. The message indicates that there is a problem with the origin transaction that was created, and it usually includes a reference to the specific transaction or document number.
  
  Cause:
  
  BADI Implementation Issues: The BADI implementation may not be correctly defined or activated. This can happen if the BADI is not properly coded or if there are missing parameters.
  Data Inconsistencies: There may be inconsistencies in the data being processed, such as missing or incorrect entries in the relevant tables.
  Authorization Issues: The user executing the transaction may not have the necessary authorizations to perform the action, leading to the error.
  Configuration Errors: Incorrect configuration settings in the related financial modules can also lead to this error.
  
  
  Solution:
  
  
  Check BADI Implementation:
  
  Go to transaction SE18 (BADI Definition) and check