How To Fix MN679 - Record missing in internal account determination table (internal error)

SAP Error Message - Details

• Message type: E = Error

• Message class: MN - Message class for subsequent settlement (Purchasing)

• Message number: 679

• Message text: Record missing in internal account determination table (internal error)

What causes this issue?

You tried to read a record in the internal account determination table.
However, no entry exists for the key fields Client / Document condition
number / Condition item number / Stage number / Condition counter with
the values &V1&.
This is due to a program error.

System Response

INCLUDE ISR_STOP

How to fix this error?

INCLUDE NA_SYSADMIN1
This was accessed in form routine &V2& in function module &V3&.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MN679 - Record missing in internal account determination table (internal error) ?

  The SAP error message MN679, which states "Record missing in internal account determination table (internal error)," typically occurs in the context of account determination processes, particularly in the Materials Management (MM) module. This error indicates that the system is unable to find the necessary account determination records for a specific transaction, which can lead to issues in posting or processing transactions.
  Causes:
  
  
  Missing Configuration: The most common cause is that the account determination configuration for the relevant transaction type is incomplete or missing. This can happen if the necessary settings in the configuration tables (like OBYC) are not maintained.
  
  
  Incorrect Transaction Type: The transaction type being used may not have a corresponding entry in the account determination table.
  
  
  Data Inconsistencies: There may be inconsistencies in the master data or transaction data that lead to the system being unable to find the appropriate account.
  
  
  Transport Issues: If the configuration was recently transported from one system to another (e.g., from development to production), there may have been issues during the transport process that resulted in missing entries.
  
  
  Solutions:
  
  
  Check Account Determination Configuration:
  
  Go to the transaction code OBYC and verify that the necessary account determination settings are maintained for the relevant transaction types (e.g., goods movements, invoice postings).
  Ensure that the account keys are correctly assigned to the relevant transaction types.
  
  
  
  Review Transaction Type:
  
  Ensure that the transaction type you are trying to process is valid and has the necessary configuration in place.
  
  
  
  Check Master Data:
  
  Review the material master and vendor/customer master data to ensure that all necessary fields are filled out correctly and that there are no inconsistencies.
  
  
  
  Transport Check:
  
  If the issue arose after a transport, check the transport logs to ensure that all necessary objects were transported correctly. You may need to re-transport the configuration if something is missing.
  
  
  
  Debugging:
  
  If the issue persists, you may need to debug the process to identify where the system is failing to find the account determination record.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to account determination for any specific guidance or known issues.
  
  
  
  Related Information:
  
  
  Transaction Codes: 
  
  OBYC: Configuration for automatic account determination.
  MM03: Display material master data.
  MM02: Change material master data.
  
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search for the error message or related keywords in the SAP Support Portal.
  
  
  Community Forums: Consider checking SAP Community forums or other SAP-related discussion boards for similar issues and solutions shared by other users.
  
  
  By following these steps, you should be able to identify and resolve the cause of the MN679 error in your SAP system.