Contents

Fundamentals ..............................................................................................................................................................3
1. Architecture of PeopleSoft ...........................................................................................................................3

2. What is a control table and what information is stored in it.....................................................................3

3. Transaction table and what information is stored .....................................................................................4

4. Prompt table and what information is stored in it .....................................................................................4

5. Purpose of SetIDs and Tablesets ...............................................................................................................4

6. What is a Business Unit ...............................................................................................................................5

7. Concept of Effective dates ...........................................................................................................................5

8. Different Organizational Relationship PS Supports .................................................................................5

9. Purpose of ERN ............................................................................................................................................6

10. Difference between person(jobcode) and position structure(position Management) .......................6

11. Navigation to set the Installation defaults ................................................................................................6

12. Navigation to setup the system to drive by person or position or both ..............................................6

13. Define FTE ...................................................................................................................................................6

14. Navigation for Holiday Schedule ..............................................................................................................6

15. Common actions used to update employee data ...................................................................................6

16. Navigation and table for Actions and .......................................................................................................6

17. Navigation and table Action Reason ........................................................................................................6

18.Steps to add a person in to the PeopleSoft system ................................................................................7

19. Ways to assign Person IDs .......................................................................................................................7

20. Different instances in the system ..............................................................................................................7

21. Where do you enter details of a person's job, including the regulatory region, company,
department, and location ..................................................................................................................................7

22. What is the information that is entered in Job Information page .........................................................7

23. What are different values for the field Payroll system ...........................................................................7

24. How do we change the value for the Reports To field when we have assigned a Position to an
employee ............................................................................................................................................................7

25. What is the field to store Active & Inactive status of employees Job record? ...................................7
26. Explain the importance of Sequence number in Job data page ..........................................................7

27. What is the purpose of Job Indicator field ...............................................................................................8

28. How is the Termination date recorded .....................................................................................................8

29. Importance of Position Management Record field .................................................................................8

30. Importance of Payroll Status field in Job data page ..............................................................................8

40. What happens when we re-hire a person ...............................................................................................8

41. How do we add concurrent jobs to an employee ...................................................................................8

42. How to update effective-dated information on the Personal Data pages ...........................................8

43. How to update Emergency Contact information .....................................................................................8

44. How to update effective-dated job data ................................................................................................. 10

45. How to enter Multiple Actions on the same date .................................................................................. 10

46. Default items from control tables ............................................................................................................ 10

 Fundamentals

1. Architecture of PeopleSoft

PIA – PeopleSoft’s Pure Internet Architecture.

Tables
1 The Translate table
2 Processing and defaulting tables
3 Control Tables
4 Transaction Tables

Translate table
Code allocated is 4 characters long
Tracked by long and short desc
They do not need to be updated often
They are effective dated
No other field should be releated to this field
Values can be updated by power users ( pt>utilities>administartio>translate
values)(PSXLATMAINT)

Processing and defaulting tables

Installation table (Set up Hrms >Install>Installation tables )
Organization default by permisssion list( Set up Hrms>Ft>Organization>Org default by permission
lidt)
Business Unit Options default( Set up Hrms>FT>Organization>Business unit option Defaults)
Table set control (PT> Utilities>Administration>Table set control)

2. What is a control table and what information is stored in it

Control tables store information that is used to process and validate the day-to-day business
activities (transactions) users perform with PeopleSoft HRMS applications.
The information stored in control tables is common and shared across an organization, for
example, master lists of customers, vendors, applications, items, or charts of accounts. By storing
this shared information in a central location, control tables help to reduce data redundancy,
maintain data integrity, and ensure that users have access to the same basic information.
The information stored in control tables is generally static and is updated only when fundamental
changes occur to business policies, organizational structures, or processing rules.

a. Company ( Set up hrms> FT>Organization>Company

b. Table Set IDs(PT>Utilities>Administration>Table set IDs)

c. Business Units(Set up Hrms>FT>Organization >Business Unit)

d. Establishment (Set up Hrms>FT>Organization >Establishment)

e. Location ( Setup Hrms>FT>Organization>Location)

 f. Department ( Setup Hrms>FT>Organization>Department)

g. Comp Rate Code Table(Set Up HRMS, Foundation Tables,Compensation Rules, Comp

Rate CodeTable)
h. Salary plan (Set Up HRMS, Product Related,Compensation, Base Compensation,
SalaryPlan)
i. job Code (Set Up HRMS, Foundation Tables, JobAttributes, Job Code Table)

3. Transaction table and what information is stored

Transaction tables store information about the day-to-day business activities (transactions) users
perform with PeopleSoft HRMS applications.
The information stored in transaction tables often changes and is updated more frequently than
the information stored in control tables.

a. Person
b. Names
c. Address
d. Eff date Personal Data
e. Personal National Id
f. Job
g. Person Org assignments
h. Benefits Program Participation

4. Prompt table and what information is stored in it

Prompt tables are tables that are associated with fields on PeopleSoft application pages and
which display valid data values for those fields when a user selects a prompt or search option.
The data values stored in prompt tables are retrieved from control tables, transaction tables, or
other PeopleSoft tables.

5. Purpose of Set IDs and Table sets

Table sets and set IDs are devices that enable you to share – or restrict – information across
business units.
For example, with table sets and set IDs you can centralize redundant information such a country
codes while keeping information such as departments and job codes decentralized. The overall
goal of table sets and set IDs is to minimize data redundancy, maintain data consistency, and
reduce system maintenance tasks.
You must define at least one table set/set ID. The SETID key field is included on all control
tables.
6. What is a Business Unit

Business units are logical units that you create to track and report specific business information.
Business units have no predetermined restrictions or requirements; they are a flexible structuring
device that enables you to implement PeopleSoft HRMS based on how your business is
organized.
You must define at least one business unit. The BUSINESS_UNIT field is included on all
transaction tables.

7. Concept of Effective dates

 Maintain a chronological history of your data. By storing effective-dated information in

tables, the system enables you to review past transactions and plan for future events. For
example, you can roll back your system to a particular time to perform historical analyses
for your company. Or, you can set up tables and data ahead of time without using tickler
or pending files.
 Maintain the accuracy of your data. By comparing the effective dates in prompt tables to
the effective dates on application pages, the system displays only those values that are
valid for the current time period. For example, you create a new department code with an
effective date of May 1, 1998. Then, on the Job Data pages, you enter a new data row for
an employee with an effective date before May 1, 1998. When you select the prompt for
the department field, you won’t see the new department code because it is not in effect.

8. Different Organizational Relationship PS Supports

 Employee.
A person who is hired to provide services to the organization and has a legal employee
relationship with the organization.
 Contingent worker.
A person who provides services to the organization and who does not have a legal employee
relationship with the organization.
 Person of interest (POI).
A person who is not an employee or contingent worker but is of interest to the organization.
POIs can be:
a. COBRA participants.
b. Pension payees.
c. Stock - board members.
d. Stock - non-HR administered employees.
e. Global Payroll payees.
f. Campus Solutions persons.
g. External trainees
h. External instructors
9. Purpose of ERN

Employment record numbers (ERNs), in combination with a person's ID, uniquely identify a
person’s job data records. The system distinguishes between a person’s organizational instances
by using a new ERN when you create a new instance.

10. Difference between person(jobcode) and position structure(position Management)

When you drive PeopleSoft Human Resources by person, you use job codes to classify job data
into groups. You use those codes to link person data to job data. When you drive PeopleSoft
Human Resources by position, you still use job codes to create general groups, or job
classifications, in your organization, such as EEO (equal employment opportunity) and salary
survey data, but you also uniquely identify each position in a job code and link people to those
positions.

11. Navigation to set the Installation defaults

Set Up HRMS > Install > Installation Table > Products

12. Navigation to setup the system to drive by person or position or both

Set Up HRMS > Install > Installation Table > HRMS Options
1. Full -Position Management
2. Partial- system runs on both PM and JC
3. None – is nothing but jobcode

13. Define FTE

Full-time equivalency (FTE) is the percentage of full time that a worker should normally work in a
job. In calculating the FTE, the system uses your definition of the standard hours and the
standard work period.

14. Navigation for Holiday Schedule

Set Up HRMS, Foundation Tables, Organization, Holiday Schedule

15. Common actions used to update employee data

o Hire
o promotions
o transfers,
o terminations
o salary increases
o Leaves of absence.

16. Navigation and table for Actions and

Set Up HRMS, Product Related, Workforce Administration, Actions
ACTION_TBL_GBL

17. Navigation and table Action Reason

Set Up HRMS, Product Related, Workforce Administration, Action Reasons
ACTION_REASON_TBL
18.Steps to add a person in to the PeopleSoft system
To create a person record, use the Add a Person component
 Enter name and biographical data.
 Enter contract information.
 Enter country-specific person data.
 Create organizational relationships and maintain checklists.

19. Ways to assign Person IDs

When you open the Add a Person component, the system requests a person ID. There are two
ways to assign IDs:
 Automatically
If you use automatic ID assignment, the system adds IDs sequentially as you add new
people. The system maintains the last assigned ID on the Installation Table - Last ID
Assigned page.
 Manually
You enter the IDs, using any system that you choose for the organization. With manual entry,
you don’t need to assign IDs sequentially.

20. Different instances in the system

o Employment Instance
o Contingent Worker Instance
o POI Instance

21. Where do you enter details of a person's job, including the regulatory region, company,
department, and location
Navigate to Workforce Administration, Job Information, Add Employment Instance, Work Location

22. What is the information that is entered in Job Information page

Information about a person's job, including status, employee class, shift, or standard hours.

23. What are different values for the field Payroll system
Global Payroll, Other, Payroll Interface and Payroll for North America

24. How do we change the value for the Reports To field when we have assigned a Position to an
employee
Use the Override Position Data button on the Work location page.

25. What is the field to store Active & Inactive status of employees Job record?
Field HR_STATUS of Job record is used to store the active and Inactive status.

26. Explain the importance of Sequence number in Job data page

We use this number to track multiple administrative actions that occur on the same day. The
default value is 0, the correct number for new instances.
27. What is the purpose of Job Indicator field
This field indicates whether this is the person’s primary or secondary job for this organizational
relationship. Select N/A (not applicable) if those selections don’t apply to this job. This field is
used to process people with more than one organizational instance in a single organizational
relationship.

28. How is the Termination date recorded

The system displays the day before the termination effective date as the termination date and the
date last worked.

Termination date = Effective date - 1 where Action = “Termination” or “Resignation” or related

Action.

29. Importance of Position Management Record field

The system selects this check box when you make changes to fields in the Add/Update Position
Info component that initiate a system update of fields here. A selected check box indicates that
the system inserts a data row on the Job Data pages.

30. Importance of Payroll Status field in Job data page

This field is used for employment instances. It displays the payroll status of the current job record.
Changes that we make to this field trigger Retro Pay or Final Check processing.
A Retro Pay Request is triggered by any payroll status change with an effective date that’s earlier
than or equal to the latest pay end date of a check already paid to the employee.
A Final Check Request is triggered by any payroll status change that’s based on one of the action
or reason codes that are defined in the Final Check Action/Reason table.

40. What happens when we re-hire a person

If we rehire a person, the system clears the termination date and the date last worked fields.
When a person returns from leave, the system clears only the Last Date Worked field. If the date
is not accurate, select Override Last Date Worked to enter the date.

41. How do we add concurrent jobs to an employee

Navigate to Workforce Administration > Job Information > Add Additional Assignment
Add the new assignment with Empl Rcd = Empl Rcd +1

42. How to update effective-dated information on the Personal Data pages

 Insert a new data row in the effective-dated group boxes.
 Each of these group boxes can use different effective dates. They are not related.
 Enter the date when the new personal data that you’re entering will take effect.
 This date can be current or in the future.
 Enter the new information.
 Save the pages.

43. How to update Emergency Contact information

 Access the Contact Address/Phone page.
 Select the Same Address as Employee and Same Phone as Employee check boxes
before you update the worker's address.
 Select the type of address and type of phone number that is the same as the emergency
contact.
 When you update the worker's address, the system automatically updates the emergency
contact address. It also updates the Dependent/Beneficiary pages in the Benefits menu
and the Payroll Data pages in the Employee Payroll Data menu.
 Use the Other Phone Numbers page to record emergency contact phone numbers for the
emergency contact in addition to the primary number that is recorded on the Contact
Address/Phone page.
44. How to update effective-dated job data
 Locate the person whose record you want to change.
 Always start on the Work Location page because that’s where the Effective Date field is
located.
 Insert a new data row.
 In the Effective Date field, enter the date when the new action will take effect.
 Select an action code for the change, such as Transfer or Promotion.
 If applicable, enter a reason code to explain why this action is occurring.
 Change any other data needed to complete the new action, either on this page or on
other pages in the component.
 Save the pages.

45. How to enter Multiple Actions on the same date

 Access the Work Location page for the person whose data you’re updating.
 Insert a new data row for the first action.
 The effective date is set by default to the system date, usually today’s date, which you
can override if necessary. Leave the effective sequence number set at 0.
 Enter any other information that you need to complete the action, either here or in other
pages in the same component.
 To enter the second action, return to the Work Location page and insert another data
row.
 Enter the same effective date as the first action, but enter an effective date sequence
number of 1.
 Select the appropriate personnel action and enter any other information required to
implement the action, either here or on other pages.

46. Default items from control tables

Company = Pay group
Location= salary plan and holiday schedule
Department = Company , location, Manager/supervisor id, tax location for NAP
Comp rate code= can be defaulted from salary step, workers job data, job code
Benefit program entered in pay group page in cal parameters will be defaulted to job data page from pay group

Job code table defualts Pay group

1. Standard rs Benefit Program
2.Work Period Employee type
3.Salary plan,Grade,step Holiday Schedule
4. Flsa Status Earning program
5.Comp Frequency
6.Rate Code