How To Fix VBDRV036 - Saving in derivation cancelled

SAP Error Message - Details

• Message type: E = Error

• Message class: VBDRV - Derivation of Batch Characteristics

• Message number: 036

• Message text: Saving in derivation cancelled

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 VBDRV036 - Saving in derivation cancelled ?

  The SAP error message VBDRV036 ("Saving in derivation cancelled") typically occurs in the context of the SAP Sales and Distribution (SD) module, particularly when dealing with condition records or pricing procedures. This error indicates that the system was unable to save the derivation of a condition record due to some issues in the configuration or data.
  Causes:
  
  Missing or Incorrect Configuration: The derivation strategy or rules may not be correctly configured in the system.
  Data Inconsistencies: There may be inconsistencies in the data being processed, such as missing master data or incorrect condition records.
  Authorization Issues: The user may not have the necessary authorizations to perform the action.
  Technical Issues: There could be underlying technical issues, such as database locks or system performance problems.
  
  Solutions:
  
  
  Check Configuration:
  
  Review the condition derivation settings in the customizing (transaction code SPRO).
  Ensure that all necessary derivation rules are correctly defined and activated.
  
  
  
  Validate Data:
  
  Check the master data (e.g., customer master, material master) to ensure that all required fields are filled and correct.
  Verify that the condition records are properly maintained and do not have any inconsistencies.
  
  
  
  Review Authorizations:
  
  Ensure that the user has the necessary authorizations to create or modify condition records. This can be checked in transaction SU53 or by consulting with your security team.
  
  
  
  Check for Technical Issues:
  
  Look for any system messages or logs that might indicate a technical issue (e.g., transaction SM21 for system logs, ST22 for dumps).
  If there are database locks, you can check transaction SM12 to see if any locks are preventing the save operation.
  
  
  
  Debugging:
  
  If the issue persists, consider debugging the process to identify where the error occurs. This may require assistance from a technical consultant.
  
  
  
  Consult SAP Notes:
  
  Search for relevant SAP Notes in the SAP Support Portal that might address this specific error message or provide patches or updates.
  
  
  
  Related Information:
  
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  SPRO: Customizing settings
  VK11/VK12: Create/Change condition records
  VK31: Maintain condition records in bulk
  SE11: Data dictionary to check table structures
  SE80: Object Navigator for debugging
  
  
  
  Documentation: Review SAP documentation related to condition management and pricing procedures for a deeper understanding of how derivation works.
  
  
  If the problem continues after trying the above solutions, it may be beneficial to reach out to SAP support or consult with an experienced SAP SD consultant for further assistance.