How To Fix AM368 - Duplicate check not active (no BAdI implementation)

AM368 - Overview

• Message type: E = Error

• Message class: AM - Business Address Services

• Message number: 368

• Message text: Duplicate check not active (no BAdI implementation)

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 AM368 - Duplicate check not active (no BAdI implementation) ?

  The SAP error message AM368 "Duplicate check not active (no BAdI implementation)" typically occurs in the context of Asset Accounting (FI-AA) when the system is trying to perform a duplicate check for asset master records, but there is no active implementation of the Business Add-In (BAdI) that would handle this check.
  
  Cause:
  
  BAdI Not Implemented: The primary cause of this error is that the BAdI for duplicate checks in Asset Accounting is not implemented in the system. The system expects a certain BAdI implementation to be active to perform the duplicate check.
  
  Configuration Issues: There may be configuration settings that are not properly set up, leading to the system not being able to perform the duplicate check.
  Custom Development: If there is a custom development that relies on the duplicate check, and it is not properly implemented, this error can occur.
  
  
  Solution:
  
  
  Implement the BAdI:
  
  You need to implement the BAdI FI_AA_DUPLICATE_CHECK (or a similar BAdI related