(This page is under construction, click here to see legacy documentation.)
CreateOverview:
An Administrator is allowed to:
From here an Administrator will be able to create and maintain Leave Types to be used
on Leave Requests. The default types that come with the system are: Annual, Sick, Bereavement, Study, Maternity.
Default values must be configured for each Leave Type for Job,
Activity and
Work Centre from the Defaults hyper link. If the Activity entered has 'Use Time Codes" set, then an appropriate Time Code must also be entered. These values are in turn used to create timesheets for the approved leave requests. (note: all 3 are required if
Timesheet Lines are to be created automatically)
With these populated Timesheet Lines will be automatically created on Approval
. JobTransactions record will have 'Leave' in details column.
If these defaults are not set Approved Leave will have to be entered against the corresponding Timesheet manually
.
Screen Guide:
Leave Type Code, is a unique code (no spaces) to identify the type.
Leave Type Description, is a text field to describe in more detail the leave type.
Non-Approved Event Type and Approved Event type are used on the Leave Scheduler calendar, to show the types of leave requests. They are color coded for an easy visual identification.
See Resource Allocation Types for values in Columns 'Not Approved Event Type' and 'Approved Event Type'Defaults (0), see details at the bottom of this page.
If set, the
Review Required
adds a review step in the approval process.
A request must be reviewed before it may be approved. Users with a Leave Reviewer authorities must exist for reviewer options to be selectable on the Leave Request.
If set, the
Auto Approve
is applied only on the Bulk Leave Creation Screen.
This enables the Bulk Approve button on Bulk creation screen.
The Administrator may create the Request and Approve the Request in
one-step process, by using the Bulk Approve
button. For
bulk creating only, use
the Bulk Request
button.
People Default - Do not use. This can only be used in conjunction with the HR module which has been deprecated. A default Job Code for an employee can only be configured in the hR module. The best option for defaults in to use the Defaults.
If set, the
People Default
applies the
Employee’s Default Job Code and Activity Code (on the Employee Details tab of the User maintenance) as the defaults on the Leave Request.
As there are no Time Code defaults on a Person's record, the Time Code needs to be included in the Leave Type record.
The Work Centre defaults from the Job's Activity Group Line.
Leave Type record.
Timesheets Lines are generated on Approval if the Job/Activity/Work Centre are populated on the
Leave Request.
If set,
Statutory
ignores the existence of any Statutory Days entered in the 'Statutory Holidays' table in calculating the
Returning Date and Leave Days
See 'Leave Scheduler Setup" for values in Columns 'Not Approved Event Type' and 'Approved Event Type' Leave Scheduler Setup
.
Inactive: If a Leave Type
becomes redundant it should be set as 'Inactive'. Inactive Leave Types are not available for selection on new Leave Requests, but do support existing Leave Requests
Leave defaults by Profit Centre
Default Job/Activity/WorkCentre values can also be specified by ProfitCentre if needed.
Defaults(0)
column,
opens a 'Leave Type Defaults' screen where Job/
Activity/WorkCentre/TimeCode values can be set. Minimum values required
is Job.
If the user for which the leave is being requested for, belongs to a Profit Centre defined in the 'Leave Type Defaults',
then those values will be used.
Note that if any of the defaults are missing, the user can always select Job/Activity/Workcentre/TimeCode in the request leave screen. The defaults are just defaults. At the time
of approval, if all the values have been selected,
the timesheet entry will be created, whether
the values ere defaults or
manually edited/changed.
Info |
---|
For leave request events to show on Leave and People schedulers, the leave type must have a default jobcode. Also user must be a member of a Work group. |
Next Steps:
Related Pages:
FAQs:
Filter by label (Content by label) | ||||||
---|---|---|---|---|---|---|
|
Process Flow: