How To Fix PYC_CONF_WB070 - Valeur sémantique & refusée pour définition règle de validation de filtre

SAP Error Message - Details

• Message type: E = Error

• Message class: PYC_CONF_WB -

• Message number: 070

• Message text: Valeur sémantique & refusée pour définition règle de validation de filtre

Quelle est la cause de ce problème?

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.

Réponse du système

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.

Comment corriger cette erreur?

(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</>.

Procédure pour les administrateurs système

Le système émet un message d'erreur et ne vous permettra pas de poursuivre cette transaction tant que l'erreur n'est pas résolue.

Extrait du message d'erreur du système SAP. Copyright SAP SE.