How To Fix PYC_FRW371 - The value of input parameter PYP_PROC_INST for &1 must not be maintained

PYC_FRW371 - Overview

• Message type: E = Error

• Message class: PYC_FRW - Payroll Control Center Framework

• Message number: 371

• Message text: The value of input parameter PYP_PROC_INST for &1 must not be maintained

What causes this issue?

You have defined the parameter value for the input parameter type
PYP_PROC_INST for check type &v1& in the Customizing activity
<DS:SIMG.PYD_FRW_3>Define Data Source Instances</> (view cluster
VC_PYD_INST) <LS>-> Instance Input Parameter</> view.
The value of this input parameter type PYP_PROC_INST is generated during
run time. Therefore, you must not manually define the value for this
parameter type.

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?

Make sure that the check type has only the following input parameters
assigned to it:
Parameter Type,,Fixed,,Mandatory,,No Key
PYP_PROC,,Yes,,Yes,,--
PYP_PROC_INST,,--,,Yes,,--
By using the <LS>Generate Check Instances</> (PYC_GENERATE_CONTEXT)
report, you don't need to, and must not, define the parameter value for
these input parameters.

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_FRW371 - The value of input parameter PYP_PROC_INST for &1 must not be maintained ?

  The SAP error message PYC_FRW371 indicates that there is an issue with the input parameter PYP_PROC_INST in the context of a planning process. This error typically arises in the SAP Business Planning and Consolidation (BPC) or SAP Integrated Business Planning (IBP) environments when a certain parameter is not expected to be set or is incorrectly configured.
  
  Cause:
  The error message suggests that the input parameter PYP_PROC_INST (which usually refers to a process instance in planning) is being maintained or set when it should not be. This can happen due to:
  
  Incorrect Configuration: The planning process or the script logic may have been incorrectly configured to expect a value for PYP_PROC_INST when it should not.
  Version Mismatch: There may be a mismatch between the version of the planning model and the parameters being passed.
  User Input Error: A user may have inadvertently entered a value for a parameter that should remain empty.
  
  
  Solution:
  To resolve the error, you