SAP Note 1869401 - Configuration For Divisor 30 Function For Saudi Payroll
SAP Note 1869401 - Configuration For Divisor 30 Function For Saudi Payroll
SOLUTION
Using the functionality, which is developed for Latin America countries (Note 442853 - Divisor 30
Functionality) as they consider the commercial month is always 30 days.
The payroll operations NU3, RT3,AM3 and 9LD30 has been enabled for Saudi payroll driver in order to allow
customers to use it in their schemas.
Important Notes
• Customers must include the operations and functions in their own schemas.
• Customers must test different scenarios after making all the necessary changes.
• The tasks mentioned in this guideline are mandatory and must be completed by the customer based
on their requirements.
IMPLEMENTATION STEPS
Procedure
1. From SAP Easy Access menu, choose Human Resources > Payroll > Asia/Pacific > Saudi Arabia >
Tools > Customizing Tools > Function/Operation (t-code PE04).
2. Add Saudi Arabia country assignment to the following payroll operations:
ID Description
9LDIV Divisor 30
3. Save your entries.
2. Configuring Grouping of Employee and Payroll Area for Divisor 30
Procedure
1. From SAP Easy Access menu, choose Human Resources > Time Management > Administration >
Tools > Maintain Features (t-code PE03).
2. Edit the feature Grouping of Employee and payroll area for Divisor 30 (9LDPY).
3. 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.
See Also
Features Editor
Procedure
1. Execute transaction code SM30.
2. Maintain the view Define no.of days of payroll period (V_T799L10).
3. Define the fixed number of days for a payroll period, based on your employee groupings defined in
the previous step:
Procedure
1. Execute transaction code SM30.
2. Maintain the view Define day types for Divisor 30 (V_T799L11).
3. 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:
ID Description
Note: If you have special requirements for absences, you can create additional day types for
absences with ranges Y* and Z*.
Procedure
1. Execute transaction code SM30.
2. Maintain the view Possible subtypes for Daytypes (V_T799L14):
Prerequisites
Define your own day types in the previous step.
Procedure
1. Execute transaction code SM30.
2. Maintain the view Assign day types to absences (V_T799L15).
3. Enter the codes for the personnel subarea grouping for absence and attendance types, for the
absence type and for the day type:
Procedure
1. From SAP Easy Access menu, choose Human Resources > Time Management > Administration >
Tools > Maintain Features (t-code PE03).
2. Edit the feature Grouping of Organizational Area for Divisor 30 (9LD30).
3. Define your own employee groupings to assign a priority to the day types according to the needs of
your company.
See Also
Features Editor
8. Assigning Properties to Day Types
Procedure
1. Execute transaction code SM30.
2. Maintain the view Assign priority to day types (V_T799L13).
3. Assign a priority to each day type/subtype:
Procedure
1. In the own copy of the standard schema, the following have to be inserted right after calling the PAB
function:
FUNC P1 P2 P3
-------------------------
IF SPRN
ELSE
9LDIV
ENDIF
2. Modify your own copy of rules SAPF, SAP0, SAP1 and other places that factor wage types /801,
/802 and /803 to include DIV30 customizing as per your company requirements.
Example
As highlighted, we use RT3 instead of normal RTE operation to enable the DIV30 functionality.
In a payroll run, a WPBP split happens on day 10 of the 4th month, resulting in a total of 29 days.
In the following screenshot, we implemented the functionality for /801 factor and not for /803 to highlight the
difference between the two:
Another example to a WPBP split on the 16th of the month (total days: 29):
Example for 3 splits, one on the 10 th and another on the 15 th of a 29-days month:
Copyright/Trademark