How To Fix AM768 - No record was found in EKKO (EBELN) for & records in the table EKAN

SAP Error Message - Details

• Message type: E = Error

• Message class: AM - Business Address Services

• Message number: 768

• Message text: No record was found in EKKO (EBELN) for & records in the table EKAN

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 AM768 - No record was found in EKKO (EBELN) for & records in the table EKAN ?

  The SAP error message AM768 indicates that the system could not find a corresponding record in the EKKO table (which contains purchasing document header data) for the specified purchasing document number (EBELN) in the EKAN table (which contains account assignment data for purchasing documents). This typically occurs during processes that involve account assignments, such as when trying to post an invoice or perform a goods receipt.
  Cause:
  
  Missing Purchasing Document: The purchasing document (purchase order) referenced by the EBELN does not exist in the EKKO table. This could happen if the purchase order was deleted or never created.
  Data Inconsistency: There may be inconsistencies in the database, such as orphaned records in the EKAN table that do not have a corresponding entry in the EKKO table.
  Incorrect Document Number: The document number (EBELN) being referenced might be incorrect or mistyped.
  Authorization Issues: The user may not have the necessary authorizations to view the purchasing document.
  
  Solution:
  
  Verify the Purchase Order: Check if the purchase order exists in the EKKO table. You can do this by using transaction codes like ME23N (Display Purchase Order) or SE16N (Data Browser) to query the EKKO table directly.
  Check for Deletion: If the purchase order was deleted, you may need to recreate it or check with your procurement team to understand the reason for deletion.
  Correct Document Number: Ensure that the EBELN being used is correct. Double-check for any typos or errors in the document number.
  Data Consistency Check: If you suspect data inconsistency, you may need to run a consistency check or consult with your SAP Basis team to investigate and resolve any database issues.
  Authorization Check: Ensure that the user has the necessary permissions to access the purchasing document. If not, the user may need to be granted the appropriate roles or permissions.
  
  Related Information:
  
  Transaction Codes: 
  
  ME23N: Display Purchase Order
  SE16N: Data Browser for table access
  ME2N: Purchase Orders by PO Number
  
  
  Tables:
  
  EKKO: Purchasing Document Header
  EKAN: Account Assignment Data for Purchasing Documents
  
  
  SAP Notes: Check for any relevant SAP Notes that might address known issues or provide additional guidance related to this error message.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or refer to SAP documentation for further troubleshooting.