How To Fix VBDRV072 - Derivations are not confirmed

SAP Error Message - Details

• Message type: E = Error

• Message class: VBDRV - Derivation of Batch Characteristics

• Message number: 072

• Message text: Derivations are not confirmed

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 VBDRV072 - Derivations are not confirmed ?

  The SAP error message VBDRV072, which states "Derivations are not confirmed," typically occurs in the context of the SAP Sales and Distribution (SD) module, particularly when dealing with pricing and condition records. This error indicates that the system was unable to confirm the derivation of certain values, such as pricing conditions, from the master data or configuration settings.
  Causes:
  
  Missing Condition Records: The required condition records for pricing might not be maintained in the system.
  Incorrect Configuration: The configuration settings for pricing procedures or condition types may not be set up correctly.
  Inconsistent Master Data: There may be inconsistencies in the master data (e.g., customer master, material master) that affect the derivation process.
  User Exits or BAdIs: Custom logic implemented through user exits or Business Add-Ins (BAdIs) may be interfering with the standard derivation process.
  Pricing Procedure Assignment: The pricing procedure may not be correctly assigned to the sales document type or customer.
  
  Solutions:
  
  Check Condition Records: Ensure that all necessary condition records are created and active. You can do this by navigating to the condition maintenance transaction (e.g., VK11, VK12).
  Review Pricing Procedure: Verify that the pricing procedure assigned to the sales document type is correct and that all required condition types are included.
  Validate Master Data: Check the relevant master data (customer, material, etc.) for completeness and correctness. Ensure that the necessary data is maintained.
  Debug Custom Logic: If there are any custom user exits or BAdIs that might affect pricing, review and debug them to ensure they are functioning as intended.
  Analyze Logs: Use transaction codes like SLG1 (Application Log) to check for any logs related to the error, which may provide more context on what went wrong.
  Consult Documentation: Review SAP documentation or notes related to pricing and condition derivation for any specific guidance or known issues.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VK11 (Create Condition), VK12 (Change Condition), and VK13 (Display Condition).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  SAP Community: Engage with the SAP Community or forums for insights from other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, it may be beneficial to consult with an SAP functional consultant who specializes in the SD module for further assistance.