How To Fix VSCE790 - Messages were saved in the application log (SLG1, object PPVA/KBMT)

VSCE790 - Overview

• Message type: E = Error

• Message class: VSCE - Messages for SCE

• Message number: 790

• Message text: Messages were saved in the application log (SLG1, object PPVA/KBMT)

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 VSCE790 - Messages were saved in the application log (SLG1, object PPVA/KBMT) ?

  The SAP error message VSCE790 indicates that there are messages saved in the application log related to the object PPVA/KBMT. This typically occurs in the context of the SAP Production Planning (PP) module, particularly when dealing with the production order or related processes.
  
  Cause:
  The error message VSCE790 is a general notification that there are issues or warnings logged in the application log (SLG1) that need to be reviewed. The specific causes can vary widely, but common reasons include:
  
  Data Issues: There may be inconsistencies or missing data in the production order or related master data.
  Configuration Errors: Incorrect configuration settings in the production planning module.
  Process Errors: Errors during the execution of a process, such as during the creation or processing of production orders.
  Authorization Issues: Lack of necessary authorizations to perform certain actions in the system.
  
  
  Solution:
  To resolve the issue, follow these steps:
  
  
  Check the Application Log:
  
  Go to transaction code SLG1.
  Enter the object as PPVA and