Do you have any question about this error?
Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 682
Message text: No record found for currency type &1 (internal error)
An internal table was accessed using currency type &V1&. However, no
record was found.
This is probably due to a program error.
The error occurred in form routine &V2& in function module &V3&.
INCLUDE ISR_STOP
INCLUDE NA_SYSADMIN1
Error message extract from SAP system. Copyright SAP SE.
MN682
- No record found for currency type &1 (internal error) ?The SAP error message MN682 ("No record found for currency type &1 (internal error)") typically occurs in the context of currency conversion or when dealing with currency types in financial transactions. This error indicates that the system could not find a record for the specified currency type in the relevant tables.
Causes:
- Missing Currency Type Configuration: The currency type specified in the transaction may not be defined in the system.
- Incorrect Currency Type: The currency type being referenced may be incorrect or not applicable for the transaction being processed.
- Data Inconsistency: There may be inconsistencies or missing entries in the relevant tables (e.g., T001, TCURR) that store currency information.
- Custom Development Issues: If there are custom programs or enhancements, they may not be handling currency types correctly.
- Master Data Issues: The master data for the relevant financial documents may not be set up correctly, leading to this error.
Solutions:
Check Currency Type Configuration:
- Go to the configuration settings in SAP and verify that the currency type in question is defined correctly.
- Use transaction code
OB08
to check the exchange rates and ensure that the currency type is set up properly.Verify Transaction Data:
- Review the transaction data to ensure that the correct currency type is being used.
- Check if the currency type is applicable for the specific transaction or document.
Check Relevant Tables:
- Use transaction codes like
SE11
to check the relevant tables (e.g., T001 for company codes, TCURR for currency conversion) to ensure that the necessary records exist.Review Custom Code:
- If there are any custom programs or enhancements, review the code to ensure that it correctly handles currency types and does not lead to this error.
Consult SAP Notes:
- Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
Contact SAP Support:
- If the issue persists after checking the above points, consider reaching out to SAP Support for further assistance.
Related Information:
Transaction Codes:
OB08
- Maintain Exchange RatesSE11
- Data DictionarySE80
- Object Navigator (for custom code review)Documentation: Review SAP documentation related to currency types and financial transactions for more context on how currency types are used within the system.
Testing: After making any changes, ensure to test the transactions that were previously causing the error to confirm that the issue has been resolved.
By following these steps, you should be able to identify the cause of the MN682 error and implement a solution to resolve it.
Get instant SAP help. Start your 7-day free trial now.
MN681
Provision-relevant amount not equal to 0 (internal error)
What causes this issue? In the invoice items table, one of the items in the provision-relevant correction document has an amount that is not 0, even ...
MN680
Maintain the date for currency conversion
What causes this issue? On the selection screen, you selected the field for currency conversion, but have not entered any data for currency conversio...
MN683
Balance does not equal zero: &1 &2 (internal error)
What causes this issue? A balance of &V1& &V2& occurred. This is probably due to an internal program error. The key fields (Purchasin...
MN684
The business volume data from the user exit is inconsistent
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.