How To Fix CFD_REGISTRY_CHECK185 - Performance: Condition Field &1 is not a constant but read from &2

SAP Error Message - Details

• Message type: E = Error

• Message class: CFD_REGISTRY_CHECK - Custom Fields: Messages for Registry Check

• Message number: 185

• Message text: Performance: Condition Field &1 is not a constant but read from &2

What causes this issue?

Condition field <(>&<)>1 is not defined as a constant within the view
hierarchy, but instead its value is selected from database table
<(>&<)>2. This will break the "self-join" optimization" (HANA SP11) and
could therefore lead to performance issues for CDS view extensions.

System Response

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

How to fix this error?

Define condition field <(>&<)>1 as a constant in the corresponding
branches of the union in the relevant subview, e.g.
cast( 'X' as sdraft_is_active ) as IsActiveEntity
cast( ' ' as sdraft_is_active ) as IsActiveEntity

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 CFD_REGISTRY_CHECK185 - Performance: Condition Field &1 is not a constant but read from &2 ?

  The SAP error message CFD_REGISTRY_CHECK185 indicates a performance issue related to the use of a condition field in a pricing procedure or similar context. The message states that the condition field (&1) is not a constant and is being read from a table or structure (&2), which can lead to performance degradation.
  Cause:
  
  Dynamic Condition Fields: The condition field being referenced is not a constant value but is instead being dynamically read from a database table or structure. This can lead to performance issues because the system has to access the database to retrieve the value each time it is needed, rather than using a pre-defined constant.
  Inefficient Pricing Logic: The pricing logic may be designed in a way that requires frequent database access, which can slow down processing times, especially in high-volume transactions.
  
  Solution:
  
  Use Constant Values: If possible, modify the pricing procedure or logic to use constant values for condition fields instead of dynamically reading them from a table. This can significantly improve performance.
  Review Pricing Procedure: Analyze the pricing procedure to identify if the condition field can be simplified or if the logic can be optimized to reduce database access.
  Check Custom Code: If there is custom code involved, review it to ensure that it is not unnecessarily reading from the database when a constant value could be used.
  Performance Tuning: Consider performance tuning options in SAP, such as indexing the relevant tables or optimizing the database queries involved in retrieving the condition field values.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error message or provide guidance on optimizing performance in pricing procedures.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have implemented.
  Transaction Codes: Familiarize yourself with transaction codes related to pricing procedures (e.g., V/08 for maintaining pricing procedures) to make necessary adjustments.
  Performance Analysis Tools: Utilize SAP performance analysis tools (like ST05 for SQL trace or ST12 for ABAP trace) to identify bottlenecks in the pricing logic.
  
  By addressing the underlying cause of the error and implementing the suggested solutions, you can improve the performance of your SAP system and resolve the CFD_REGISTRY_CHECK185 error message.