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

SAP Error Message - Details

• 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 the BAdI related to NF-e (e.g., J_1BNF_BADI).
  Ensure that the implementation is active and correctly coded to return the necessary data.
  
  
  
  Debugging:
  
  Use transaction SE80 or SE37 to debug the BAdI implementation. Set breakpoints to see if the BAdI is being called and what data is being processed.
  Check if the BAdI is being called with the correct parameters and if the logic is correctly implemented to return data.
  
  
  
  Review Configuration:
  
  Check the configuration settings for NF-e in transaction SPRO. Ensure that all necessary settings are correctly configured.
  Verify that the relevant master data (e.g., customer/vendor data, material data) is correctly maintained.
  
  
  
  Check Authorizations:
  
  Ensure that the user has the necessary authorizations to execute the transaction and access the data required by the BAdI.
  
  
  
  Consult Documentation:
  
  Review SAP Notes related to NF-e and the specific BAdI for any known issues or additional configuration steps that may be required.
  
  
  
  SAP Support:
  
  If the issue persists, consider reaching out to SAP Support for assistance. Provide them with details of the error, the BAdI implementation, and any relevant logs.
  
  
  
  Related Information:
  
  BAdI Documentation: Review the documentation for the specific BAdI you are working with to understand its purpose and expected behavior.
  SAP Notes: Search for relevant SAP Notes that may address this specific error or provide guidance on BAdI implementations related to NF-e.
  Community Forums: Check SAP Community or other forums for similar issues and solutions shared by other users.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.