Overview of the iEnabler Appointments

This system may be used to  

• distribute the workload and responsibility for the appointment of temporary - and fixed term contract staff to departments outside the Human Resources section 
• empower departments to appoint temporary- and fixed term contract staff with minimal involvement from the Human Resources section

The term "Fixed term contract appointments" is here used to refer to personnel appointment for a fixed term (i.e. with an end date) where the appointment contract has a fixed benefits. (A fixed monthly salary amount with fixed benefits). The person appointed may be appointed with a leave package with the standard leave types.

It is suited to institutions

• with large numbers of temporary staff, mostly paid by claim
• where the appointment of these staff members may be done in a distributed fashion
• and where institutional policy dictates service benefits to the extent that very little variation occur
• resulting in the direct involvement of the Human resources section in these appointments to be minimal.

Features of the Module

• The departure point of the system is that policy regarding the choice of Appointment Type {PACS-1}, Rank {PACS-2}, Leave Package {PLCS-1}, Grade and Stats Category used in the Service Records {PBOP-2} for appointments done through  the iEnabler is determined by the length of employment and a type of person appointed (or the type of work the person will perform) 
• For this purpose, the system administrator must 
• specify a set of Person Types {PACS2-1}
• specify a set of Employment Periods {PACS2-2}
• indicate the Valid Appointment Types {PACS2-3} applicable to the Person Type / Employment Period combination and 
• indicate the Rank, Leave Package, Grade and Stats Category applicable for each Person Type / Employment Period / Appointment Type combination.
• link Earning Codes {FPRG-6} and/or iEnabler Secondary Contract Claim Type Rules {PACS2-14} to Person Types {PACS2-1} and Remuration Types {PACS2-4} on {PACS2-12}
  
• restrict personnel members (iEnabler Users) to Departments with Maintain Restrictions {PACS2-9}. A user will only be able to use posts linked to the department(s) he/she is restricted to when capturing an appointment. (Note that the restrictions only applies to the person capturing the data and not the approver(s)).
• The end user appointing a person will then simply 
• specify start- and end dates for the appointment
• select the Person Type from a list of available Person Types for the employment period (derived from the start- and end date)
• select the Appointment Type (limited to those applicable for the Person Type / Employment Period)
  
  The Rank, Leave Package, Grade and Stats Category will then be derived from the above information. (Note that the default Rank indicated for each Post {PACS-4} plays no role here)

• Only personnel that is linked to restriction type “PAPD” for a specific department will be allowed to capture appointments for the department.
• One personnel member may be linked to multiple departments via the   restriction type “PAPD” in {PACS2-9}.
• The module will only allow the appointment of personnel for a fixed period of time (in other words, where the appointment has an end date) and will always create a Secondary Appointment Contract {PAOP-2} for each appointment. 
• New Service Records {PBOP-2} will only be created where new personnel members are appointed or for periods within the Start- and End Date of the appointment where Service Records for the person does not already exist. (That means that in the case of the appointment of an existing personnel member to a secondary post, the existing service record will be retained).

• The Posts {PACS-4} that may be used for appointments are limited those where "Allow iEnabler Appointments" is set to (Y)es or 'E' (Yes - External Appointments).

• The system will determine the monitory value of the appointment and validate that funds for the appointment is available. (Refer to the iEnabler Appointment Budget Validation for more detail)
• For this purpose, the iEnabler Appointments were developed to use one of the following four different remuneration models (Remuneration Types {PACS2-4}) for each appointment
• A - Ad Hoc Claims
• The total value of the appointment is supplied by the end user. The Secondary Appointment Contract {PAOP-1} of the appointment is created with this value as the Maximum Amount Allocated
• M - Fixed Monthly Claims
• A fixed amount per month is derived from information supplied by the end user and set-ups done by the systems administrator. The Secondary Appointment Contract{ PAOP-1} of the appointment is created with this value as Monthly Claim.
• R - Rate times Quantity
• The Contract Rate and Maximum Quantity of the Secondary Appointment Contract{ PAOP-1} of the appointment is derived from information supplied by the end user and set-ups done by the systems administrator.
• Y - Annual Salary Amount
• An Annual Salary Amount is supplied by the user. The system will divide the amount by twelve to obtain a monthly claim value for the Secondary Appointment Contract{ PAOP-1}
• The available Remuneration Types per Employment Period {PACS2-5} must be entered by the System Administrator.
• For the Rate times Quantity model, 
• the system makes provision for different Remuneration Units {PACS2-6}. Examples of units are 
• An amount per hour
• An amount per day
• An amount per examination paper that was marked 
• the Remuneration Rate {PACS2-7} applicable for each Remuneration Unit / Person Type / Rank combination must be specified by the system administrator.
• For the Fixed Monthly Claims model, the Remuneration Rate {PACS2-7} applicable for each Person Type / Rank combination must be specified by the system administrator. (In this case, Remuneration Unit will always be "M").

Note that the remuneration models used by this system are all based on the "Claims against Secondary Appointment Contracts {FPRI-27}" - functionality. The Valid Appointment Types {PACS2-3} will therefore not allow the use of Appointment Types {PACS-1} where the field "Pay By Claim" is set to (S)alary.

Appointment Types {PACS-1} that is indicated as (P)ermanent may be classified as "Pay By Claim" if the System Operational Definition {GCS2-11} "PT - Allow Permanent Appointment as Claims" is set to "Y".

• The module will facilitate a user configurable approval and notification process through the Routing System {GMAIN-4} by creating a Routing Request as soon as the end user indicates that the appointment of a personnel member is ready for approval (Refer to iEnabler Appointments {P00008-0} for detail about the "Ready for Approval" functionality and iEnabler Appointment Routing for detail about the Routing Request that is created).

• The module is integrated with ITS Document Storage {GSYS-8} and documents may be uploaded as part of the appointment. Two Document Categories {GDOCS-1} are used:
• A Document Category {GDOCS-1} for the upload of documentation in support of the appointment, the Document Category is to be indicated in the System Operational Definition {GCS2-11} "DS - Supporting Documents" for Subsystem "HR". 
• The following default values will be provided with the system
• Document Category to be used: "HRAPP - iEnabler Appointment Documents"
• Prompts for Document Category "HRAPP - iEnabler Appointment Documents" 

Prompt Number	Prompt	Reference Type	Reference Object
1	Personnel Number	Numeric	NUM
2	Post	Alphabetic	POST
3	Start Date	Date	DTE

• A Document Category {GDOCS-1} for the upload of copies of Work Permits for Foreign Staff members, the Document Category is to be indicated in the System Operational Definition {GCS2-11}  "DW -  Upload Copy of Work Permit" 
• The following default values will be provided with the system
• Document Category to be used: "HRAWP - Upload Copy of Work Permit"
• Prompts for Document Category "HRAWP - Upload Copy of Work Permit.

Prompt Number	Prompt	Reference Type	Reference Object
1	Personnel Number	Numeric	NUM
2	Permit Number	Alphabetic	ALIENPERMIT
3	Start Date	Date	DTE

• If an existing personnel member is re-appointed, the final approval for the modifcation of bank details may be done separately from the approval for the appointment.

· Only “normal” persons may be appointed. Legal requirements around things like CC’s, Trusts, et cetera, may be too complex and should be handled in the back-office system by trained staff.

Implementation Sequence

1. The Appointments Module {PMAIN-2} of the ITS Personnel System should be fully operational before this system is implemented.
2. Define the Person Types {PACS2-1} that will be available
3. Define the Employment Periods {PACS2-2}
4. Enter the Valid Appointment Types {PACS2-3} for each Person Type / Employment Period combination. In addition, indicate the Rank, Leave Package, Grade, Stats Category and Fixed Tax Rate indicator for each Person Type / Employment Period / Appintment Type combination.
5. Define Remuneration Types {PACS2-4}
6. Define the Remuneration Types per Employment Period {PACS2-5}
7. If the "Rate times Quantity" model is to be used, enter the Remuneration Units {PACS2-6} 
8. Enter the Remuneration Rate {PACS2-7} applicable for each Remuneration Unit / Person Type / Rank.
9. Validate the set up of the iEnabler Appointments {PACS2-8} and correct the set up errors each time the set-up is modified.
10. The Cost Centre and Account Number linked to the Post {PACS-4} the person will be appointed in, will display on the iEnabler screen.
11. A popup screen will also display all previous appointments.The following information is displayed:

                1.   Appointment Type and Description
                2.   Temporary/Permanent
                3.   Post Code and Description
                4.   Start date
                5.   End date

12. An Internal Note field is available where information may be captured for office use only.
13. Restrict personnel members (iEnabler Users) to Departments. A user will only be able to use posts linked to the department(s) he/she is linked to through the User Restriction {PACS2-9} "PAPD - Web Appointment Dept Access" when capturing an appointment. (Note that the restrictions only applies to the person capturing the data and not the approver(s)).
14. A report can be extracted for all Approval iEnabler Appointments {PACSR2-10}
15. Changes to iEnabler Appointments are written away to an Audit Trail {PAOPR2-25 OR FPRNR1-27}
16. Organisational Contacts {GCS-10}. This Option is used for reporting purposes to determine who has to Approve Data and Depends on Seniority.
17. Funding Bodies {GCS-23} can be set for Internal or External bodies.
18. User Defined Contact/Address/Communication Types {GCS-24}. The relevant types must be set-up to default.
19. .Indicate the Posts {PACS-4} that will be available for iEnabler Appointments and enter the budget amounts for the posts in the "Post Funding"-tab of Posts {PACS-4}.
20. Set up the approval routing (including email notification) for the iEnabler Appointments. Refer to iEnabler Appointment Routing for more detail.
21. Ensure that the set up for documents to be uploaded is in place. The Document Category may be linked to screens in the ITS back-office system with "Link Documents to Application Programs" {GDOCS-4} to allow back-office users easy access to the documents.
22. The system may be set up so that the option that will be used for the approval of an appointment displays a document containing institutional policies and rules that regulate the use of the iEnabler Appointment System to appoint personnel members and then require the end user to accept the policies and rules before proceeding with the approval. The document is typically an internal document for each institution and the set up is as follows

• Prepare the document and save it in the itsdocs - directory under the ITS home directory in the file system of the application server.

• Indicate the URL that will be used to open the document in the Description-field of External Conversion Codes {GOPS-21} for the record where the External Body is "WEB", the External Code Type is "ARR - iEnabler Appointments Rules and Regulations" and the Internal Code is "URL"

• Indicate the MIME Type that will be used to open the document in the Description-field of External Conversion Codes {GOPS-21} for the record where the External Body is "WEB", the External Code Type is "ARR - iEnabler Appointments Rules and Regulations" and the Internal Code is "MTYPE". The table below contains possible MIME Types, 

MIME Type	File Extension
application/pdf	pdf
application/msword	doc
application/vnd.ms-powerpoint	ppt, pps or ppz
text/html	htm or html

 23.Validate Equal Work for Equal Pay

The hourly rate of a person being appointed can be setup to be validated to a minimum hourly rate for the Person Type /Appointment Type combination.  If the hourly rate of the appointment is less than the minimum hourly rate defined, the user will be forced to enter a valid Reason Code.  If required, the Reason Description can be included in the email notifications.

Please Note: Only ‘Temporary’ Appointment Types as defined on {PACS-1} will be validated.  Although Permanent Appointment Types may be used if SOD ‘PT’ = ‘Y’ (allow Permanent Appointment Types as Claims) {GSC2-11}, these will not be validated.

a) The following fields must be setup on {PACS2-3} for each Person Type /Appointment Type Combination:
i) ‘Validate Equal Work for Equal Pay’
            Yes
            No   
            Null
      ii) ‘Compare Min Pay’ (i.e. how must the minimum pay be compared?)
            1 = Use Rank of Post
            2 = Use Rank of the Person /Appointment Type Combination
            3 = No check

b) The minimum hourly rate for Ranks used for iEnabler Appointments must be defined on {FPRG-2}; this hourly rate will be used when doing the validation.
c) If the person being appointed is being paid less than the minimum hourly rate of the Rank, it will be mandatory for a Reason Code as defined on {PACS2-10} to be entered.
d) A generic message, in addition to the Reason Code Description, will be written to the routing system which may be displayed in emails that are generated for notification purposes.
    The generic message is defined in {GOPS-21}
         External Body =  ‘HRA’ HR Appointments
         External Code Type = ‘BLM’ Below minimum pay message
e) In order to validate Equal Work for Equal Pay, the hourly rate of the appointment must be calculated.
       (i) Where Remuneration Types as detailed below, exist on {PACS2-3}, the ‘Maximum Hours per Month’ field should have a value greater than 0 defined; this will force the user capturing the appointment to enter the total number of hours of the appointment:
            R – Rate Time Quantity
            A – Ad Hoc Claims
            O – USER-DEFINED MONTHLY RATE
            U – USER-DEFINED RATE x QUANTITY
       To calculate the hourly rate, the total amount of the appointment is divided by the total hours of the appointment.

        (ii) For the following Remuneration Types:
              Y – Annual Salary Amount
              M – Fixed Monthly Claim
To calculate the hourly rate, the number of months of the appointment is first determined by Start Date less End Date.  This is then divided by 21.67 days per month x 8 hours per day.  The total amount of the appointment is divided by the total hours of the appointment.
f) Once the hourly rate has been determined it is validated as follows:
        (i) Compare Min Pay: use Rank of Post {PACS2-3}
              The Rank is selected from the Post the person is being appointed to as defined on {PACS-4}, the minimum hourly rate of the Rank is selected from {FPRG-2}

       (ii) Compare Min Pay: use Rank of the Code {PACS2-3}
             The Rank as defined for the applicable Person Type /Appointment Type combination the person is being appointed to is selected.  The minimum hourly rate of the Rank is selected from {FPRG-2}

g) Should the hourly rate of the appointment be less than the defined hourly rate, a question is displayed on the iEnabler Appointment screen ‘Reason why person is not being paid Equal work for Equal Pay?’, with a List of Values containing valid Reason Codes as defined on        {PACS2-10}. It is a mandatory field and the user must select a valid Reason Code.

24. Validate if appointments are greater than 3 months

The appointment period of a person being appointed can be setup to be validated and if it is for a period greater than 3 months, the user will be forced to enter a reason why. If required the Reason Description can be included in the email notification.

    a) The following field must be defined on {PACS2-11} for each Person Type /Remuneration combination:
        Validate Appointment Greater than 3 months?
        Yes
        No
        Null
    b) Reason Codes why the appointment is greater than 3 months are defined on {PACS2-11}
    c) A generic message in addition to the Reason Code Description will be written to the Routing System which may be displayed in emails that are generated for notification purposes.
         The generic message is defined on {GOPS-21}
         External Body = ‘HRA’ HR Appointment
         External Code Type = ‘AM3’ Appointed for more than 3 months message
    (d) Should the appointment period be greater than 3 months, a question is displayed on the iEnabler Appointment screen ‘Reason for employment greater than 3 months’ with a List of Values containing valid Reason Codes {PACS2-11}.  It is mandatory and the user must                select a valid Reason Code.

25. Functionality of Event Type 'W' {FPRM-2} was developed to control appointments on the iEnabler.

Overview :

• Rules for event “W”
• The Start and End Date of Event Type 'W' (WEB Appointment Cut-off Date), determines which appointments on the iEnabler will be allowed; the Start and End Date of these appointments must fall within the Start and End date of event “W”.

• The cycle as setup on event “W” in  {FPRM-2} refers to the current payroll cycle that is in process and the End date of the appointment must be greater or equal to the 1st date of event “W” cycle which implies that the person is in service for Event ‘W’ cycle period.
• The following rules apply taking into account the points above:
• If the end date of the appointment is less than the 1st day of the Cycle of Event “W” the appointment will not be allowed as it will be deemed that the payroll for the last month of the appointment has already been processed.
• The end date of any appointment must be greater than the 1st day of the cycle of event “W”.
• This process will also allow back dated appointments depending on the Start Date linked to Event “W” and the system will create claims for the following two Remuneration Types on approval:
• Annual Salary Amount
• Fixed Monthly Amount

The months of the appointment less than and equal to the Cycle of Event “W” will be created in the Cycle of Event “W”.  Claims for cycles greater than the Cycle of Event “W” will be created in the correct future cycles.

• Examples:

   Case 1 – The appointment falls within the Start and End Date of Event “W” and the appointment end date is greater than the 1st day of Event  “W” cycle.
              Appointment: 01-Jan-2015 to 31-Jun-2015
              Event ‘W’ Cycle: 201503 at the time of capturing the appointment
              Event ‘W’ Wycle: 201504 at the time of approving the appointment
              Event ‘W’ Start and End Date:   01-Jan-2015  - 31-Dec-2015
              Payment Method: Fixed monthly amount R1000   
              Total claim of appointment: R6000
              Default salary level: 15
              ED Code – 0003 – Claims amt

  This appointment will be allowed if budget check allows it. If approved the following claims will be created in {FPRIC-1} with a status of approved ‘A’    

              0003   201504    15  1000 – Claim for 201504
              0003   201504    16  1000 – Claim for 201503
              0003   201504    17  1000 – Claim for 201502
              0003   201504    18  1000 – Claim for 201501
              0003   201505    15  1000
              0003   201506    15  1000      

 Case 2 – The end date of the appointment at the time of capturing was greater than the 1st day of Event ‘W’ Cycle and the start and end date of the appointment fell within the Start and End Date period of Event “W”.  However, when approved the person was not in service    because the Cycle of Event “W” was moved to the next Cycle.

               Appointment: 01-Jan-2015 to 31-Mar-2015
               Event ‘W’: 201503 at time of capturing appointment.
               Event ‘W’: 201504 at time of approving the appointment
               Event ‘W’ Start and End Date:   01-Jan-2015  - 31-Dec-2015
               Payment Method: Fixed monthly amount R1000   
               Total claim of appointment: R3000
               Default salary level: 15
               ED Code : 0003 – Claims amt

 This appointment will be allowed and claims will be generated in {FPRIC-1} with a status of approved ‘N’.  Manual intervention will be required to determine if rollbacks /recalcs or late calcs will be done or if the end date of the appointment will be  extended. Once this has been determined, the Status of the claims are to be changed from ‘N’ to ‘A’ {FPRIC-1}

             0003   201503    15  1000 – Claim for 201503
             0003   201503    16  1000 – Claim for 201502
             0003   201503    17  1000 – Claim for 201501

 Case 3 – At the time of capturing the appointment the Cycle of Event ‘W’ was less than the end date of the appointment and the appointment end date is greater than the End Date of Event “W”.
             Appointment: 01-Jan-2015 to 31-Mar-2015
             Event ‘W’: – 201502 at the time of capturing the appointment
             Event ‘W’: Start and End Date   01-Jan-2015  - 28-Feb-2015
             Payment Method: Fixed Monthly Amount R1000   
             Total claim of appointment: R3000
             Default salary level: 15
             ED Code:  0003 – Claims amt

  This appointment will not be allowed because the end date of the appointment is greater than the End Date of Event ‘W’

  Case 4 – At the time of capturing the start date of the appointment was greater than the 1st day of Event “W” Cycle , but the start and end date of the appointment falls within the Start and End Date of Event W

              Appointment:  01-May-2015 to 31-Jul-2015
              Event ‘W’: 201504 at point of capturing the appointment
              Event ‘W’: 201504 at point of approving the appointment
              Event ‘W’: Start and End Date   01-Jan-2015  - 31-Dec-2015
              Payment Method: Fixed Monthly Amount R1000   
              Total claim of appointment: R3000
              Default salary level: 15
              ED Code:  0003 – Claims amt

  This appointment will be allowed and the following claims will be created in {FPRIC-1} with a Status of approved ‘A’

              0003   201505    15  1000 – Claim for 201505
              0003   201506    15  1000 – Claim for 201506
              0003   201507    15  1000 – Claim for 201507

  Case 5 –At the time of capturing the Cycle of Event ‘W’ was less than the start date of the appointment, but the start and end date of the appointment falls outside the Start and End Date of Event ‘W’

              Appointment: 01-May-2015 to 31-Jul-2015
              Event ‘W’: 201504 at time of capturing the appointment
              Event ‘W’  Start and End Date:   01-jan-2015  - 30 Apr-2015
              Payment method: Fixed monthly amount R1000   
              Total claim of appointment:  R3000
              Default salary level: 15
              ED Code : 0003 – Claims amt

  This appointment will not be allowed because the appointment end and start date falls outside the Start and End date of Event ‘W’

  Case 6 – At the time of capturing the appointment the Cycle of Event ‘W’ is greater than the end date of the appointment, but the start and end date of the appointment falls within the Start and End Date of Event ‘W’

              Appointment: 01-Jan-2015 to 31-Mar-2015
              Event ‘W’: 201505 at the time of capturing the appointment
              Event ‘W’ Start and End Date:   01-Jan-2015  - 31-Dec-2015
              Payment Method:  Fixed monthly amount R1000   
              Total claim of appointment: R3000
              Default salary level: 15
              ED Code:  0003 – Claims amt

  This appointment will not be allowed because the end date of the appointment is less than cycle of Event ‘W’.     

1. The system will require acceptance of the policies and rules every time the user attempts to approve an application unless the value in System Operation Definition {GCS2-11} parameter "RR - Show Appointment Rules and Regulations Only Once" for Subsystem "HR" is set to "Y", in which case it will be required once for a user and then never again.
2. The following System Operation Definition {GCS2-11} parameters for Subsystem "HR" should be set

Code	Description	Processing Rules
CM	Default Campus for Posts	The value in this field will default into the field Campus Code when a new Post {PACS-4} is created
DS	Supporting Documents	Document Category {GDOCS-1} of documents that may be uploaded as part of the appointment
DW	Upload Work Permit	Document Category {GDOCS-1} of documents that may be uploaded as copies of Work Permits
E1	Secondary Appointment Earning for Annual Amounts	The Earning Code {FPRG-6} of the Earning to be used in the Secondary Appointment {PAOP-2} for  appointments where the remuneration model is "Y - Annual Salary Amount"
E2	Secondary Appointment Earning for Ad Hoc Claims	The Earning Code {FPRG-6} of the Earning to be used in the Secondary Appointment {PAOP-2} for  appointments where the remuneration model is "A - Ad Hoc Claims"
FB	Funding Body for Commitments	The Funding Body {GCS-23} to be used in the Post Funding - tab of Posts {PACS-4} by the iEnabler Appointment Budget Validation when reserving funds for an appointment.
RR	Show Appointment Rules and Regulations Only Once	If this value is set to "N", the iEnabler Appointment Approvals {P00008-1} will require the user to Accept the Policies and Rules every time the appointment of a personnel member is approved.
SI	Service Record Indicator	The value of the Service Record Indicator {PACS-28} to be used when a Service Record {PBOP-2} is created by the iEnabler Appointments System.
U1	UIF Contributing Status	The UIF Status to be used when a Service Record {PBOP-2} is created by the iEnabler Appointments System and a Global Earning/Deduction {FPRG-6} for the Appointment Type {PACS-1} exists where the Calculation Method is "B - Unemployment Insurance".
U2	UIF Contributing Reason	The UIF Contributing Reason to be used when a Service Record {PBOP-2} is created by the iEnabler Appointments System and a Global Earning/Deduction {FPRG-6} for the Appointment Type {PACS-1} exists where the Calculation Method is "B - Unemployment Insurance".
U3	UIF Non-Contributing Status	The UIF Status to be used when a Service Record {PBOP-2} is created by the iEnabler Appointments System and no Global Earning/Deduction {FPRG-6} for the Appointment Type {PACS-1} exists where the Calculation Method is "B - Unemployment Insurance".
U4	UIF Non-Contributing Reason	The UIF Contributing Reason to be used when a Service Record {PBOP-2} is created by the iEnabler Appointments System and no Global Earning/Deduction {FPRG-6} for the Appointment Type {PACS-1} exists where the Calculation Method is "B - Unemployment Insurance".
SR	Service Record Indicator - Mandatory for iEnabler appointments	If this value is set to 'Y', the Service Record Indicator on the iEnabler appointments will be a mandatory field. Note that the Service Record Indicator will always be mandatory if Validation Control {GOPS-22} "P2 - Service Record Ind Mandatory" is set to (Y)es, regardless of the setting of this System Operational Definition.
PM	Default Payment Method. Che(Q)ue, (C)ash, (M) Bank Transfer or (T)ape Transfer	Valid values are Q, C, M, T OR NULL{FPRI-1}
RC	Default value for Receiver of Revenue to be used for iEnabler Appointments	Validate against {FPRC-2} FASROR
DC	Default email address to send email to when Disability Code entered.	Email to be sent to default email address when Disability Code entered o iEnabler Appointments.
SA	Must SARS Addresses only be displayed and not normal addresses for iEnabler Appointments	If this value is set to "Y" then addresses in SARS format will be displayed as entered on {PBOP-1 pg5} or {PBOP-12}
BA	Cell Number Mandatory for iEnabler Appointments	If this value is set to "Y" Cell number will be mandatory.
HA	iEnabler Appointments HTTP HOST inc.port	Email address to be entered
U7	Allow Duplicate iEnabler Appointments	If this value is set to "Y", Duplicate iEnabler Appointments will be accepted.
U8	UIF Status for Last Months' Service Record	The value if entered will default previous month's UIF Status.
ID	Character to replace ID  Numbers on the Web Service	The value if entered will be used to replace ID numbers.
AD	Force Mandatory SARS Fields on Entry (SA)	If this value  is set to "Y" the SARS Fields will be Mandatory.
PT	Allow Permanent Appointments as Claims	If this value is set to "Y", Permanent Appointments will be allowed as Claims
E3	Email address mandatory iEnabler Appointments	If this is set to "Y" the Email Address will be made mandatory.
MU	Upload Docs mandatory for existing staff.	The upload/View Button must work like this : Currently this button is mandatory for new and existing staff. If existing staff member on PAA and if SOD below is 'Y', then this button greyed out(no mandatory) If new staff , this button is mandatory, irrespective of what this SOD is.
CA	Choose Approvers: iEnabler Appointments	This value will default to "N" - change to "Y" for the screen to re-direct to choose approvers.
SC	Create Secondary Contract only After Applicant Accepted the appointment.	This value will default to "Y" will create Secondary Contract.If "N" will create Secondary Contract after final approval.
DI	Allow Duplicate ID Numbers	If this is set to "Y" duplicate ID Numbers will be allowed.
DE	Default ED code for Salaried Secondary Contracts	If this value allows an ED code to be defined for Secondary Contracts.
EG	Default ED Group Code for Paid-By-Claims Secondary Contracts.	A default ED Group can be set for Paid-By-Claims Secondary Contracts.
E4	Secondary Appointment Earning/Deduction Code User-defined Rate x Quantity Details	Secondary Appointment Earning /Deduction Code User-defined Rate x Quantity Default Earning / Deduction Code to use if not set up.
SF	Default Service Record Indicator for UIF Service Record	This value will default if entered.
SS	Secure Server : WEB Appointment Applicant Confirmation	If the value is "Y" the applicant will have to Confirm/Accept the Appointment.
IT	Income Tax Number Mandatory	If the value is "Y" the income Tax number must be completed and pass the modulus 10 check.
LT	NMMU LS - Required Approver Rank for appointments > 3 monthjs	This is the max rank required all personnel with a rank from 1 up to this rank  qualify to approve appointments greater than 3 months.

Maintain System Operational Definition {FPRM-9}

CA	Sec Contract Claims Approve OC	The Outcome Code used to indicate Approval of Salary Claims against Secondary Appointment Contracts. Refer to Approve Contract Claims {P00011-2}.
CD	Sec Contract Claims Reject OC	The Outcome Code used to indicate Rejection of Salary Claim against Secondary Appointment Contracts.Refer to Approve Contract Claims {P00011-2}
CE	E/D Group for Claims Earnings	The E/D Group (Refer to Management Report Structure  {FPRC-7} that contains the Earnings Code that may be used for in Secondary Appointment Contracts {PAOP-2}  for Claims.
CR	Sec Contract Claims Routing Tp	The routing Request Type {GROU-1}  to be used for the approval of Salary Claims against Secondary Appointment Contracts.Refer to Approve Contract Claims {P00011-2}
CS	Sec Contract Claims Cancelled Seq	The Sequence in the Routing Request {GROU-1} to be used when a Salary Claim against a Secondary Appointment Contract is Cancelled. Refer to Appointment Contract Claims {P00011-2}

The following two options are available in the Personnel iEnabler

• iEnabler Appointments {P00008-0}
• iEnabler Appointment Approvals {P00008-1}
• Query WEB Appointments with Financial Detail {P00008-3}
• Query Web Appointments without Financial Detail {P00008-9}
• Query Status of Web Appointments in Process {P00008-5}
• Query Rejected Web Appointments {P00008-7}
• Query Routing statuses on Web Appointments {P00008-8}
• A page that the appointee can use to confirm acceptance of the Appointment {P00008-2}

• Refer to Implementation sequence nr 13 : GCS-10 is used to validate approver details.

History of Changes

Date	System Version	By Whom	Job	Description
02-Apr-2009	v01.0.0.0	Frans Pelser	t156583	New document
06-Jul-2010	v01.0.0.1	Goodman Kabini	t165108	- Add the Feature of the Module for system administrator restriction on   iEnabler Users to Departments. - Add SR Code on table 15.
01-Mar-2012	v03.0.0.0	Frans Pelser	T180941	Add Validation "P2" to rule of SOD SR
21-Aug-2014	v03.0.0.1	Samu Ntshangase	T198356	Added new SODs from GCS2-11 and FPRM-9
04-Nov-2015	v03.0.0.2	Sakhile Ntimane	T198769	Added new Code NMMU and its description
14-Aug-2019	v04.1.0.0	Nomhle lubisi	T236816	Added claim type rules