Previous | Next | Contents | Index | Navigation | Glossary | Library |
Typically, you would expect to record more than just the name of the element. For example, if you defined an element to record employee expenses, you might want to record the Type, as a code value, and the Claim Amount as a monetary value.
In Oracle HRMS you define these values as input values for the element. When you define an element, you can define up to 15 input values for it. You decide which values you want to record and what limits, or validation, to apply to those values.
Input values can be numbers, text, dates, times, hours, or monetary values. You also decide whether each input is required or optional when an entry of the element is made for an employee.
For example, if your enterprise makes overtime payments, you might write a formula to calculate the payment amounts for each assignment from inputs of the overtime rate and the hours worked for the period. The payroll run then processes each assignment and produces the overtime payment amounts as run results.
Run results are used for other purposes besides summing the amount of employee pay. In the overtime example, the run result information can also be used for costing purposes and to track the actual hours of overtime worked.
You can enter a pay value directly as an input to the element. When you do so, no formula will fire during the payroll run to calculate any direct result for the element. Instead, the pay value you enter becomes the run result.
With Oracle's formula writing tool, Oracle FastFormula, you can include conditional logic to validate input values using different criteria for different employees.
Using Oracle FastFormula for Payroll Calculations
Using Oracle FastFormula for Validation
Previous | Next | Contents | Index | Navigation | Glossary | Library |