How To Fix PYC_CONF_WB070 - Semantic value & is deprecated for defining filter validation rule.

SAP Error Message - Details

• Message type: E = Error

• Message class: PYC_CONF_WB -

• Message number: 070

• Message text: Semantic value & is deprecated for defining filter validation rule.

What causes this issue?

This validation rule is used as filter by other validation rules to
suppress their alerts. You see this message because the semantic value
for semantic category <AB>PYD_CKFLTR </>for the filter validation rule
is not the validation rule ID.
<ZH>Background</>
One validation rule X can be used as filter to suppress the check
results of other validation rules (Y and Z for example). As a result, if
an alert detected by Y and Z is already raised by validation rule X, the
same alert will not be shown by Y and Z.
Prior to Configuration Workbench, this is implemented in Customizing
activity Define Check Types (under Customizing for <LS>Payroll ->
Payroll International -> Payroll Control Center -> Payroll Control
Center Configuration Simplification</>.)
For validation rule X, which is used as filter, assign the semantic
category <AB>PYD_CKFLTR </>and any pairing semantic value (for example,
ABCD).
For validation rules Y and Z, which use validation rule X as filter,
assign the semantic category <AB>PYD_NEED </>and the same pairing value
(ABCD in this case).
RESET N1
In Configuration Workbench, this is implemented by configuring alert
dependencies for validation rules:
Enable validation rule X as a filter by selecting the checkbox <LS>This
validation rule can be used by other validation rules to suppress raised
alerts </>on the <LS>Alert Dependencies </>tab page.
Add validation rule X in the alert dependencies of validation rules Y
and Z on the <LS>Alert Dependencies </>tab page.
With Configuration Workbench, you no longer need to enter a pairing
value, but the validation rule ID is used automatically as the semantic
value for <AB>PYD_CKFLTR</> if the validation rule is used as a filter.

System Response

This custom-paring-value implementation in Customizing activity is now
deprecated with the introduction of Configuration Workbench. With
Configuration Workbench, the pairing value is the ID of the filter
validation rule.
The <LS>Consistency Check for Existing Objects with Configuration
Workbench </>(<AB>PYC_SUPPORT_CWB_CONS_CHECK</>) report can update the
configuration by doing the following:
RESET N1
For filter validation rule X, change from <AB>PYD_CKFLTR = ABCD </>to
<AB>PYD_CKFLTR = ID of filter validation rule X</>.
Find all validation rules with <AB>PYD_NEED = ABCD</>. In this example,
they are validation rules Y and Z.
Check whether there are other validation rules (W, for example) that
provides a filter by using the same pairing key ABCD: <AB>PYD_CKFLTR =
ABCD</>.
If yes, for validation rules Y and Z, change from <AB>PYD_NEED = ABCD
</>to <AB>PYD_NEED = ID of filter validation rule X</>.
If no other filter validation rules use the same pairing value
<AB>PYD_CKFLTR = ABCD</>, then for validation rules Y and Z, change from
<AB>PYD_NEED = ABCD </>to <AB>PYD_NEED = ID of filter validation rule X
</> and delete the entry <AB>PYD_NEED = ABCD</>.
<ZH>Result</>
Validation rule X is still used as filter by relevant validation rules.
But now the pairing semantic value is the ID of the filter validation
rule X rather than a custom semantic value. This is the required logic
of Configuration Workbench.

How to fix this error?

(Recommended) If you want the report to apply the abovementioned
solution for you, choose <LS>Apply Solution </>in the application
toolbar bar on the <LS>Display All Convertible Configurations </>page of
the report.
If you want to change the configuration by yourself, you can manually
edit alert dependencies for relevant validation rules in Configuration
Workbench or edit the semantic values of relevant validation rules in
Customizing activity <LS>Define Check Types</>.

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 PYC_CONF_WB070 - Semantic value & is deprecated for defining filter validation rule. ?

  The SAP error message PYC_CONF_WB070 indicates that a semantic value you are trying to use for defining a filter validation rule is deprecated. This typically occurs in the context of SAP's Profitability and Cost Management (PCM) or similar modules where certain configurations or settings may have been updated or replaced in newer versions of the software.
  Cause:
  
  Deprecated Semantic Value: The semantic value you are using has been marked as deprecated in the current version of SAP. This means that it is no longer recommended for use and may be removed in future releases.
  Version Upgrade: If your system has been recently upgraded, some semantic values that were previously valid may no longer be supported.
  Configuration Changes: Changes in the configuration settings or updates to the business rules may have led to the deprecation of certain values.
  
  Solution:
  
  Identify the Replacement: Check the SAP documentation or release notes for the version you are using to find out what the recommended replacement for the deprecated semantic value is. SAP often provides alternatives or new values that should be used instead.
  Update the Configuration: Once you have identified the new semantic value, update your filter validation rule configuration to use the new value instead of the deprecated one.
  Consult SAP Notes: Look for relevant SAP Notes that may provide additional guidance or fixes related to this error. You can search for notes in the SAP Support Portal.
  Testing: After making the changes, test the configuration to ensure that it works as expected and that the error message no longer appears.
  
  Related Information:
  
  SAP Help Portal: The SAP Help Portal contains documentation on various modules, including PCM, which may provide insights into deprecated values and their replacements.
  SAP Community: Engaging with the SAP Community can be helpful. Other users may have encountered the same issue and can share their solutions or workarounds.
  SAP Support: If you are unable to resolve the issue, consider reaching out to SAP Support for assistance. They can provide specific guidance based on your system configuration and version.
  
  By following these steps, you should be able to resolve the error message PYC_CONF_WB070 and continue with your configuration tasks in SAP.