How To Fix VK860 - Screen &1 &2 saved

SAP Error Message - Details

• Message type: E = Error

• Message class: VK - Pflege und Bearbeitung von Konditionen

• Message number: 860

• Message text: Screen &1 &2 saved

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 VK860 - Screen &1 &2 saved ?

  The SAP error message VK860 typically indicates that there is an issue related to the saving of a screen or transaction in the context of pricing or condition records. This message can occur in various scenarios, particularly when working with pricing procedures, condition types, or when trying to save changes in the pricing master data.
  Cause:
  
  Data Inconsistency: There may be inconsistencies in the data being processed, such as missing mandatory fields or incorrect data formats.
  Authorization Issues: The user may not have the necessary authorizations to save changes in the relevant transaction or screen.
  Technical Issues: There could be a technical issue with the SAP system, such as a temporary glitch or a problem with the database.
  Configuration Errors: Incorrect configuration in the pricing procedure or condition records can lead to this error.
  
  Solution:
  
  Check Data Entry: Ensure that all required fields are filled out correctly and that the data entered is valid. Look for any fields that may be highlighted or marked as errors.
  Review Authorizations: Verify that the user has the necessary authorizations to perform the action. This can be checked with the help of a system administrator.
  System Logs: Check the system logs (transaction SLG1) for any additional error messages or warnings that may provide more context about the issue.
  Technical Support: If the issue persists, consider reaching out to your SAP Basis team or technical support for assistance. They can check for any underlying technical issues or system errors.
  Configuration Review: If you suspect a configuration issue, review the pricing procedure and condition records to ensure they are set up correctly.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VK11 (Create Condition), VK12 (Change Condition), and VK13 (Display Condition) for managing pricing conditions.
  SAP Notes: Check SAP Notes for any known issues or patches related to the error message VK860. SAP Notes can provide specific guidance or fixes for known problems.
  Documentation: Review SAP documentation related to pricing procedures and condition records for best practices and troubleshooting tips.
  
  If you continue to experience issues, consider consulting with your SAP support team or a professional with expertise in SAP pricing and condition management.