How To Fix 5F139 - Absence of split SV during change of contribution &1 &2

SAP Error Message - Details

• Message type: E = Error

• Message class: 5F - HR F: Error Messages (France)

• Message number: 139

• Message text: Absence of split SV during change of contribution &1 &2

What causes this issue?

The contribution &V2& of the body &V1& has changed during the period
&V3& to &V4&. The change is not accompanied by an SV split in payroll.
The contribution amount cannot be distributed between the two
contribution validity periods.

System Response

The system issues an error message and discontinues processing.

How to fix this error?

If you wish to change the properties of the contribution, delimit the
employee's infotype <ZH>Social Insurance</> (0064) at the change date in
order to generate an SV split.
Otherwise, correct the definition of the contribution rates
&V2& of the body &V1& (tables T5F1C and T5F1C1) so that the properties
of the contribution remain unchanged for the entire period &V3& to &V4&.

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 5F139 - Absence of split SV during change of contribution &1 &2 ?

  The SAP error message 5F139, which states "Absence of split SV during change of contribution &1 &2," typically occurs in the context of payroll processing or when handling contributions in the SAP Human Capital Management (HCM) module. This error indicates that there is an issue with the split of social security (SV) contributions during a change in contribution types or amounts.
  Cause:
  The error can be caused by several factors, including:
  
  Missing Split Entries: The system expects a split of contributions (e.g., between different social security types) but cannot find the necessary entries in the relevant tables.
  Incorrect Configuration: The configuration for the contribution types may not be set up correctly, leading to inconsistencies in how contributions are processed.
  Data Inconsistencies: There may be inconsistencies in the employee master data or payroll results that prevent the system from processing the contribution changes correctly.
  Timing Issues: The error may occur if the contribution change is being processed at a time when the system expects a different state of data (e.g., during a payroll run).
  
  Solution:
  To resolve the error, you can take the following steps:
  
  Check Configuration: Review the configuration settings for the contribution types in the SAP system. Ensure that the splits for social security contributions are correctly defined.
  Review Employee Data: Check the employee master data for any inconsistencies or missing information related to contributions. Ensure that all necessary data is present and correct.
  Analyze Payroll Results: Use transaction codes like PC_PAYRESULT or similar to analyze the payroll results for the employee in question. Look for any anomalies or missing entries related to contributions.
  Run Consistency Checks: Use SAP tools to run consistency checks on the payroll data. This can help identify any discrepancies that need to be addressed.
  Consult Documentation: Refer to SAP documentation or notes related to this error message for any specific guidance or patches that may be available.
  Contact SAP Support: If the issue persists after checking the above points, consider reaching out to SAP support for further assistance. They may provide insights based on the specific version of SAP you are using.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as PA30 (Maintain HR Master Data), PC00_MXX_CALC (Payroll Calculation), and PC_PAYRESULT (Display Payroll Results).
  SAP Notes: Search for SAP Notes related to error 5F139 in the SAP Support Portal, as there may be specific fixes or recommendations provided by SAP.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.