How To Fix SRM_GENERIC_SP820 - An internal error has occurred -- check application log

SAP Error Message - Details

• Message type: E = Error

• Message class: SRM_GENERIC_SP - SRM: Generic Service Provider

• Message number: 820

• Message text: An internal error has occurred -- check application log

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 SRM_GENERIC_SP820 - An internal error has occurred -- check application log ?

  The SAP error message "SRM_GENERIC_SP820 An internal error has occurred -- check application log" typically indicates that there is an issue within the SAP Supplier Relationship Management (SRM) system. This error can arise from various underlying causes, and resolving it often requires checking the application logs for more detailed information.
  Possible Causes:
  
  Configuration Issues: Incorrect or incomplete configuration settings in the SRM system can lead to internal errors.
  Data Inconsistencies: Inconsistent or corrupted data in the database can trigger this error.
  Authorization Problems: Insufficient user authorizations may prevent certain operations from completing successfully.
  System Bugs: There may be bugs or issues in the specific version of the SRM software you are using.
  Integration Issues: Problems with integration points between SRM and other SAP modules or external systems can also lead to this error.
  
  Solutions:
  
  
  Check Application Logs: 
  
  Use transaction code SLG1 to access the application logs. Look for entries related to the error message to get more context about what went wrong.
  
  
  
  Review Configuration:
  
  Verify that all necessary configurations in SRM are correctly set up. This includes checking settings related to purchasing, supplier management, and any custom configurations.
  
  
  
  Data Validation:
  
  Check for any inconsistencies or errors in the data being processed. This may involve validating master data, transaction data, or any relevant documents.
  
  
  
  User Authorizations:
  
  Ensure that the user encountering the error has the necessary authorizations to perform the action that triggered the error.
  
  
  
  System Updates:
  
  Check if there are any patches or updates available for your version of SAP SRM. Applying the latest support packages can resolve known bugs.
  
  
  
  Consult SAP Notes:
  
  Search the SAP Support Portal for any relevant SAP Notes that may address this specific error. SAP Notes often provide solutions or workarounds for known issues.
  
  
  
  Contact SAP Support:
  
  If the issue persists and you cannot find a resolution, consider reaching out to SAP Support for assistance. Provide them with the error details and any relevant logs.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SLG1 (Application Log), SE80 (Object Navigator), and SE37 (Function Module) for debugging.
  Documentation: Review the official SAP documentation for SRM to understand the expected behavior and configuration settings.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed.
  
  By following these steps, you should be able to diagnose and potentially resolve the "SRM_GENERIC_SP820" error in your SAP SRM system.