SAP HR: Understanding and Troubleshooting the “Division by Zero Not Performed” Error

In SAP HR (Human Resources) calculations, the “Division by Zero Not Performed” error can cause payroll headaches and unexpected results. This error signals an attempt within the SAP system to divide a number by zero, an impossible mathematical operation.

If you’re an SAP HR administrator or consultant, understanding why this error occurs and how to resolve it is crucial to ensuring smooth and accurate payroll processing.

Common Causes

The “Division by Zero Not Performed” error in SAP HR usually stems from these scenarios:

• Missing or Incorrect Data in Infotypes: Infotypes are SAP HR modules that store employee data. Essential info types like IT0007 (Planned Working Time) or IT0008 (Basic Pay) might have missing or zero values in calculation fields.
• Errors in PCRs: PCRs (Personnel Calculation Rules) are the code blocks within SAP HR that dictate payroll calculations. If a PCR contains a formula that tries to divide by a variable that could potentially be zero, the error may be triggered.
• Unexpected Data Scenarios: Sometimes, unusual employee data combinations, like an employee with zero planned working hours or zero basic pay, can introduce the possibility of division by zero within calculations.

Troubleshooting Steps

1. Identify the Source: Use the payroll log and error message to pinpoint the exact wage type or PCR where the error originates.
2. Scrutinize Infotype Data: Carefully examine the affected employee’s relevant info types (e.g., IT0007, IT0008). Look for missing or zero values in fields like planned working hours, number of calendar days, basic pay, etc.
3. Review PCR Logic: Meticulously debug the PCR identified in the error. Ensure all divisor variables are checked for zero values before performing division operations. Introduce code to handle potential division gracefully by zero scenarios.
4. Test Corrections: After changing info types or PCRs, thoroughly retest your payroll calculations to verify that the error has been resolved as expected.

Preventive Measures

• Robust PCR Design: Include error handling and check for zero values in your PCRs to prevent division by zero errors.
• Data Validation: Implement data validation checks during data entry to ensure critical fields in info types are not entered as zero.
• Regular Testing: Routine payroll testing and simulations can catch potential data issues and PCR errors before they become critical.

Example

Imagine a PCR that calculates an employee’s daily Rate like this:

Daily Rate = Basic Pay / Planned Working Days

If an employee’s Planned Working Days in IT0007 is zero, this PCR will try to divide by zero, resulting in the error.

Solution

Modify the PCR to include error handling:

IF Planned Working Days = 0

   Daily Rate = 0  

ELSE

   Daily Rate = Basic Pay / Planned Working Days

ENDIF