Approve Appointments

This option is used for approval of applications. 

• If the user is required to accept the policies and rules before being allowed to proceed. (Refer to the paragraph on the implementation sequence in the Overview of the iEnabler Appointment System {P00003-4} for detail)
• Display the document referred to with the set up of the External Conversion Codes {GOPS-21} for External Body "WEB" and External Code Type "ARR - iEnabler Appointments Rules and Regulations".
• Present a button to allow the user to "Accept" or "Reject" the policies and rules.
• Once the user accepted the policies and rules a screen that will allow the user to assign an outcome to the sequence of the routing request will be presented.
• The personnel number and name of the person to be appointed as well as the routing request number and routing sequence number will be displayed
• To enable the end user to view the data fields related to the appointment to be approved, this option will display the data in the Email Instruction Lines of the Routing Sequence to be approved as set up in Maintain Default Request Information {GROU-1}. This allows the system administrator to decide what data to display at what level of the approval process.
• A colon (":")  may be used to manipulate the data in each Email Instruction Line to appear in a two-column format. 
• If the text in the Email Instruction Line contains a colon, all text before the colon will be in the first column (formatted like a field label) and all other text will appear in the socond column. 
• If the Email Instruction Line contains no colon, the text will appear in the second column.
• A text area for comments is presented. This may be used by the end user to enter details of corrections to be made to the appointment details in cases where the appointment is referred back to the original person requesting the appointment for corrections. (Refer to outcome code "PCOR" below).
• A button to allow the user to view documents linked to the appointment or to upload new documents is presented.
• A field to allow the user to assign an outcome code is presented. In addition to the normal processing as set up in Maintain Default (Routing) Request Information {GROU-1}, the following outcomes will be processed according to the rules described below.
  
  

  Outcome Code	Description	Processing Rules
  PREJ	Reject an Appointment	This outcome will release the funds reserved for the appointment by the iEnabler Appointment Budget Validation  so that it is available for other appointments
  PRAP	Appointment ready for approval	This outcome is automatically assigned by iEnabler Appointments {P00008-0} when the user indicates that the appointment is ready for approval and the Post {PACS-4} has "(Y) - Yes" in the field iEnabler Appointments. Note that it must never be linked to any sequence except sequence 0.
  PREX	Appointment ready for approval	This outcome is automatically assigned by iEnabler Appointments {P00008-0} when the user indicates that the appointment is ready for approval and the Post {PACS-4} has "(E) - Yes (Extenal Appointment)" in the field iEnabler Appointments. Note that it must never be linked to any sequence except sequence 0.
  PCOR	Send back for Corrections	This outcome will Release the funds reserved for the appointment by the iEnabler Appointment Budget Validation Create sequence 0 of a new routing request with the same data as in sequence 0 of the existing routing request as well as the comments entered by the user. The purpose of the comments is to indicate the data to be corrected The appointment will then appear in the list of incomplete appointments of iEnabler Appointments {P00008-0} for the original user to do the corrections required and then to re-submit the appointment. The comments will display as a note at the top of the relevant screen in the iEnabler Appointments {P00008-0} so that the original user can see what corrections should be done.
  PAPP	Approve Appointment	This outcome will appoint the person in the the ITS Personnel System.  Note that bank details of existing personnel members will not be updated, the update of bank details should be handled by a separate sequence in the routing request with the outcome as described below. For Remuneration Type “Fixed Monthly Amount” and “Annual Amount”, Salary Claims for all the relevant months will automatically be generated on Appointment into the "Claims against Secondary Appointment Contracts" {FPRI-27} facility
  PPAP	Approve Bank Details	This outcome will update the bank details of the appointee in the ITS Personnel System
  PAAA	Applicant Accepted Appointment	This outcome will update the personal details of the appointee in the ITS Personnel System.
  PADA	Applicant Declined Appointment	This outcome will release the funds reserved for the appointment by the iEnabler Appointment Budget Validation  so that it is available for other appointments

  
  

• If an existing person is re-appointed with the module, existing service record information will be written to sequence 0 of the routing request. The HR Department should examine the information and make corrections to any “Tax Breaks”, “Breaks in Service”, “UIF Statusses and Reasons” et cetera if required
• Remuneration of personnel appointed through the iEnabler Appointments should be handled as follows
• For Remuneration Type "A - Ad Hoc Claims" and "R - Rate times Quantity", refer to the "Overview of Claims against Secondary Appointment Contracts {FPRI-27}" for information on how to handle the claims.
• Before each Payroll Calculation, all claims should be copied to the Individual Earnings/Deductions {FPRI-2} using Copy Claims to PRS {FPRIC-3}

• Details of each appointment are logged in the Salary Related Audit Trail {PAOPR2-25} / {FPRNR1-27}.