How To Fix CRM_PRCIL016 - Price element entry not displayed in header; not part of total price

SAP Error Message - Details

• Message type: E = Error

• Message class: CRM_PRCIL - Messages for Pricing Condtion Genil

• Message number: 016

• Message text: Price element entry not displayed in header; not part of total price

What causes this issue?

The price element entry was distributed to the items, but was then
identified as a statistical or inactive price element. As a result, this
entry does not contribute to the total price and is no longer displayed
at header level. The price element remains at item level.

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

If the price element is also missing at item level, the system rejected
your entry (entry with errors) and it will likewise not appear at header
level.

System Response

How to fix this error?

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 CRM_PRCIL016 - Price element entry not displayed in header; not part of total price ?

  The SAP error message CRM_PRCIL016 indicates that a price element entry is not displayed in the header of a pricing document because it is not part of the total price calculation. This error typically occurs in the context of pricing in SAP CRM (Customer Relationship Management) when there is a mismatch or misconfiguration in the pricing procedure.
  Causes:
  
  Pricing Procedure Configuration: The pricing procedure may not be correctly configured to include the specific price element in the total price calculation.
  Condition Records: There may be missing or incorrect condition records for the price element in question, leading to it not being considered in the total price.
  Access Sequence: The access sequence for the pricing condition may not be set up to retrieve the relevant condition records.
  Item Category: The item category may not be configured to allow the specific price element to be included in the pricing.
  Pricing Type: The pricing type for the item may not be set to include the price element in the total price calculation.
  
  Solutions:
  
  
  Check Pricing Procedure: Review the pricing procedure assigned to the document type and ensure that the price element is included in the procedure. You can do this by navigating to the configuration settings in SPRO:
  
  SPRO > SAP Customizing Implementation Guide > Sales and Distribution > Basic Functions > Pricing > Pricing Control > Define Pricing Procedures.
  
  
  
  Review Condition Records: Ensure that the condition records for the price element are maintained correctly. You can check this using transaction VK11 (Create Condition) or VK12 (Change Condition).
  
  
  Verify Access Sequence: Check the access sequence assigned to the pricing condition type to ensure it is set up to retrieve the necessary condition records.
  
  
  Item Category Configuration: Review the configuration of the item category to ensure it allows for the inclusion of the price element in the pricing. This can be checked in:
  
  SPRO > Sales and Distribution > Sales > Sales Documents > Define Item Categories.
  
  
  
  Check Pricing Type: Ensure that the pricing type for the item is set correctly to include the price element in the total price calculation.
  
  
  Debugging: If the issue persists, consider debugging the pricing procedure to identify where the price element is being excluded from the total price calculation.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VK11, VK12, V/06 (for pricing procedure), and V/07 (for condition types).
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide additional guidance on this error message.
  Documentation: Review SAP documentation on pricing procedures and condition records for a deeper understanding of how pricing is managed in SAP CRM.
  
  By following these steps, you should be able to identify the cause of the error and implement the necessary changes to resolve it.