How To Fix PH235 - Some cluster B2 records still have the wrong version

SAP Error Message - Details

• Message type: E = Error

• Message class: PH - PA: Archiving & Reorganization

• Message number: 235

• Message text: Some cluster B2 records still have the wrong version

What causes this issue?

This personnel number still has cluster B2 records on database PCL2
whose version is not current. However, you can only archive cluster
records whose cluster version is current.

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?

INCLUDE NA_SYSADMIN1 OBJECT DOKU ID TX

Procedure for System Administrators

Start converting cluster B2 for this personnel number. This converts
the cluster records to the current version.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message PH235 - Some cluster B2 records still have the wrong version ?

  The SAP error message PH235, which states "Some cluster B2 records still have the wrong version," typically occurs in the context of payroll processing, particularly when dealing with cluster B2 records in the SAP HR module. Cluster B2 is used for storing payroll results, and this error indicates that there are inconsistencies in the versioning of these records.
  Cause:
  
  
  Version Mismatch: The error usually arises when there are discrepancies between the expected version of the cluster B2 records and the actual version present in the database. This can happen due to:
  
  Incomplete payroll runs.
  Manual changes to payroll results.
  Issues during the payroll processing or retroactive accounting.
  Data inconsistencies due to system upgrades or changes in configuration.
  
  
  
  Incorrect Configuration: Changes in payroll schema or configuration settings that affect how payroll results are processed can lead to this error.
  
  
  Data Corruption: In rare cases, data corruption in the database can lead to version mismatches.
  
  
  Solution:
  
  
  Reprocess Payroll: The most straightforward solution is to reprocess the payroll for the affected period. This can help regenerate the cluster B2 records with the correct version.
  
  
  Check Payroll Logs: Review the payroll logs for any errors or warnings that occurred during the payroll run. This can provide insights into what went wrong.
  
  
  Consistency Check: Use transaction codes like PC00_MXX_CALC (where MXX is your country-specific payroll) to run a consistency check on the payroll results. This can help identify and correct any inconsistencies.
  
  
  Cluster B2 Repair: In some cases, you may need to use specific SAP programs or transactions to repair the cluster B2 records. Consult with your SAP Basis or HR team for the appropriate tools or programs.
  
  
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that address this specific error. There may be patches or updates that resolve known issues related to cluster B2 records.
  
  
  System Upgrade: If the issue is related to a known bug in the version of SAP you are using, consider upgrading to a more recent version where the issue has been resolved.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as PA03 (Maintain HR Master Data), PC00_MXX_CEDT (for payroll results), and PC00_MXX_CWTR (for payroll cluster).
  SAP Help Documentation: Refer to the official SAP documentation for detailed information on payroll processing and cluster management.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered and resolved similar issues.
  
  If the problem persists after trying the above solutions, it may be necessary to involve SAP support for further assistance.