4152020 Wiring Formulas for Time Enty and Approval Rules (Oradle HRMS) Writ ing Formulas for Time Entry and Approval Rules ‘You can create formulas to validate submitted timecards using the Human Resources responsibilty. You can also write formulas to define which time and labor entries or changes require approval before an application retrieves the data. For example, you can specify that overtime entries higher than a certain level require approval, You create the time entry and approval rules formulas using the OTL Time Eniry Rules formula type. For each new formula you define, you create a new flexfeld context in the OTL. Formulas flexfield, For each new context you create, you also create a segment for each formula input you want to enter through the Time Entry Rules window. This setup enables you to select the formula in the Time Entry Rules window for one or mare rules, making appropriate entries for is inputs for each rule. Example For example, you create a new formula called: USR_OVERTIME_MAXIMUM, which raquites the following inputs for atime enity rule: + USR_OVERTIME_MAXIMUM + USR_OVERTIME_PERIOD + USR_OVERTIME_SHIFT_LEVEL You use this formula to define a number of time entry rules, where each rule specifies the overtime maximum for a specified shit level Approval Formulas Approval formulas use a separate formula type of OTL Approvals. Approval formulas have ane mandatory return value called ‘TO_APPROVE with the value ¥ (lo initiate the approval process) or N (indicating that approval is not required, which allows the timecard to Auto Approve). (OTL uses the approval formulas in the approval process by associating them to atime entry rule. You can select this time entry rule in the Approval Rules ragion of the Approval Style window. If you do not specify any rules in the Approval Rules region, then the approval process uses the information in the Approval Styles ‘Components region to execute the components, Additional rules in the Approval region provide a mechanism to choose between an auto approve process or an approval process you define. Ian approval rule returns TO_APPROVE equal to N, then OTL auto approves the timecard,Ifit returns TO_APPROVE equal to Y, then ‘OTL uses the approval process in the Approval Style Components region. Ifyou add more than one approval rule in an approval style, then the OTL application executes all the rules, until a rule returns TO_APPROVE equal to Y. The application does not execute subsequent rules once it finds a retum wih TO_APPROVE equal to Y. If the application does not find a rule that tums this value, then it auto approves the timecard ‘You can also associate mappings to time entry rules. The OTL application evaluates the mappings you associate to decide whether or not to execute the rule. This evaluation compares the current value and the value for each component on the timecard you identify by the mapping. f any of the current values are different to the old values, then OTL considers the timecard changed. If the value changes from an empty value to a value or vice versa, then OTL also considers the timecard changes. Ifthe result of a mapping indicates that OTL should not apply the rule, for example, the components defined in the mapping have not ‘changed on the timecard, then the rule does not execute. Ifthe approval rules do not execute, then the OTL application initiates the approval process defined in the Approval Styles Components region. Predefined Formulas ‘Tho predefined OTL Time Entry Rules formulas are: + Seeded formula for Period Maximum (HXC_PERIOD_MAXIMUM). This formula checks the number of hours worked within a time category (or across all categories) does not exceed the specified limit per week (or other period) over a specified reference Period (such as 14 days). You can use this formula in time rules for validation. Note: European users: You can use or adap! this formula to implement European Working Time Directive (WTD) rules. ‘+ Approval - Assignment Status Test (Seeded) (HXC_APPROVAL_ASG_STATUS). This formula checks the assignment status of the worker at the end of the approval period against a value specified in the Time Entry Rules window. If the statuses do not ‘match, then the time entries must be approved. You can use this formula in time rules for approval to specify which assignment statuses do not need special approval itpssiwww. supplier etisalat ae/OA_HTMLnelptopics!Halp/HolpSerletUSIHXT/@ptinfor?p=true8iocale=en 44152020 Wiring Formulas for Time Enty and Approval Rules (Oradle HRMS) ‘+ Approval - approval maximum test (Seeded) (HXC_APPROVAL, MAXIMUM), This formula checks whether the number of hours ‘worked in a time category within an application approval period exceeds @ maximum entered in the Time Entry Rules window. If itdoes, then the time entry must be approved. ‘You can use this formula in time rules for approval This is similar to the Period Maximum except the period is fixed (application approval period) and there is no rolling average (‘eference period) ‘+ Override Approver WE Person Mechanism (Seeded Approval) (HXC_OVERRIDE_APPROVER_WF_PERSON). This formula checks the override approval style in the default Projects preferences. It sends timiecards to the overTide approver selected on the Timecard Entry page. ‘+ Assignment Standard Hours vs Time Category (Seeded Formula) (HXC_ASG_STD_HRS_Comparison). This formula validates hours entered on the timecard within selected tme categories against an assignments standard hours. The rule uses the standard hours recorded for the employee's primary assignment. + PTO Accrual Balance vs Absence (Seeded Formula) (HXC_PTO_ACCRUAL_Comparison), This formula compares the hours entered on the timecard which decrement the accrual balance as specified in the Accrual plan definition against the PTO Accrual balance. + Period Hours vs Time Category (Seeded Formula) (HXC_TIME_CATEGORY_Comparison). This formula validates hours entered fon a timecard against the hours defined for a period ‘You can copy and configure the predefined formulas, or write your own formulas, according to the following rules. Formula Inputs and Outputs Formulas executed from time entry rules (fr validation of approval) must be ofthe following form: INPUTS ARE resource id (runber) submission date (text) /* Formula Processing */ RETURN , Outputs formula result> is: + RULE_STATUS with the value S (success) or E (error) for formulas used for validation. ‘+ TO_APPROVE with the value ¥ (to initiate the approval process) or N (indicating that approval is not required) for approval formulas. ‘ means thatthe formulas can also retum up to five messages, which must be passed back in the optional return values, MESSAGE1, MESSAGE2, MESSAGES, MESSAGE¢, MESSAGES. You defne these messages in the Messages window, and they must belong to product HXC. ‘You specify whether the messages are errors, business messages, of Warnings (for validation formulas) in the Time Entry Rule Group window. OTL displays the validation messages when workers save or submit their timecards. OTL sends approval messages as notifications in accordance with your approval workflow setup. Inputs You can display up to 15 inputs on the Time Entry Rules window so that you can pass inputs from the time entry rule definition to your formula. ‘Your formula must also have the following static inputs, which are passed to all OTL formulas. esource_id | This is the person id of the person whose timecard is being checked against the rule [submission_date | The frst day ofthe timecard period Note: Even ifthe flexfield context for your formula in the OTL Formulas flexfeld has a segment called TIME_CATEGORY, you do not need to add a similar formula Input. You can use the following inputs if the descriptive flextield context for your formula has a segment called PERIOD which contains a valid HXC_RECURRING_PERIOD (that i, it uses the value set HXC_TCARD_PERIOD), and a segment called REFERENCE PERIOD, Which is a number F 1 itpsswww supplier etisaat ae/OA_HTMLnelptopics!Halp/HolpSerletUSIHXT/@ptinfor?p=truv8iocale=en 2841572020 Timecard Hours Wiring Formulas for Time Enty and Approval Rules (Oradle HRMS) The number of hours that appear on the timecard and are included in the period specified in the PERIOD. segment Duration in days [The duration in days specified or derived from the period specified {db_pre_period_start |[The start date ofthe pre timecard period not covered by the timecard idb_pre_period_end [The end of the pre timecard period not covered by the imecard {db_post_period_star [The start ofthe post timecard period not covered by the timecard (db_post_period_end |[The end of the post imecard period not covered by the timecard Use the last four input formula needs to deri its, above, when the period specified in the PERIOD segment is greater than the timecard period. In this case the ive, from the database, hours prior to or following the timecard period, which do not appear on the timecard itself. The predefined formula HXC_PERIOD_MAXIMUM uses a reference period segment, If your formula uses this segment, you can use the following inputs to specify the start and end of the reference period. idb_rof_period_start| The start of the reference period that is not covered by the timecard| idb_ref_period_end The end of the reference period that is not covered by the timecard Note: The db_ref_period_start and end inputs are integrated with the db_pre and db_post period start and end inputs. That is, where appropr REFERENCE, Flats these dates are adjusted when the reference hours are found on the time card. Do not speciy a PERIOD in your descriptive flex context without specifying the PERIOD. itpssiwww. supplier etisalat ae/OA_HTMLnelptopics!Halp/HolpSerletUSIHXT/@ptinfor?p=true8iocale=en 313