INTERNAL

SAP Note 3007375 – Overview and Implementation

Steps
Support for End of Service Off-Cycle Payments in Local
Version Saudi Arabia
TABLE OF CONTENTS
SOLUTION OVERVIEW .............................................................................................................................. 3
System Objects .......................................................................................................................................... 3
New Objects ............................................................................................................................................... 3
Changed Objects ....................................................................................................................................... 4
Example Scenarios .................................................................................................................................... 6

2
This document contains a solution overview and the manual implementation steps that must be followed to
install SAP note number 3007375.

SOLUTION OVERVIEW

System Objects

New Objects

Object Type Documentation

Pay EOS in Off- Feature Use

Cycle (24EOP) This feature determines whether to pay end of service (EOS)
with a regular/on-demand payroll run or with an off-cycle
payroll run.

Updated format:
x EOS payment payroll type
R or Blank Regular or on-demand payroll run
O Off-cycle run

Categories for View New entry for EOS off-cycle:

Off-Cycle
Reasons
(V_T52OCC)

Reasons for Off- View New entry for EOS off-cycle:

Cycle Payroll
Runs Customizing path:
(V_T52OCR) Payroll: Saudi
Arabia > Off-Cycle
Activities > Set Up
Off-Cycle Reasons

Keep EOS WT for Personnel Object

EOS Calculation calculation rule Personnel calculation rule for payroll
(SA93)
Use
This rule selects only the wage types that are relevant to end
of service (EOS).

Access
PIT SA93 P61 NOAB

Procedure
It keeps only the specified EOS-relevant wage types and
removes other wage types in IT.

Requirements
The payroll run must be off-cycle with reason 0099.

3
Object Type Documentation

Changed Objects

Object Type Documentation

Process EOS payout, Payroll Operation Object

provision or not? Operation
(SATER)
Use
This returns whether end of service (EOS) must be paid to
the employee or not.

If the employer does not use feature 24EOP or uses the

feature with the return value as ‘R’ (pay EOS in regular or on-
demand payroll), this checks the following cases for paying
EOS:
1. The employee is terminated in the current period
where EOS is to be paid.
2. The employee is terminated in a retro period where
EOS was to be paid.
3. Avoid paying EOS if already paid in earlier periods
after termination.
4. Avoid paying EOS in off-cycle.

If the employer uses the feature with the return value as ‘O’
(Off-cycle payroll), this operation checks the following cases
for paying EOS:
1. Pay EOS in off-cycle with off-cycle reason ‘0099’.
2. Avoid paying EOS if already paid in earlier periods
after termination.

Syntax
OOOOO – Operation Name

4
 Object Type Documentation

EoS: End of service Schema

calculation - v2.0
(SAEN)

Import Additional Schema

Payments/Deductions
(KSA) (SAP9)

Important: These objects are only delivered with a Support Package

installation. If you are not installing the solution via Support
Package, follow the steps in Note Installation Steps to install
the solution.

5
Example Scenarios

Abdullah has been hired on 01.01.2019 with a salary of SAR 10,000.00. Abdullah resigns and his last
working day is 15.06.2021. Abdullah worked for 896 days and is entitled to end of service (EOS) gratuity.
Based on how feature 24EOP is configured, the employer can pay EOS with a regular/on-demand payroll
run or with an off-cycle payroll run.

1. If the employer wants to pay the EOS gratuity with an off-cycle run on 23.06.2021 (within two weeks
after the employee separation/termination):

Feature return value: O

Note: With this setting, no EOS is paid in a regular/on-demand payroll run.

2. (Option 1) The payroll administrator runs the off-cycle workbench (t-code PUOC_24):

a. EOS can be paid any day after the employee termination.

Note: The amount must not be entered manually in IT0267. The

system will calculate the EOS amount.

b. The admin chooses Start Payroll and Yes for the warning message related to wage types:

6
 c. Finally, the admin saves the payroll run.

3. (Option 2) The HR administrator uses the payroll driver (t-code PC00_M24_CALC):

Object Documentation

Payroll Reason 0099 – EOS Payment

Payroll Type A – Bonus Payment

Payroll Identifier Payroll identifier for the off-cycle run.

Payment Date Desired payment date after employee termination,

for example, two weeks from termination.

7
a. The admin executes the off-cycle payroll run:

8
www.sap.com/contactsap

© 2021 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.

The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary softwar e components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable
for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliate d companies’ strategy and possible future developments, products, and/or platform directions and functionality are
all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation
to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from e xpectations. Readers are
cautioned not to place undue reliance on these forward-looking statements, and they should not be relied upon in making purchasing decisions.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the trademarks of their respective companies. See www.sap.com/trademark for additional trademark information and notices.