How To Fix PYC_FRW370 - Auth. prefix of check instance &1 differs from that of payroll process

PYC_FRW370 - Overview

• Message type: E = Error

• Message class: PYC_FRW - Payroll Control Center Framework

• Message number: 370

• Message text: Auth. prefix of check instance &1 differs from that of payroll process

What causes this issue?

You are trying to generate check instances for a process using the
<LS>Generate Check Instances</> (PYC_GENERATE_CONTEXT) report. The
generated check instances will be named as the combination of authority
prefix (of the process ) and the check type ID.
However the system finds an existing check instance for the check type
in the Customizing activity
<DS:SIMG.PYD_FRW_3>Define Data Source Instances</> (view cluster
VC_PYD_INST). This check instance must have been manually created.

How to fix this error?

Check the manually created check instance (the one with a different
authority prefix) of the check type in the Customizing activity
<DS:SIMG.PYD_FRW_3>Define Data Source Instances</> (view cluster
VC_PYD_INST). Delete the check instance and then run the report again.

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_FRW370 - Auth. prefix of check instance &1 differs from that of payroll process ?

  The SAP error message PYC_FRW370 indicates that there is a mismatch between the authorization prefix of the check instance and that of the payroll process. This typically occurs in the context of payroll processing in SAP, particularly when dealing with payroll results and authorization checks.
  
  Cause:
  The error is caused by a discrepancy between the authorization prefix defined for the payroll process and the one defined for the check instance. This can happen due to:
  
  
  Configuration Issues: The payroll process and the check instance may have been configured with different authorization prefixes.
  Custom Development: If there are custom developments or modifications in the payroll processing logic, they might not align with the standard authorization checks.
  Data Consistency: There may be inconsistencies in the data or configuration settings that lead to this mismatch.
  
  
  Solution:
  To resolve the PYC_FRW370 error, you can follow these steps:
  
  
  Check Configuration:
  
  Go to the configuration settings for the payroll process and the check instance.
  Ensure that