How To Fix J1B_NFE343 - Error in BAdI implementation; no data returned

J1B_NFE343 - Overview

• Message type: E = Error

• Message class: J1B_NFE - Message class for NF-e

• Message number: 343

• Message text: Error in BAdI implementation; no data returned

What causes this issue?

The logic in your implementation of the <ZK>Conversions for Incoming
NF-e Automation</> Business Add-In (BAdI) did not return any data.

System Response

The system does not send inbound delivery information to SAP
BusinessObjects Nota Fiscal Eletr(nica.

How to fix this error?

Check your implementation of the <ZK>Search for Inbound Delivery</> (
<ZH>INBOUND_DELIV_SEARCH</>) method in the
<DS:SIMG.J_1BNFE_IN>Conversions for Incoming NF-e Automation</> (
<ZH>J_1BNFE_IN</>) BAdI.

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

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message J1B_NFE343 - Error in BAdI implementation; no data returned ?

  The SAP error message J1B_NFE343: Error in BAdI implementation; no data returned typically occurs in the context of Brazil's Nota Fiscal Eletrônica (NF-e) processing. This error indicates that there is an issue with a Business Add-In (BAdI) implementation that is expected to return data but is not doing so.
  
  Cause:
  
  BAdI Implementation Issues: The BAdI implementation may not be correctly defined or activated. It might not be returning the expected data due to logic errors or missing configurations.
  Data Not Found: The BAdI might be called in a scenario where there is no relevant data to return, leading to the error.
  
  Configuration Issues: There may be missing or incorrect configuration settings related to the NF-e process or the specific BAdI being used.
  Authorization Issues: The user executing the transaction may not have the necessary authorizations to access the data required by the BAdI.
  
  
  Solution:
  
  
  Check BAdI Implementation:
  
  Go to transaction SE19 (BAdI Implementation) and check the implementation for