How To Fix FIKZ_DDX005 - Customer with BIN &1 not found in company code &2 or not Customized

SAP Error Message - Details

• Message type: E = Error

• Message class: FIKZ_DDX - Message class for digital documents exchange

• Message number: 005

• Message text: Customer with BIN &1 not found in company code &2 or not Customized

What causes this issue?

The system cannot process the XML file because no customer exists with
the given external ID (<DS:GLOS.5CF3FCDB46F61ED484E5F872885ED595>BIN</>
number) and company code in the system or the electronic invoicing
solution has not been enabled for the customer with this BIN.

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?

Ensure that you have made the following settings:
You have maintained the BIN number in the master data for the customer.
You have enabled e-invoicing for the customer in the
<DS:TRAN.FIKZDIPCUST>Enable E-Invoicing for Customers</> transaction.

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 FIKZ_DDX005 - Customer with BIN &1 not found in company code &2 or not Customized ?

  The SAP error message FIKZ_DDX005 indicates that a customer with a specific Business Identification Number (BIN) is not found in the specified company code or is not properly customized in the system. This error typically arises during processes that involve customer data, such as invoicing or payment processing.
  Cause:
  
  Missing Customer Master Data: The customer with the specified BIN does not exist in the customer master data for the given company code.
  Incorrect Configuration: The customer may not be properly configured in the system, meaning that the necessary settings or data entries are missing.
  Company Code Issues: The customer might exist in another company code but not in the one specified in the error message.
  Data Synchronization Issues: If the system is integrated with other systems (like CRM or third-party applications), there may be synchronization issues leading to missing or outdated data.
  
  Solution:
  
  
  Check Customer Master Data:
  
  Go to the customer master data transaction (e.g., XD03 for display).
  Verify if the customer with the specified BIN exists in the system for the given company code.
  If not, create the customer master record using transaction XD01 (create customer) or XD02 (change customer).
  
  
  
  Verify Configuration:
  
  Ensure that the customer is properly configured in the system. Check the settings related to the customer account group and company code.
  Make sure that the necessary fields are filled out correctly in the customer master data.
  
  
  
  Check Company Code Assignment:
  
  Confirm that the customer is assigned to the correct company code. If the customer is meant to be used in multiple company codes, ensure that they are set up accordingly.
  
  
  
  Data Synchronization:
  
  If your SAP system is integrated with other systems, check for any data synchronization issues. Ensure that the customer data is consistent across all systems.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to this error message for any specific guidance or updates that may apply to your version of SAP.
  
  
  
  Contact Support:
  
  If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting SAP Notes for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  XD01, XD02, XD03 for customer master data management.
  FD01, FD02, FD03 for financial customer data.
  
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error message or provide additional troubleshooting steps.
  User Roles: Ensure that the user has the necessary permissions to view or edit customer master data.
  
  By following these steps, you should be able to identify the root cause of the error and implement the necessary solutions to resolve it.