Configuration for Divisor 30 function

for Saudi Payroll Note 1869401

Overview
In Saudi Arabia, some companies use 30 days as a fixed for a Payroll month (Commercial Month), and
because of Hijri (Islamic) Calendar, the actual month could be either 29 days or 30 days.
During a month of 29 days, a WPBP split may lead to incorrect salary calculations. Typically, this happens
during a mid-month promotion or a mid-month salary change.

Solution
The solution to solve this issue is a functionality originally developed for Latin America countries (Note
442853 - Divisor 30 Functionality ), as they consider the commercial month is always 30 days.
Payroll operations NU3, RT3, AM3 and 9LD30, and function 9LDIV, are technically enabled for the Saudi
Arabia payroll driver in order to allow customers to use it in their schemas.

IMPORTANT NOTES
-

This function is designed to work with only Regular Payroll, and is not supported with Special
Payroll.
This functionality is not a standard delivery within the Saudi Payroll schema; it is only enabled
for customers based on their specific requirements.
Customers will have to include the mentioned operations and functions in their own schemas.
Customers will have to test different scenarios after making all the necessary changes to ensure
supported scenarios are working as expected.
The tasks mentioned in this guideline are mandatory and it has to be done by the customer
based on the requirements.
In case of an unsupported scenario, the customer has to adjust their own schemas, or to
implement a custom development in order to adjust the results.
For more information, refer to note Note 442853 - Divisor 30 Functionality, and system
documentation for payroll function 9LDIV, operations 9LD30, NUM3,RT3 and AM3.

Guidelines
Configuration
1- Feature 9LDPY:
You define your own employee groupings to set the fixed number of days for the payroll period.
Note: The return value will be used for defining the grouping in the customizing tables later.
To obtain more information about how to maintain features, use the transactions extended
help.

2- View V_T799L10: Define number of days of payroll period

In this step of the Implementation Guide, you define the fixed number of days for a payroll
period.
You must define your own employee groupings in the previous step.

3- View V_T799L11: Define day types for Divisor 30:

In this step of the Implementation Guide, you define the day types used within the "Divisor 30"
functionality.
Standard settings
The standard offers the following day types, which are fixed and cannot be changed:
o WORK Worked days
o PABS Paid absences
o UABS Unpaid absences
o GABS Generic absences
o INAC Inactive days
If you have special requirements for absences, you can create additional day types for
absences with range Y* and Z*.

4- View V_T799L14 : Possible subtypes for Day types

5- View V_T799L15: Assign day types to absences:

In this step of the Implementation Guide, you assign day types to your absence types.
Requirements
Before executing this step you need to:
o Define your own day types in the previous step.
- Enter the codes for the personnel subarea grouping for absence and attendance types, for
the absence type and for the day type.

6- Feature 9LD30: Define employee grouping to assign priority to day types

In this step of the Implementation Guide, you define your own employee groupings to
assign a priority to the day types according to the needs of your company.
To obtain more information about how to maintain features, use the transactions extended help.

7- View V_T799L13: Assign priority to day types: In this step of the Implementation Guide, your
assign a priority to each day type/subtype.

Payroll Objects
1.

In the own copy of the standard schema, the following have to be inserted right after calling the
PAB function :
Note: This function is designed to work with only Regular Payroll run, and not supported with Special
Payroll Run.

FUNC
P1
P2
P3
------------------------IF
SPRN
ELSE
9LDIV
ENDIF

2.

Modify your own copy of rules SAPF, SAP0, SAP1 and other places factors /801 or /802 or /803
or all of them to take into account the DIV30 customizing as per your company requirements.

Example:

As Highlighted, use RT3 instead of normal RTE operation to get use of DIV30
functionality.
In Payroll Run, a WPBP split happens on 10th of the 4th month which is total 29 days:
In the following screenshot, we implemented for /801 factor and not for /803 in
order to get the difference between both of the functionalities.

Another example to a WPBP split in 16th of the month (Total days 29 days) :

Example for 3 splits, on 10th then 15th of a 29 days month: