Process Overview and Fundamentals | Part 1 | PeopleSoft Time and Labor
You are reading a preview.
Activate your 30 day free trial to continue reading.
First in a series of presentations on Peoplesoft. For more information visit my blog at www.peoplesofthrms.blogspot.com
First in a series of presentations on Peoplesoft. For more information visit my blog at www.peoplesofthrms.blogspot.com
Similar to Time And Labor Overview
Free with a 30 day trial from Scribd
Free with a 30 day trial from Scribd
- Set Up Fundamental Tables – HRMS, Installation, T&L Related Tables (Shift, Schedules, TRC, Workgroup etc.)
- Enroll Employees into T&L
- Provide Security
- Report Time
- Process Time (Run TIMEADMIN)
- Approve Time
- Load Payable Time from T&L to Payroll.
- Hourly employees (Positive Time Reporters) report PUNCH time everyday.
- Salaried employees (Exception Time Reporters) report ELAPSED time like Leave, Holiday etc.
- Time reported by the employees get entered in the PUNCH and ELAPSED reported time tables – TL_RPTD_PCHTIME and TL_RPTD_ELPTIME respectively.
- The TIMEADMIN process reads from the above reported time tables, applies RULES to the entries and converts REPORTED TIME to PAYABLE TIME.
- Select the Reporting Method from the drop down box .
- Select the appropriate check box for reporting time for a particular employee or a group .
- Click on “Get Employees”.
- Click on the desired Employee name hyperlink to report time .
- Querying TL_RPTD_PCHTIME table to view entry of PUNCHED time reported in the previous slide
- Querying TL_RPTD_ELPTIME table to view entry of ELAPSED time reported before
- The TIMEADMIN process is the heart of Time and Labor.
- A complex process that converts REPORTED TIME to PAYABLE TIME.
- Process consists of an AE – TL_TIMEADMIN which in turn calls a number of other AEs.
- The major steps in the process consists of –
- a. Deciding which employees to process.
- b. Creating batches of employees.
- c. Read Reported Punch and Elapsed Time.
- d. Apply Rules.
- e. Update Intermediary Payable Time Tables.
- f. Update Payable Time table.
- Time and Labor Process Time Request Time Administration
- Enter the Date till which Time is to be processed (Process Date)
- Enter either an EMPLID or GROUP ID to be processed.
- TIMEADMIN queries the TL_TR_STATUS table to decide which all employees to process
- On ENROLLING an employee in Time and Labor: – a. TA_STATUS is set to ‘Y’ and b. EARLIEST_CHGDT is set to T&L Enrollment Date.
- After processing – EARLIEST_CHGDT is set to the first day of the next pay period for elapsed employees and to the last processed day for positive time reporters.
- After processing – TA_STATUS flag is set to ‘N’ for Positive time reporters and to ‘Y’ for Elapsed Time Reporters.
- After processing time, if any time is further reported, TA_STATUS is set to ‘Y’ for Positive Time Reporters.
- If time is reported on a date lesser than the ECD, the ECD is reset to that date.
- TIMEADMIN selects ONLY those employees having a TA_STATUS = ‘Y’ and ECD <= Process date on Time Administration page.
- Producing PAYABLE TIME is the end result of Time and Labor processing.
- After processing time, TIMEADMIN inserts data into the Payable Time table – TL_PAYABLE_TIME, which is ready to be taken by payroll.
- Data in TL_PAYABLE_TIME represents final processed time which has been generated after applying all the defined rules to Reported Time.
- PAYABLE_STATUS is an important field that decides whether the time is ready to be taken by payroll and whether payroll has processed that time.
- PAYABLE_TIME table populated for earlier employee after running TIMEADMIN.
- Note that though no TRC was reported for PUNCH TIME – the rules in TIMEADMIN resolved the PUNCH TIME and assigned appropriate TRCs to the reported time as per the defined rules.
- Note that the PAYABLE_STATUS of the rows right after TIMEADMIN is ‘NA’ – Needs Approval.
- When new entries are created in TL_PAYABLE_TIME after TIMEADMIN – PAYABLE_STATUS set to NA .
- After manager approves TIME – if TRC is mapped to an ERNCD, PAYABLE_STATUS set to AP (Approved) , if not PAYABLE_STATUS set to CL (Closed).
- Stage in which TIME is loaded to Payroll – the status will be set as SP (Sent to Payroll)
- If Payroll accepts time – status becomes – TP (Taken by Payroll)
- If Payroll did not accept time – status becomes – RP (Rejected by Payroll)
- Reported time has to be approved by managers if they are to be taken by payroll.
- This functionality can be defaulted at the WORKGROUP Level.
- All TRCs having a status of NA will be populated in the Approve Time page of the manager.
- Once the manager approves time, the PAYABLE_STATUS of those TRCs will be updated to either AP or CL .
- Approving Time which was reported earlier.
- Note that the PAYABLE_STATUS of all the rows have changed from ‘ NA ’ to either ‘ AP ’ or ‘ CL ’ after approving time.
- Time and Labor Rules carry out the function of converting REPORTED TIME to respective TRCs depending upon business regulations and requirements.
- For example, hourly employees report time by PUNCHING and not in the form of TRCs. How does this time get converted to the respective TRCs? How does the system assign different TRCs to Regular and Over Time? All this is achieved by the use of T&L Rules.
- T&L Rules are simply SQL Objects that manipulate data in the reported time tables, converting them into the required TRC/TL_Quantity and inserting into the PAYABLE TIME table.
- T&L Rules are called by TIMEADMIN. All the defined rules can be found as separate sections in the AE – TL_TA_RULES.
- As said before RULES are composed of SQL Objects. Thus, the basic building block of every rule is a SQL Object.
- Many SQL Objects are combined together to form a RULE.
- How is a RULE attached to a Time Reporter? This is achieved with the concept of a RULE PROGRAM .
- RULE PROGRAMS again, are composed of a collection of many RULES arranged in the required order of execution. (Like Daily OT, Daily Double Time, Weekly OT, Holiday Pay etc)
- A RULE PROGRAM is attached to a Workgroup and thus it applies to all employees under one workgroup.
- Peoplesoft delivers ready made TEMPLATES for almost all categories of RULES that may be required in an implementation.
- Thus, the custom rules can be built from the delivered – TEMPLATE BUILT RULES .
- Creating a new rule from a TEMPLATE BUILT RULE will create for itself, all the SQL Objects that are required.
- Any customisations required to the rule, can be achieved by modifying the concerned SQL Object in the rule.
- Requirement :- All hours greater than 12 hours reported in a day has to be paid at a TRC of @2.0
- Step1 :- Select the concerned TEMPLATE TYPE (Set Up HRMS Product Related T&L Rules and Workgroups Template Built Rules)
- Step 2 :- Customise the TEMPLATE RULE (Page 1)
- Step 3:- Customising the TEMPLATE (Page 2)
- Step 4: – Compiling the RULE and viewing the SQL Objects (Set Up HRMS System Administration Utilities Build Time and Labor Rules Rules)
- Step 4: – Compiling the RULE and viewing the SQL Objects (Set Up HRMS System Administration Utilities Build Time and Labor Rules Rules)
- Adding a new SQL Object to a Rule :-
- View/Modify a SQL Object :- (Setup HRMS System Administration Build Time and Labor Rules SQL Objects)
- View/Modify a SQL Object :- (Setup HRMS System Administration Build Time and Labor Rules SQL Objects)
- This step is similar to adding a SQL Object in a rule. Select the required RULE PROGRAM, add a new row in the required place in the scroll and select the concerned RULE. (Set UP HRMS Product Related –> Time and Labor Rules and Workgroups Rule Programs)
- Set UP HRMS Product Related –> Time and Labor Rules and Workgroups Rule Programs
- Adding a RULE PROGRAM to a WORKGROUP: –
- Set UP HRMS Product Related –> Time and Labor Rules and Workgroups Workgroups
- IPT stands for Intermediary Payable Time. By now you would have understood that TIMEADMIN involves a lot of juggling and manipulation of data. This is done in the IPT tables. These are Temporary tables attached to the TIMEADMIN process. The tables range from TL_IPT1 to TL_IPT5 and each of these tables have 15 instances each. TL_IPT1 is the most important of all these tables. Reported time data is initially loaded into IPT1 and from here, it is further inserted into the other IPT tables, manipulated and the final product is inserted back into the TL_IPT1 table at the end of each process. After all the rules are executed, TL_IPT1 data is inserted into the payable time table (TL_PAYABLE_TIME).
- Always COMPILE a rule after any modifications to it.
- Never modify a delivered RULE or SQL Object. Clone the required rules with the help of Copy Rules/Copy SQL Object utility.
- Ensure that the RULE/SQL Object is added at the right place in the Rule Program/Rule as the order of execution is important.
What are the terminal rules of an element?
Ans: Below are the three main rules of an element.
Actual Termination – It is used for a nonrecurring element. The entries will get closed when the pay date ends.Final Close – This will be used when the entries need to be opened beyond the leave period of an employee.Standard Process – It refers to the day that the employee is relieved of his employment.
It is basically an area where the users can define the assignment data in a clear manner. It is possible to utilize this data for the purpose of grouping the sets that matter a lot to the user. Whenever it comes to defining the eligibility of the elements, it is possible for the users to simply use them.
It is an approach that is referred to as a specific class of an application dealing with business modules. In order words, it is a blend of various software applications and can thus perform all the important tasks alone which are generally dependent on a number of software. It is an integrated approach and the users are free to save a lot of time through this approach.
It is basically used in the handling and managing of core tables that can be the same or different from one another. It simply puts separate the different transactions made by an employee on different dates. Several Setup tables can also be managed with this data easily. The effective data simply make sure no error remains present and the record always remains up to date.
It is basically a system that is considered when it comes to the management of the skills, potential, efficiency, as well as extra curricular activities of an employee working in an organization. It also enables organizations to represent the drawbacks associated with the employees and how they can be eliminated. Therefore, this approach is of significant importance and is best when it comes to keeping up the pace with the error-free efficiency in an organization.
It is basically an approach that is considered best because it makes sure that the large sections of data dealing with the transactions of the employees can be handled in a reliable manner. The fact is that almost all the transactions are actions driven and it is very common that employees made similar transactions multiple times during a specific period. When such a situation arrives at all the other transactions then the first needs prompt attention. This is done through the Job table which is prepared through effectively sequencing the information.
