1. iEnabler Salary Claims
Presenter: Cheryl Whitmore
Date: 13th March 2013

2. iEnabler Salary Claims Contents
Introduction
Purpose & Benefits
An overview of the setup requirements and the claims process
System Operational Definitions
Routing Setup Requirements
Changes to existing reports / new report
Questions

3. iEnabler Salary Claims Introduction
Standard development available from Integrator3.
A license for iEnabler Personnel System must exist in order to make use of the iEnabler Salary Claim functionality.
The availability of the iEnabler options may be setup in the Business Process driver {PWEBM-1,2}. Select privileges can be defined on {USERS-2}.
A Salary Claim is a claim where an agreement exists between the Employer and Employee and a Secondary Contract exists on
{PAOP-2}.

4. iEnabler Salary Claims Introduction
Purpose of the development:
To provide an electronic format for submission, cancellation, approval, rejection and tracking of salary claims.
To programmatically create the claim on {FPRIC-1 pg2}.

5. iEnabler Salary Claims Introduction
Benefits of the development:
It provides an on-line procedure which is vastly superior to the current paper based method.
The employees can track all claims that they have submitted.
Payroll department can control the cycles for which claims may be submitted electronically.
Payroll department can run a report to determine claims that have been submitted but not yet approved.

6. iEnabler Salary Claims An overview of the setup requirements
A new Event Type ‘H’ ‘Cycle For Web Claims Entry’ has been developed on the Run Cycle Control File {FPRM-2}
The Month /Year
linked to Event Type
‘H’ on {FPRM-2}
controls the contracts
that display on
iEnabler & the cycles
for which claims may
be submitted.

7. iEnabler Salary Claims An overview of the setup requirements
A valid Secondary Contract {PAOP-2} must exist for the employee
In order to display on
iEnabler, the Start Date
and End Date will be
validated to the Month
and Year set on Event
Type ‘H’ on {FPRM-2}.

8. iEnabler Salary Claims An overview of the setup requirements
The Current Post
Code and Secondary
Post Code may be
the same.

9. iEnabler Salary Claims An overview of the setup requirements
ED Codes that may
be used are to be
linked to a Group
Code on {FPRC-7}.
The Group Code
is indicated by a SOD,
Code ‘CE’ on
{FPRM-9}.

10. iEnabler Salary Claims An overview of the setup requirements
Remuneration Units
(applicable to
Rate x Quantity claims)
are to be defined on
{PACS2-6} and linked to
the Secondary Contract.
Where a Contract Rate
exists, a Remuneration
Unit is mandatory.

11. iEnabler Salary Claims An overview of the setup requirements
The Start & End
salary levels for
claims are to be
linked to the
Appointment Types
on {FPRG-10}.
The Salary Level
Appointment Type
of the Employee
will be defaulted and
is a mandatory field. overlap.

12. iEnabler Salary Claims An overview of the setup requirements
Direct Supervisor field
is mandatory.
The Employee appointed
to the Senior Post Code,
linked to the Secondary
Post Code on {PACS-4}
will be defaulted.

13. iEnabler Salary Claims An overview of the setup requirements
Maintain Claims {FPRIC-1 pg2}
The claim is populated.
A new Indicator has
been developed to
determine the status
of the claim.

14. iEnabler Salary Claims An overview of the claims process
There are three new Web applications
for the Claims process:
Appointment Contract Claims
(Claims may be submitted or cancelled
from this form)
Approve Contract Claims
Contract Claims Approval Progress
(The progress of a submitted claim
may be tracked from this form)

15. iEnabler Salary Claims An overview of the claims process
Appointment Contract Claims
Secondary Contracts that meet the requirements will be displayed, in addition to the Claim Status of previous claims for the contract.
The employee can either submit a claim or cancel a claim by clicking on the applicable Action.

16. iEnabler Salary Claims An overview of the claims process
To submit a claim, the
employee will choose the
applicable contract, enter
the payroll year /month
and either amount or
quantity, depending on how
the contract has been
defined.

17. iEnabler Salary Claims An overview of the claims process
The Supervisor will receive
an advising of the claim
submitted.
The claim will be populated
on {FPRIC-1 pg2}.

18. iEnabler Salary Claims An overview of the claims process
The same Routing
Request will be used for
both the Submission &
Cancellation of Claims.
Claims can be cancelled
after they have been
approved, providing they
have not been processed
i.e. have not been copied
to Payroll {FPRIC-3}.

19. iEnabler Salary Claims An overview of the claims process
Approve Contract Claims
The Supervisor can view all
applicable claims and action
the Claim by clicking on the
Routing Request number.
The status of the Claim will be
updated on {FPRIC-1 pg2}.

20. iEnabler An overview of the claims process
The status of the claim/s
submitted can be tracked
by the Employee.

21. iEnabler Salary Claims System Operational Definitions {FPRM-9}
System Operational Definitions (SOD’s) {FPRM-9} – for Routing Setup
Code ‘CR’ Secondary Contract Claims Routing Type
Routing Request Type {GROU-1} for iEnabler Salary Claims.
Default (PACL) is installed.

22. iEnabler Salary Claims System Operational Definitions {FPRM-9}
Code ‘CA’ Secondary Contract Claims Approval Outcome Code
for approval of iEnabler Salary Claims.
Default (APR) is installed.

23. iEnabler Salary Claims System Operational Definitions {FPRM-9}
Code ‘CD’ Secondary Contract Claims Reject Outcome Code
for rejection of iEnabler Salary Claims.
Default (PREJ) is installed.

24. iEnabler Salary Claims System Operational Definitions {FPRM-9}
Code ‘CS’ Secondary Contract Claims Cancel Seq Outcome Code
The seq in the Route from where notification of the cancellation of the
claim will be started.
Default (100) is installed.

25. iEnabler Salary Claims Routing Set-up Requirements
Routing Set-up for Approval /Rejection /Cancellation of Claims
A default set-up will be installed, Type ‘PACL’ (SOD ‘CR’)
A single level approval process will be installed, however a multi-level may be implemented.
The Approval process will start with sequence number 0
The same Routing Request Number will be used for both the Approval and Cancellation of the Claim. A Claim can be cancelled after it has been Approved providing it has not been processed (i.e. Copied to Payroll).

26. iEnabler Salary Claims Routing Set-up Requirements
When a Claim is cancelled:
- All open Routing Seq Numbers will be cancelled, using ‘.’ as the Outcome Code.
- The sequence for the Notification of the Cancellation will be started (SOD ‘CS’)

27. iEnabler salary Claims Changes to existing reports
The following programs have been changed:
Pro-forma Payslip {FPRI-25}
Leave Credit Calculation {PLOP-2}
List Secondary Appointments {PBOPR1-2}, {FPRICR-1}
Calculate Budget Values {MSBOP-2}

28. iEnabler Salary Claims New report {FPRIC-5}
List of Unapproved Claims {FPRIC-5} – for payroll staff to follow-up

29. iEnabler Salary Claims Questions

30. Disclaimer
The information, comments and material presented in this presentation are provided for information purposes only. The presentation is not addressing all possible technical or business aspects and does not claim to be complete or exhaustive.
ITS reserves the right to change its business or product development plans as circumstances dictate.
This document may not be reproduced or distributed without the written permission of ITS Holdings (Pty) Ltd.

31. Thank you