How To Fix 68066 - Customer $ not found in company code $

SAP Error Message - Details

• Message type: E = Error

• Message class: 68 - Message for DARWIN Loans (continued)

• Message number: 066

• Message text: Customer $ not found in company code $

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 68066 - Customer $ not found in company code $ ?

  The SAP error message "68066 Customer $ not found in company code $" typically indicates that the system is unable to find a customer master record for the specified customer ID in the specified company code. This can occur in various scenarios, such as when trying to post a transaction related to that customer or when attempting to access customer data.
  Causes:
  
  Customer Not Created: The customer master record has not been created for the specified company code.
  Incorrect Company Code: The customer may exist, but not in the specified company code.
  Data Deletion: The customer record may have been deleted or marked for deletion in the specified company code.
  Authorization Issues: The user may not have the necessary authorizations to view or access the customer record.
  Data Migration Issues: If data was migrated from another system, there may have been issues during the migration process that resulted in missing records.
  
  Solutions:
  
  
  Create Customer Master Record:
  
  If the customer does not exist, create a new customer master record in the relevant company code using transaction code XD01 (for general data) and XD02 (for company code data).
  
  
  
  Check Existing Customer Records:
  
  Use transaction code XD03 to check if the customer exists in the system and verify if it is assigned to the correct company code.
  
  
  
  Review Deletion Flags:
  
  Check if the customer record has been marked for deletion. You can do this by reviewing the customer master data in the relevant transaction.
  
  
  
  Verify Company Code:
  
  Ensure that the correct company code is being used in the transaction. If the customer exists in a different company code, you may need to switch to that company code.
  
  
  
  Authorization Check:
  
  Ensure that the user has the necessary authorizations to access customer data. This may involve checking user roles and permissions.
  
  
  
  Data Migration Review:
  
  If the issue arose after a data migration, review the migration logs and processes to ensure that all customer records were migrated correctly.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  XD01: Create Customer (General Data)
  XD02: Change Customer (General Data)
  XD03: Display Customer (General Data)
  FD01: Create Customer (Company Code)
  FD02: Change Customer (Company Code)
  FD03: Display Customer (Company Code)
  
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to customer master data management.
  
  
  Documentation: Refer to SAP documentation for customer master data management for more detailed information on how to manage customer records effectively.
  
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP support team or a functional consultant for further assistance.