Data entry validations in Oracle Labor Distribution are performed on the following attributes:
Oracle Projects charging instructions
Oracle Grants Accounting charging instructions
Oracle General Ledger code combinations
The purpose of data entry validation in Labor Distribution is as follows:
to ensure that labor scheduled cannot be distributed more than 100% on any given day
to prevent deletion of any schedule line whose begin and end dates overlap with the date of any distribution lines that are generated in the past
The validations that are performed for General Ledger code combinations are the same as those performed for other Oracle financial applications.
The validations that are performed for Projects and Grants Accounting charging instructions during the labor scheduling process are the same as those performed during the Create Distribution Lines process.
Data Entry Validations consists of the following:
In the Labor Scheduling window, the following validation rules are applied:
The expenditure item date used when validating the Grants Accounting charging instruction is the begin date from the schedule line.
The message box displayed to the user indicates which particular entry failed validation.
All entry failures are considered errors or warnings.
If entry failures are considered errors, Labor Distribution does not allow the schedule line to be saved until a correction is entered and passes validation.
If entry failures are considered warnings, corrective action is not required, and the schedule line can be saved without making corrections.
Labor scheduling rules for deletions are as follows:
Element types can be deleted if the following conditions apply:
No payrolls for the element type dates exist.
No schedule lines for the element type dates exist.
No element groups are associated with the element type.
If a global element exists for this element type, the element type must exist in the PSP element types table at least once or more to maintain referential integrity.
An element type can be deleted from an element group if there are no schedule lines for the dates of the associated element group.
An element group can be deleted if there are no element types associated with it.
A global element can be deleted if there are no payrolls for the dates of the global element.
A default schedule can be deleted if there are no payrolls imported for the dates of the default schedule.
A default account can be deleted if there are no payrolls imported for the default account dates.
A suspense account can be deleted if there are no payrolls imported for the dates of the suspense account.
Rules for end-dating apply to the following:
element type
element group
global element
default schedules
default accounts
suspense accounts
End-dating rules for element types are as follows:
An element type can be end-dated to the last payroll import date.
An element type can be end-dated to the last schedule line date.
An element type in an element group must be end-dated to make the element type active for at least one day.
An element type's end date can be extended if it does not overlap with other instances of this element type.
End-dating rules for element groups are as follows:
An element group can be end-dated to the last payroll import date.
An element group can be end-dated to the date of the element group's last schedule line.
An element group can be end-dated so that each element type associated with it can be active for at least one day.
An element group's end date can be extended if it does not overlap with other instances of this element group.
End-dating rules for global elements are as follows:
A global element can be end-dated to the last payroll date.
A global element's end date can be extended if there are no payrolls for the extended period and if the global element does not overlap with other instances of this global element.
End-dating rules for default schedules are as follows:
A default schedule can be end-dated to the last payroll date.
A default schedule's end date can be increased if there are no payrolls for the extended period and if the default schedule does not overlap with other instances of the default schedule organization.
End-dating rules for default accounts are as follows:
A default account can be end-dated to the last payroll date.
A default account's end date can be increased if there are no payrolls for the extended period and if the default account does not overlap with other default accounts for this organization.
End-dating rules for suspense accounts are as follows:
A suspense account can be end-dated to the last payroll date.
A suspense account's end date can be increased if there are no payrolls for the extended period and if the suspense account does not overlap with other suspense or global accounts for this organization.
In the Labor Scheduling window, entry failures of many charging instructions or accounting flexfields are considered errors. Entry failure for charging instructions include the following:
Project does not exist.
Task does not exist for the project.
Award does not exist.
Expenditure Organization does not exist.
Expenditure Type does not exist.
General Ledger code combination does not exist.
In the Labor Scheduling window, the following entry failures are considered warnings:
Project is not active for schedule line begin date.
Task is not active for schedule line begin date.
Award is not linked to the Project via an installment.
A new schedule line is entered which has a begin-date that includes a payroll that has already been distributed.
During the Create Distribution Lines process, all entry failures are considered errors. All charging account entry failures are posted to the organizational suspense account.
Other data entry validations include the following:
End date can be changed if it is greater than the last payroll process date and can be changed to a date greater than the payroll process date.
Begin date can be changed if it is greater than the last payroll process date and can be changed to a date greater than the payroll process date.
New schedule lines can be created with a begin date that is greater than the last payroll process date.
Percentages cannot be changed on any schedule line if the schedule line has already been used in any payroll distribution.
Note: Users can change the end date and create a new record.
The end date of the most recent Oracle Payroll, Quick Pay or non-Oracle payroll imported into Oracle Labor Distribution is checked by Labor Distribution. Schedules can only be adjusted for dates after the end date of the last processed payroll for the selected employee assignment, assuming that the employee assignment was included in the payroll import.
If Oracle Payroll, Quick Pay, or a non-Oracle payroll is imported into Labor Distribution for a payroll period for employee assignments, the schedules of these employee assignments are locked from update for any date within that payroll period. Users can update the schedules of employee assignments not included in that payroll import.
Users can define and program additional validation rules for the labor scheduling process that meet the needs of their unique business requirements.