How To Fix DPR_FC014 - Make sure that condition &1 is compatible with object category &2

DPR_FC014 - Overview

• Message type: E = Error

• Message class: DPR_FC - Field Control for Project Management

• Message number: 014

• Message text: Make sure that condition &1 is compatible with object category &2

What causes this issue?

For each condition that SAP delivers in field control, an appropriate
include exists with a schema program that the system uses to generate
the field control class.
Example: The include 'EVAL_CONDS_C001' exists for the condition 'C001'.
<EX>/>EVAL_CI_C001<(><<)>/</>
<EX>,,data: lr_<(>&<)>objectname& type ref to cl_dpr_<(>&<)>objectname&.
</>
<EX>,,data: ls_condition type ts_condition_per_node.</>
<EX>,,* check if object is released</>
<EX>,,lr_<(>&<)>objectname& ?= ir_root_object.</>
<EX>,,if lr_<(>&<)>objectname&->is_released( ) eq cl_dpr_co=>sc_true.</>
<EX>,, ls_condition-condition_value = cl_dpr_co=>sc_true.</>
<EX>,,else.</>
<EX>,, ls_condition-condition_value = cl_dpr_co=>sc_false.</>
<EX>,,endif.</>
<EX>,,ls_condition-node_name = iv_node_name.</>
<EX>,,ls_condition-node = ir_object.</>
<EX>,,ls_condition-condition_id = 'MV_C001'.</>
<EX>,,insert ls_condition into table mt_conditions.</>
<EX>,,/>END<(><<)>/</>
When it generates the field control class, the system replaces the
variable '<NP><(>&<)>objectname<(>&<)>'</> by the appropriate object
category.
Example: When you assign the condition 'C001' to the object category
'DPO' (project definition), the system replaces <NP>'<(>&<)>objectname
<(>&<)>'</> by <NP>'PROJECT_O'</> during generation. Therefore, the
first line from this example would be:
<EX>,,data: lr_PROJECT_O type ref to cl_dpr_PROJECT_O.</>
The object-specific method or value assignment calls used in the
implementation must be valid for the object category.
Example: The following is an example of the coding generated for the
object category 'DPO':
<EX>,,lr_PROJECT_O ?= ir_root_object.</>
<EX>,,if lr_PROJECT_O->is_released( ) eq cl_dpr_co=>sc_true.</>
The corresponding method <NP>lr_PHASE_T->is_released()</> does not exist
for the object 'PPT' (phase in template) because this would cause a
syntax error in the generated class.

System Response

The system cannot automatically check whether the condition is
compatible with the object category.
If the assignments are incompatible, the system generates a syntax error
or the program may terminate when the field control class or its usage
is generated in the application.

How to fix this error?

Check the schema program to see if it is compatible with the object
category.
If the program terminates, check your field control settings and field
control classes.
If the selected condition is not compatible with the object category,
create a customer-specific condition and assign it to the object
category (see SAP Note 947936).
For more information about setting up field control, see:
Customizing for <LS>Project Management</> under <ZK>Global Enhancements
to Project Elements</> -> <ZK>Set Up Field Control</>
SAP Note 947936

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 DPR_FC014 - Make sure that condition &1 is compatible with object category &2 ?

  The SAP error message DPR_FC014, which states "Make sure that condition &1 is compatible with object category &2," typically occurs in the context of project management or project-related transactions in SAP, particularly when dealing with conditions that are not compatible with the specified object category.
  
  Cause:
  This error usually arises due to one of the following reasons:
  
  
  Incompatible Condition Type: The condition type you are trying to use is not valid for the specified object category. For example, if you are trying to apply a cost condition to a project that does not support that type of cost condition.
  
  
  
  Configuration Issues: There may be configuration settings in the SAP system that define which conditions are valid for which object categories. If these settings are not correctly configured, it can lead to this error.
  
  
  Data Entry Errors: There might be a mistake in the data entry where the wrong condition type is selected for the object