How To Fix FACI_ANA101 - BAdI &1 is not implemented.

FACI_ANA101 - Overview

• Message type: E = Error

• Message class: FACI_ANA - Messages for analysis routines in function group FACI

• Message number: 101

• Message text: BAdI &1 is not implemented.

What causes this issue?

The BAdI <(>&<)>V1<(>&<)> is not implemented in your system. The split
functionality for incoming and outgoing invoices must be activated via a
custom BAdI implementation.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Using transaction SE18, create a custom implementation of the BAdI
<(>&<)>V1<(>&<)>. You can use one of the following methods for ac
tivating the split function:
1) SET_NUMBER_OF_INVOICE_ITEMS
With this method, you can determine how many items of the incoming or
outgoing invoice should be included in a document of the posting.
However, you should bear in mind that each invoice item usually
generates several lines in the FI document. For example, an incoming
invoice from Logistics invoice verification usually generates a balance
item and a GR/IR line per invoice item. However, freight clearing lines
or price differences could also be posted. Therefore, you should not
select a number of invoice items that is too high as otherwise the
resulting FI document could again possibly include more than 999 line
items.
2) ACTIVATE_AUTOMATIC_SPLIT
If you activate the document split with this method, the optimum number
of invoice items per split FI document is determined automatically by
the system. With this option, the fewest possible FI documents are
posted because the number of document items per split FI document is
selected as high as possible.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

FACI_ANA101 - Details

• The SAP error message FACI_ANA101 indicates that a Business Add-In (BAdI) is not implemented. This typically occurs when the system is trying to execute a piece of code that relies on a specific BAdI implementation, but no implementation exists for that BAdI in the system.
  
  Cause:
  
  Missing Implementation: The BAdI has been defined in the system, but no implementation has been created for it.
  Incorrect Configuration: The system may be configured to use a BAdI that is not relevant for the current context or transaction.
  Transport Issues: If the BAdI was recently transported from another system, the implementation may not have been included in the transport.
  
  
  Solution:
  
  
  Check BAdI Implementation:
  
  Go to transaction SE18 (BAdI Definition) and enter the name of the BAdI indicated in the error message.
  Check if there are any implementations available by using transaction SE19 (BAdI Implementation).
  If no implementation exists, you may need to create one.
  
  
  
  Create Implementation:
  
  If you need to implement the BAdI, you