Effective sequence concept is used in some key tables like Job. Job table has high volume of employee traction data. There are multiple types of tractions and they are all action driven. It is very likely in a business scenario that employee has same type of traction more than once in the same day. For example: Employee can have a data change action happening on the same day more than once. In such a situation, for the same employment instance, we now have more than one row with the same effective date. In order to uniquely store this second traction, we need another primary key which is where effective sequence comes into play. Hence Job table has a primary key structure: Employee id, employee record number, effective date and effective sequence.
Location is the core table which is used to define all the office locations of the organization. All locations are tied to a company and setid. Location is also tied to a department. Geographic location is a US federal concept. This is specific to a State –City code. Locality pay area and law enforcement officer special pay area calculations are noted in this setup. Based on the geographic location code setup the locality pay percentages are calculated and used in US payroll process.
Different organization relationships a person can have are: Employee, Contingent worker or Person of Interest as per the person model. Employee is a permanent staff member of the firm who is paid by company payroll and has a hire row in job with all associated information like company, department, location and paygroup etc. Example is a permanent position for a chief executive or sales manager in the firm.
Contingent worker is a contractor in the organization mostly on an assignment. Personal information and job information is stored for a contractor in the system but person is not on the company payroll. Example can be a person from a third party company which is acting as a vendor for the firm to conduct a project for the firm needs. This person is a part of the project and working in the firm till the end of the project.
Person of interest has many flavors. There are various types of POI:– Pension payee, external trainee, external instructor or board member. They are members who are connected to the firm due to some business purpose. There are two types of POIs- who have a row in job data and others who do not have. POIs who do not have job information have a separate mechanism in PS to maintain their data security.
A termination action can be followed by a data change action row or a rehire row. DTA action row would be added if some correction needs to happen to the data of the employee who is terminated and you don’t want to update the current row then you can add a new DTA row. Rehire action is the most logical one to follow a TER action row this will happen when an employee post termination again wishes to join the organization and the organization wants to consider this as a rehire with same employee id and other details.
A regulatory region is a region which has laws and regulations that are used by functionality in PeopleSoft HRMS. A lot of tractions are driven by regulatory requirements. These requirements include areas like ethnicity, disability, and health and safety. When driven by Regulatory Region, the regulatory codes, People Code edits, and set processing in the system can vary by country and for each traction.
Standard hour is defined in multiple ways in the system. Under Setup HRMS - Installation table in HRMS options, there is a standard hour rule setup. This is at the system level. Here the admin will define the minimum and maximum hours for the HR system and also the default hours. The second place where the setup can be done is in the jobcode table setup. Under Setup HRMS -> Foundation tables -> Job Attributes -> Job code table. When a user sets up a job code then the standard hours value can be set specific to that job code. When employee job details are being populated based on the jobcode, the standard hours and FTE will get refreshed. Also values like regular/ temporary will get populated.
When a user logs in PS the system sc through the user profile to see the associated primary permission list. There is a setup called org defaults by permission list. Setup HRMS -> Foundation tables -> Organization -> Org Defaults by Permission list.
For every permission list following field defaults are set here: Business unit, Setid, Company, Country, Regulatory region, Currency and name format.
it depends on the version:
8.3 HRMS :
8.9 HCM :
If there is a person who is a permanent employee with an organization, i.e. organizational relationship is employee and he has to take up a consulting role for a new product launch in another department of the same organization for say, 6 months, then he will be a contingent worker. In this case, he will have two organizational relationships – full time employee and contingent worker for the new product launch.
Let's say your PeopleTools is installed in D:PT848
-ZIFD:pt848SQRpssqr.ini -S -DEBUGX -PRINTER:PD -EH_PDF
-i => Input file Directory
-f => Output File Name
-o => Log file Name
-ZIF => SQR Initialization File Name
Using data buffer classes in people soft we have show required field que.using that we can conver it to mandatory.
Checklist is a handout type of a utility for the user that can be referenced to ensure that all the tasks the user has to accomplish are done and noted. Say, a recruiter or HR admin wants to a hire a new joinee in HRMS system, there is a recruitment checklist the user can use. When the user is done with all the data entry, he can refer to this checklist in the system. Checklist has a bunch of tasks like passport and documents verified, bank documents sent, offer pack issued, identity check etc. User can put the status against each task like initiated, completed etc. This is a way of tracking that all formalities related to hire are completed. Admin can create new checklists also from Setup HRMS -> Common Definitions -> Checklists -> Checklist. If needed new checklist items can also be created from Setup HRMS -> Common Definitions -> Checklists -> Checklist items.
To identify a particular job in PS HRMS we use job code.
Example: You can have a job code representing Administrative assistant. This jobcode will have a defaulted salary grade and standard hours. A collection of multiple such jobs grouped together which use this job code will make a job family.
The above wer is for to retrieve the 3rd scroll recoed level data only.
If u want the field level information use below syntax:
Table Data which is going to change on daily is traction table , Table data (Organisation Address , Phone No , Locations) whcih is going to change as part of the organisation approval is called setup tables.
Values like business unit, company, country get defaulted by virtue of the user’s primary permission list. These default values are associated with SetIDs on the Business Unit Options Default page.
Using the tableset controls and business unit default options, the system determines the default values to enter in select fields on the component. So, when a user accesses a component that uses business unit defaults and selects a business unit, the system determines the setID which drives the defaults for the business unit on the Tableset Control –Record group page.
Effective date concept is used in multiple core tables in PS HRMS. For example in job this is a primary key. Purpose of this field is to differentiate multiple traction rows for same employee that has happened on two different dates. Effective date is also used in a lot of setup tables for example location. A location is say active as of today but 5 days later if I wish to make it inactive how does the system recognize the current status of location 5 days in future. It will be done by using the most effective dated row for that location.
EMPLOYEES table is a current employee information table. This is primarily used in interfacing with third party systems or in business reporting as well in conjunction with EMPLOYMENT which is now a view. EMPLOYEES table is populated by running a delivered process called Employee refres, the job name is PERS09@This process will populate EMPLOYEES table by first truncating the whole table and then re inserting the data. This table will only store information for active employees in the system and it will have only one row corresponding to each employee’s most recent personal and job details.
If the organization is not fit to be position driven, then the other options available are:
By Person: In this approach, job codes are used to classify job data into groups. Job codes have one to many relationships with employees, i.e. multiple employees can have the same job code. Jobs to be performed are identified in the organization. Job codes can be shared across departments, locations or companies.
Partial Position: There might be a situation wherein the system has to be driven by both the approaches – by person and by position. In this case, partial position management can be implemented. Driving by position might work for certain departments or executive levels whereas others can be person driven.
Last hire date is the date a person is hired or rehired in the organization. Hire date is the date associated with a hire action job row. For example if a person is hired on 1st May 2010 first time in the company and then terminated on 1st May 20@Hire date and last hire date both will be 1st May 20@Let’s say now the person is rehired on 5th May 2011 then the hire date will still remain as 1st May 2010 but the last hire date will now be 5th May 2011.
The data which is not going to change frequently such type of data is stored in setup tables.
Exp: Company Address,Phone No,Company Locations,Company Name,Business Units,Departments,Positions