How To Fix VBDRV079 - Derivation was not saved - error during late lock for &1, &2, &3

SAP Error Message - Details

• Message type: E = Error

• Message class: VBDRV - Derivation of Batch Characteristics

• Message number: 079

• Message text: Derivation was not saved - error during late lock for &1, &2, &3

What causes this issue?

The shipping approval runs using the "Late Lock" option. This means
that none of the sender batches are locked while you are checking the
derivation in the shipping approval. However, to ensure consistent
derivation, the system re-reads the sender batches (with lock) when you
save, and checks to make sure that the values that were sent have not
been changed.
This check failed for sender batch &V1&, &V2&, &V3&.
In other words, this batch either could not be read, could not be
locked, or the values of this batch that were sent were changed.

System Response

The derivation cannot be saved. The receiver batch is not changed.

How to fix this error?

Repeat the shipping approval for the receiver batch in question.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message VBDRV079 - Derivation was not saved - error during late lock for &1, &2, &3 ?

  The SAP error message VBDRV079 indicates that there was an issue during the late lock process when trying to save a derivation. This error typically occurs in the context of SAP's condition technique, particularly in pricing or other areas where derivations are used to determine values based on certain conditions.
  Cause:
  The error can be caused by several factors, including:
  
  Lock Conflicts: Another user or process may have locked the object you are trying to modify, preventing your changes from being saved.
  Database Issues: There may be issues with the database that prevent the saving of the derivation.
  Authorization Issues: The user may not have the necessary authorizations to perform the action.
  Configuration Errors: There may be issues with the configuration of the condition records or derivations that are causing the error.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Locks: Use transaction code SM12 to check for any locks on the object you are trying to modify. If you find any locks that are not needed, you can delete them (if you have the necessary authorizations).
  
  
  Retry the Operation: After checking for locks, try to save the derivation again. Sometimes, the issue may be temporary.
  
  
  Check Authorizations: Ensure that the user has the necessary authorizations to perform the action. You can check this using transaction code SU53 after the error occurs to see if there are any authorization issues.
  
  
  Review Configuration: Check the configuration of the derivation and ensure that all necessary settings are correct. This may involve reviewing the condition records and the logic used in the derivation.
  
  
  Database Consistency: If the issue persists, it may be necessary to check the database for consistency issues. This may require the assistance of your database administrator.
  
  
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. There may be patches or updates that resolve known issues.
  
  
  Contact SAP Support: If none of the above solutions work, consider reaching out to SAP Support for further assistance. Provide them with the error message details and any relevant logs.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like SM12 (for lock entries), SU53 (for authorization checks), and SE11 (for data dictionary) to help diagnose the issue.
  Documentation: Review SAP documentation related to the condition technique and derivations to ensure that your configuration aligns with best practices.
  User Forums: Consider checking SAP community forums or other user groups for similar issues and solutions shared by other users.
  
  By following these steps, you should be able to identify and resolve the cause of the VBDRV079 error in SAP.