How To Fix PYC_CONF_WB140 - The provided data &1 is not defined in table PYC_D_PROV.

PYC_CONF_WB140 - Overview

• Message type: E = Error

• Message class: PYC_CONF_WB -

• Message number: 140

• Message text: The provided data &1 is not defined in table PYC_D_PROV.

What causes this issue?

This issue only happens for step templates created outside of
Configuration Workbench.
When a step template provides data for validation rules, it has the
semantic category <AB>PYD_PROV</> and a semantic value (<AB>CALC </>for
payroll data, or other customer-defined values for other data) in
Customizing activity <DS:SIMG.PYD_FRW_1>Define Data Source Types</>.
These customer-defined semantic values in the Customizing activity are
not recognized by Configuration Workbench (which keeps the semantic
values in table <AB>PYC_D_PROV</>).

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

System Response

The configuration still takes effect, but you cannot display or edit it
in Configuration Workbench.

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 PYC_CONF_WB140 - The provided data &1 is not defined in table PYC_D_PROV. ?

  The SAP error message PYC_CONF_WB140 indicates that the system is unable to find the specified data in the table PYC_D_PROV. This typically occurs in the context of SAP Profitability and Cost Management (PCM) or SAP Profitability Analysis (PA) when the system is trying to access configuration or data that has not been properly defined or is missing.
  
  Cause:
  
  Missing Configuration: The data you are trying to access or use is not defined in the relevant configuration tables, specifically in PYC_D_PROV.
  Incorrect Data Entry: There may be a typo or incorrect entry in the data you are trying to use.
  Data Deletion: The data might have been deleted or not yet created in the system.
  Transport Issues: If the configuration was transported from another system, it may not have been transported correctly.
  
  
  Solution:
  
  Check Configuration: Verify that the data you are trying to access is correctly defined in the PYC_D_PROV table. You can do this by using transaction