Selling Of Leave {P00004-4}

The leave system provides for the application to sell back leave back to the institution.

This menu option can be used to sell leave by the employee or may be used to apply to sell leave on behalf of another employee, refer to {PWEBM-6} for setup.

1. A list of employees will be available if {PWEBM-6} has been setup to allow the user logged on to select the Personnel number for whom the application to sell leave is to be submitted for. 
2. A list of Leave Types {PLCS-2} which are linked to the relevant Leave Package, will be displayed.
3. On Selection of a Leave Type, details for the Employee, relating to the Leave Type, will be displayed.
   Below the list, a command button with which to create a new Application to Sell Leave will be made available.
4. If the user clicks on the command button, a page will appear that will allow the user to enter the relevant information for the Selling of Leave Application.
   The program will perform the same validations and use the same formulas as is used by Selling of Leave {PLOP-4} in the Back-office system.
5. Upon submission, the Monetary Value of Leave Sold {pweb01pkg.html} will be calculated and saved with the application. The page also has a "Calculate Value of Leave Sold" - hyperlink to displaythe monetary value, as well as an estimated "after tax" value, based on the value calculated and the salary transactions for the person in the month selected.
6. The Leave Administrator may use the Leave Records {PLOP-1} / {PLOP-10} to update the Monetary Value before Leave Selling Earnings {FPRI-12} is created.

Refer to the documentation on the Routing System {GMAIN-4} for information about routing.

1. When the Leave Application is saved, the System will automatically create a Routing Request for Routing Entry Type "WEBS".
2. The Routing System may then be configured to notify the persons involved and allow the responsible personnel members to approve or reject the leave application.
3. The Routing Sequence for final approval should have only two outcomes, i.e. Approved (APPR) or Rejected (REJ);  it should lead to a sequence that executes database procedure person.wl01pkg.approve_reject_leave. This procedure will update the Web Leave Applications Table with: the date of final approval, the approval status (Approved or Rejected), and a completed date with which to prepare the approved application to be copied into the ITS Leave System with Leave Records {PLOP-8}.
4. All sequences where the application may be rejected, should lead to the above sequence with the database procedure (person.wl01pkg.approve_reject_leave), if the outcome of the sequence indicates that the application is rejected.
5. The following information will be written to the Routing Email Instructions for Sequence 0 of the Routing Request, for the lines as indicated. (Data from the System between <>). This may be used by the Routing System as text in Email messages and / or to route the application to different personnel members for approval.. 

6. Line Number	Email Instruction
   1	"Application For Leave" "Application For Selling Of Leave" "The Cancellation Of an Application For Leave" "The Cancellation Of an Application For Selling Of Leave"
   2	"Applicant: " <Personnel Number, Name and Surname>
   3	<Applicant Primary Email Address>
   4	"Email Address: " <Applicant Primary Email>
   5	"Telephone Numbers : " <Applicant Primary Contact Numbers>
   6	<Routing Request Number>
   11	<Applicant's Personnel Number>
   12	<Applicant's Email Address>
   13	<Supervisor's Personnel Number>
   14	<Supervisor's Email Address>
   20	"Applicant From : " <Personnel Number, Name and Surname of the Applicant>This may be used by the Routing System to route the application to different personnel members for approval.
   21	"Department : " <Applicant's primary Department Code>
   22	<Applicant's Primary Department Code>
   23	"Number of days : " <Number of Days Applied For>
   24	"Start Date : " <Leave Start Date
   25	"End Date : " <Leave End Date>
   26	"Payment Month : " <Payment Month where it is an Application to Sell Leave>
   27	"Type Of Leave : " <Leave Type Name>
   28	"Current Status : " <Approval Status>
   29	"Please Note: A medical certificate needs to be submitted" (Where Applicable)
   30	"Application Date : " <Leave Application Date>
   31	<Notes as entered on the Leave Application - The first 80 Characters>
   32	<Notes as entered on the Leave Application - The next 80 Characters>
   33	<Notes as entered on the Leave Application - The next 80 Characters>
   34	<Notes as entered on the Leave Application - The next 80 Characters>
   50	<Personnel Number> of user submitting the application
   51	<Title, Initials, Surname> of user submitting the application
   52	<Primary email address> of user submitting the application

   
   
7. The System may also be configured to write additional information, from the Organisational Contacts {GCS-10} to the Routing Email Instructions, for Sequence 0 of the Routing Request. This may be used by the Routing System to route the application to different personnel members for approval.
   

   The Organisational Contacts {GCS-10} allows the user to indicate different Communication Levels (e.g. Departments or Faculties) and different Types (e.g. Department Heads, Department Head Secretaries), and to link a Personnel Number as a Contact Person for each Level and Type. In this way, a list of Department Heads, or a list of their Secretaries may be maintained.

   
   
   • The instruction to write the additional information should be entered in the Routing Email Instructions of the Default Request Information {GROU-1} for Routing Entry Type "WEBL", in a line of its own, after line 34, as follows:
     $OE,Dxxx,nn$  or
     $ON,Dxxx,nn$  or
     $OU,Dxxx,nn$  or
     
     $OE,Fxxx,nn$  or
     $ON,Fxxx,nn$  or
     $OU,Fxxx,nn$  or
     
     where
     • The first two characters are always $O;
     • The third character indicates whether a Personnel number (N), Email Address (E) or ITS User Code (U), as in User Access Definitions {USERS-5}, will be written to the line;
     • The fourth character is always a comma (,);
     • The fifth character indicates the Communication Level, as in Organisational Contacts {GCS-10}, that will be used.
       Note that only values (F)aculty and (D)epartment are allowed.
     • The next set of characters (xxx), before the second comma, is the Communication Level Type in Organisational Contacts {GCS-10} that will be used.
     • The set of characters after the second comma (nn), is the personnel number that will be used. If this is entered as zero (0), the System will use the personnel number of the person who applied for leave.
     • The last character should always be a $.
       
       The System will then insert the following information in the line for sequence 0 of the Routing Request:
       • The Personnel Number, Email Address or ITS User Code (depending on the third character): 
       • of the person indicated as the contact person for the 
       • Primary Department or Faculty (depending on the fifth character): 
       • of the person indicated with the characters after the second comma: 
       • for the Organisational Contact Type indicated by the set of characters before the second comma.
         

• Selling of Leave