How To Fix W4101 - &: & dependent consignment price records exist

SAP Error Message - Details

• Message type: E = Error

• Message class: W4 - Messages for material discontinuation

• Message number: 101

• Message text: &: & dependent consignment price records exist

What causes this issue?

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

System Response

How to fix this error?

First archive the dependent consignment price records for the material.
You can then
archive the material itself.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message W4101 - &: & dependent consignment price records exist ?

  Certainly! Here's a detailed explanation for the SAP error message:
  
  SAP Error Message:
  W4101 & : & dependent consignment price records exist
  
  Cause:
  This warning message typically occurs when you attempt to delete or change a condition record (such as a price condition) that has dependent consignment price records linked to it. In SAP, consignment price records are special pricing conditions used in consignment processes, and they often depend on standard pricing conditions.
  
  The system detects that there are existing consignment price records that rely on the condition record you are trying to modify or delete.
  Deleting or changing the base condition record without addressing the dependent consignment records could lead to inconsistent pricing data.
  
  
  Explanation:
  
  The first placeholder (&) usually contains the condition type or condition record number you are trying to change or delete.
  The second placeholder (&) refers to the dependent consignment price record(s) that exist and prevent the operation.
  
  
  Solution:
  
  
  Check Dependent Records:
  
  Identify the consignment price records dependent on the condition record you want to change or delete.
  Use transaction codes like VK13 (Display Condition) or VK12 (Change Condition) to view the condition records.
  You can also use SE16N or SE16 to check tables like KONP (Condition Item Data) or KONH (Condition Header Data) for dependencies.
  
  
  
  Delete or Adjust Dependent Consignment Price Records:
  
  If you want to delete the base condition record, first delete or adjust the dependent consignment price records.
  If you want to change the base condition record, ensure that the changes are consistent with the dependent consignment price records.
  
  
  
  Use Correct Procedure:
  
  Follow the proper sequence: first handle dependent consignment price records, then proceed with the base condition record.
  This avoids data inconsistencies and system warnings/errors.
  
  
  
  Consult Pricing Procedure:
  
  Review the pricing procedure configuration to understand how consignment pricing is set up and linked to standard pricing conditions.
  
  
  
  
  Related Information:
  
  Consignment Pricing: In SAP SD, consignment stock is stock that is stored at the customer’s premises but still owned by the vendor until consumption. Pricing for consignment stock often involves special condition records.
  Condition Records: Pricing in SAP is controlled by condition records, which can be standard prices, discounts, surcharges, or special prices like consignment prices.
  Tables to Check:
  
  KONV: Condition values (transaction data)
  KONP: Condition item data
  KONH: Condition header data
  
  
  Transactions:
  
  VK11: Create Condition Record
  VK12: Change Condition Record
  VK13: Display Condition Record
  
  
  SAP Notes: Check SAP OSS notes for any known issues or patches related to consignment pricing and condition record dependencies.
  
  
  Summary:
  
  Cause: Attempting to delete/change a condition record that has dependent consignment price records.
  Solution: Identify and delete or adjust dependent consignment price records before modifying the base condition record.
  Related Info: Understand consignment pricing setup, use appropriate transactions, and check relevant tables for dependencies.
  
  
  If you need help with specific transaction steps or further troubleshooting, feel free to ask!