D41114 PDF 76 100

Setting Up Core Foundation Tables Related to Business Units and TableSet Sharing Lesson 4
Defining SetIDs, Business Units, and TableSet Sharing (continued)
Record Groups
A record group is a collection of similar records (tables and views).
A record group can contain a single table or many tables and views:
HR_01 Departments
record group
Department View of all Department-Level

(DEPT_TBL) Departments Security
(DEPT_ALL_VW) (DEPT_SCRTY_VW)
Slide 55 _______________________________________________________________________________________________________
Student Notes
Delivered Human Resources Record Groups

n l y
O
PeopleSoft delivers the following human resources-related record groups:
e
•
•
HR_01 Departments.
HR_02 Job Codes.

•
•
U s
HR_11 Legislative Requirements.
HR_12 FP Actions Group.
• HR_03 Locations.
A
• I HR_13 Grades Group.
• HR_04 Job Tasks and Requirements. O • HR_14 Labor Agreement.
• HR_05 Plan Salaries.

l & • HR_15 Employee Classification.
•
n a
HR_06 Business Unit Defaults. • HR_16 Supervisor Level Table.
•
te r
HR_07 Absence Types. • HR_17 Works Council.
•
I n
HR_08 Health & Safety. • HR_18 Professional Compliance.
cl
•e HR_09 Contract Types. • HR_19 Competency Management.
O ra • HR_10 Credit Card Vendor

Information.
66 PeopleSoft Proprietary and Confidential

Lesson 4 Setting Up Core Foundation Tables Related to Business Units and TableSet Sharing
Other Delivered HRMS Record Groups

PeopleSoft also delivers payroll-related record groups:
• PY_01 Balance ID Tbl-Setid Company.
• PY_02 Shift Table-Setid Paygroup.
• PY_03 HR Chartfields.
Page Used to Maintain Record Groups

Page Name Navigation
Record Group PeopleTools, Utilities, Administration, Record Group
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
n l y
e O
______________________________________________________________________
U s
______________________________________________________________________
A I
______________________________________________________________________
O
&
______________________________________________________________________
l
a
______________________________________________________________________
n
te r
______________________________________________________________________
I n
______________________________________________________________________
c l e ______________________________________________________________________
r a
O ______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
PeopleSoft Proprietary and Confidential 67

Record Groups (continued)

Mapping a setID to a record group for a business unit links this same setID to all views
and tables that are contained within a record group.
And, by using record groups, you are not limited to one setID per business unit; you can
adjust your business unit and setID mapping needs for greater effectiveness:
Record Group SetID
HR_01 Departments SBA
Business Unit HR_02 Job Codes SHARE
HR_03 Locations SBA
n l
This mapping of business units to setIDs is done in the TableSet Control component.
y
e O
Slide 56 _______________________________________________________________________________________________________
Student Notes U s
A I
The Importance of Record Groups
O
Record groups ensure that tableset sharing is applied consistently across all related tables
and views in your system.
l &
n a
r
______________________________________________________________________
te
I n
______________________________________________________________________
cl e
______________________________________________________________________
r a ______________________________________________________________________
O ______________________________________________________________________
______________________________________________________________________

Example: Analyzing Your Business Unit Needs

This example shows data needs for Business Unit A:
Computer
Testing SetID Department
Research SBA Office of the President
SBA Business Unit A Sales
SBA Business Unit A Customer Serv
Business Unit A
BUA
Default SetID Job Code

SetID: SBA SBA Sales Support
SBA Customer Service Rep.
Business Unit B SBA Manager
BUB
SetID Location
Default SBA Location 1: Headquarters
SetID: SBA Location 2: North
n l y
SetID
SBA
Salary Plan
e O
Business Unit A Salary Plan
U s
I
Slide 57 _______________________________________________________________________________________________________
A
Student Notes O
l &
a
Analyzing Your Business Unit Needs
n
te r
Assume your new company, Computer Testing Research, wants to create two business
units: Business Unit A (BUA) and Business Unit B (BUB). The next task is to determine
the business unit data needs; let us begin with Business Unit A (BUA).
I n
cl e______________________________________________________________________
r a ______________________________________________________________________
O ______________________________________________________________________
______________________________________________________________________

Example: Analyzing Your Business Unit Needs (continued)

This example shows data needs for Business Unit B:
Computer
Testing SetID Department
Research SBA Office of the President
SBA Business Unit A Sales
Business Unit A SBB Business Unit B Sales
BUA SBB Business Unit B Customer Serv

SetID: SBA SBA Sales Support
X SBA Customer Service Rep.
Business Unit B SBA Manager
BUB
SetID Location
Default SBA Location 1: Headquarters
SetID: SBB SBA
SBB
Location 2: North
Location 30: South
n l y
SetID Salary Plan
e O
SBA
SBB
s
Business Unit B Salary Plan
U
A I
Slide 58 _______________________________________________________________________________________________________
O
Student Notes
l &
n a
Analyzing Your Business Unit Needs (continued)
te r
After you have determined data needs for one business unit, you need to analyze the
needs of your other business units. You may find that some of the needs are different, but
I n
some of the data can be shared, such as the job codes in this example.
cl e
Common Data
O ra In this example, you do not want to create another set of job codes when both business
units can use the same information. However, the second business unit does not have
access to the tableset values SBA. Record groups and the TableSet Control component
can resolve this problem.


This example shows how you would set up information for Business Unit A on the
TableSet Control component:
Computer
Testing Research
Business Unit A
BUA
SetID Department
Default TableSet Control SBA Office of the President
SetID: SBA component SBA Business Unit A Sales
Business Unit B SBB Business Unit B Sales
BUB SBB Business Unit B Customer Serv
SetID: SBB SBA Sales Support
Set Control Value BUA
Default SetID SBA
SBA
SetID
Manager
Location
n l y
Rec Grp
HR_01
Description
Departments
SetID
SBA
SBA
SBA
SBB
O
Location 1: Headquarters
Location 2: North
e
Location 30: South
HR_02
HR_03
Job Codes
Locations
SBA
SBA
U
SetID s Salary Plan
HR_05 Plan Salaries SBA
A I SBA
SBB
O
Slide 59 _______________________________________________________________________________________________________
l &
Student Notes
n a
te r
Using the TableSet Control Component to Determine Your Business Unit
n
Needs
I
c l e
Use the TableSet Control component to adjust your business unit and setID mappings for
greater effectiveness.
r a
O ______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


This example shows how you would set up information for Business Unit B on the
TableSet Control component:
Computer
Testing Research
Business Unit A
BUA
SetID Department
Default SBA Office of the President
SetID: SBA SBA Business Unit A Sales
Business Unit B TableSet Control SBB Business Unit B Sales
BUB component SBB Business Unit B Customer Serv
SetID: SBB SBA Sales Support
Set Control Value BUB
Default SetID SBB
SBA
SetID
Manager
Location
n l y
Rec Grp
HR_01
Description
Departments
SetID
SBB
SBA
SBA
SBB
O
Location 2: North
e
Location 30: South
HR_02
HR_03
Job Codes
Locations
SBA
SBB
U
SetID s Salary Plan
HR_05 Plan Salaries SBB
A I
SBA
SBB
O
Slide 60 _______________________________________________________________________________________________________
l &
Student Notes
n a
te r
TableSet Control Record Groups
I n
You can modify the setID for each record group to share or restrict data. This example
c l e
provides a good example of tableset sharing for job codes.
r a ______________________________________________________________________
O ______________________________________________________________________
______________________________________________________________________


In this example, a common setID of SHARE will be implemented:
Computer
Testing Research
Business Unit A
BUA
SetID Department
Default SBA Office of the President
SetID: SBA SBA Business Unit A Sales
Business Unit B TableSet Control SBB Business Unit B Sales
BUB component SBB Business Unit B Customer Serv
SetID: SBB SHARE Sales Support
SHARE Customer Service Rep.
SHARE Manager
Set Control Value BUB
Default SetID SBB SetID
SBA
Location
n l y
Rec Grp
HR_01
HR_02
Description
Departments
Job Codes
SetID
SBB
SHARE
SBA
SBB O
Location 2: North
Location 30: South
e
HR_03
HR_05
Locations
Plan Salaries
SBB
SBB
SetID
SBA
U s Salary Plan
A I SBB Business Unit B Salary Plan
O
Slide 61 _______________________________________________________________________________________________________
Student Notes
l &
n a
Common SetIDs
te r
If you define setIDs that are to be tied to one specific business unit, you may want to
I n
define generic setIDs to be used across numerous business units that share identical data.
cl e
In this example, because all business units will share the same job codes, a common
setID of SHARE will be implemented.
r a
O

How the TableSet Control Table Works

The system retrieves only the valid values for the designated business unit:
Job Data component for a worker: TableSet Control component
Work Location page Set Control Value BUA
Business Unit BUA

Rec Grp Description SetID
Department HR_01 Departments SBA
Looks for only the

rows with this setID
The view on this
field displays only
valid values for Department Table
this business unit SetID Code Description
SBA
SBA
50100 Office of the President
50200 Business Unit A Sales
n l y
SBA
SBB 50200 Business Unit B Sales
e O
50300 Business Unit A Customer Serv
SBB
s
50300 Business Unit B Customer Serv
U
I
Slide 62 _______________________________________________________________________________________________________
A
Student Notes
O
l &
The Process of Retrieving Valid Values
n a
This diagram shows the process unseen by the user that the system follows when a user
te r
searches on the Department field. The user will get a list of valid values contained within
the business unit that the worker has been associated with.
I n
Using the Department field as an example, you want to get a list of valid values
c l e
(departments). For the system to retrieve this data, it accesses the TableSet Control table
first:
r a 1. When you search for valid values in the Department field, the system asks, “With
what business unit is this person associated?”
O 2. The Business Unit field displays the business unit BUA.
3. The system then accesses the TableSet Control table for the set control value
(business unit) BUA.

4. Since the Department table is part of record group HR_01 Departments, the system
references this line to determine the setID, which is SBA.
5. The system accesses the Department table and retrieves all rows with a setID of SBA.
6. This list of valid values appears in the search dialog box on the Department field.
Note. If no rows of data with the defined setID were found, the system informs you that
no matching entries were found.
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
n l y
______________________________________________________________________
e O
s
______________________________________________________________________
U
I
______________________________________________________________________
A
O
______________________________________________________________________
l &
______________________________________________________________________
n a
r
______________________________________________________________________
te
n
______________________________________________________________________
I
c l e______________________________________________________________________
r a ______________________________________________________________________
O ______________________________________________________________________
______________________________________________________________________

Creating SetIDs
Establishing setIDs is the first step in setting up your business unit and setID foundation
tables within the system.
Use the TableSet IDs component to define your high-level keys for many of your control
tables.
Slide 63 _______________________________________________________________________________________________________
Student Notes
Page Used to Create SetIDs

TableSet Control PeopleTools, Utilities, Administration, TableSet IDs
Use this page to create setIDs:

n l y
e O
U s
A I
O
l &
TableSet Control page
n a
te r
I n
______________________________________________________________________
cl e
______________________________________________________________________
r a ______________________________________________________________________
O ______________________________________________________________________
______________________________________________________________________

Creating Business Units

Business units enable you to:
• Maintain a tree structure to facilitate customer-specific roll-up reporting.
• Distribute and administer certain control tables such as the Department table. This is
especially important for large or multinational companies.
Slide 64 _______________________________________________________________________________________________________
Student Notes
Page Used to Set Up Business Units

Business Unit Set Up HRMS, Foundation Tables, Organization, Business Unit
Use this page to enter business unit information: n l y

e O
U s
A I
O
l &
n a
te r
I n
c l e
Business Unit page
r a
O Use the Business Unit page to define business units for reporting demands or organizing
operating responsibilities. You have a great deal of flexibility in how to implement this
organizational level in your PeopleSoft HRMS application. Each business unit will then
use the established setIDs as a base for tableset sharing.

Setting Up the TableSet Control Record Groups

After you establish both your setIDs and your business units, the next step is to determine
which setID you want the system to access for each record group for each HR business
unit.
Use the TableSet Control, Record Group page to specify a setID for each set of business
unit record groups. Consider the following:
• Record groups consist of many similar records and views, and not individual tables.
• Using record groups saves you the step of assigning setIDs to each record or view in
the system that uses setIDs as a high-level key, without requiring you to know all of
the tables that are involved in a particular function.
Slide 65 _______________________________________________________________________________________________________
Student Notes
Page Used to Set Up Record Group Information

n l y
Page Name
Record Group
Navigation
e O
PeopleTools, Utilities, Administration, TableSet Control
U s
A I
O
l &
n a
te r
I n
c l e
r a
O

Use this page to maintain record-group information:
Record Group page
______________________________________________________________________
n l y
e O
______________________________________________________________________
U s
______________________________________________________________________
A I
______________________________________________________________________
O
&
______________________________________________________________________
l
a
______________________________________________________________________
n
te r
______________________________________________________________________
I n
______________________________________________________________________
c l e______________________________________________________________________
r a
O ______________________________________________________________________
______________________________________________________________________

Activity 2: Defining SetIDs, Business Units, and TableSet Sharing

In this activity, you will review the activity overview and:
1. Establish setIDs.
2. Create business units.
3. Administer tableset sharing.
See Human Resources: Activity Guide, lesson 4, “Setting Up Core Foundation Tables
Related to Business Units and TableSet Sharing,” Activity 2: Defining SetIDs, Business
Units, and TableSet Sharing.
Slide 66 _______________________________________________________________________________________________________
Student Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
n l y
e O
______________________________________________________________________
U s
______________________________________________________________________
A I
______________________________________________________________________
O
&
______________________________________________________________________
l
a
______________________________________________________________________
n
te r
______________________________________________________________________
I n
______________________________________________________________________
c l e
______________________________________________________________________
r a
O ______________________________________________________________________
______________________________________________________________________

Establishing User and Business Unit Defaults
User Versus Business Unit Defaults

This diagram depicts the tables that are typically affected when you have established
defaults in the Org Defaults by Permission Lst and Business Unit Options Defaults
components:
User ID: PS
Business Unit: BUA
Perm List: HCPPALL
Org Defaults by Business Unit

Permission Lst Options Defaults
Provides Business
Provides User Defaults
Unit Defaults
Location Department Salary Plan Job Code Transactional table

pages defining business
n l y
Control table pages
e O
unit-related information
s
Slide 67 _______________________________________________________________________________________________________
U
Student Notes
A I
O
l &
User Defaults Versus Business Unit Defaults
User defaults are associated with your user ID and assist primarily in supplying
n a
information on the setup tables.
te r
Business-unit defaults are typically related to transactional pages, where you are defining
data, such as a budget, for a specific business unit.
I n
c l e
Default Values
When a user signs in to the system, defaults and control values throughout PeopleSoft
r a HRMS are based on the defaults that you have established for that user’s permission list
on the Org Defaults by Permission Lst component. You can also link specific defaults to
O a setID that is associated with your business unit. That way, when a user selects a
business unit on tables and pages throughout PeopleSoft Human Resources, default
values such as Country and Currency fill the pages automatically, based on the defaults
that you have established on the Business Unit Options Defaults component.

Establishing User and Business Unit Defaults (continued)
User Defaults and Primary Permission Lists

When you create a user ID, you can associate various roles and permissions lists with that
user.
These roles and permission lists grant a user access to pages, components, and people’s
data.
Permission List
User ID Role (mgr self service)
(PS) (Manager)
Permission List
(compensation)
Permission List
(training)
Role
(Employee)
Permission List
n l y
(employee self service)
O
Slide 68 _______________________________________________________________________________________________________
e
Student Notes
U s
Roles and Permission Lists
A I
Permission List O
Create permission lists to assign access to menus,
l & components, component interfaces, pages, global

functionality, data, and so forth.
a
rn
Role Assign permission lists to a role to create access that is
required for role specific tasks.
t e
e In
c l ______________________________________________________________________
r a
O ______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

User Defaults and Primary Permission Lists (continued)

In addition to assigning roles to each user, which in turn are tied to permission lists, you
will assign four primary permission lists directly to each user:
User ID
Navigator Homepage
Permission List
Process Profile Permission List
Primary
Permission List
Row Security Permission List
n l y
O
Slide 69 _______________________________________________________________________________________________________
e
Student Notes
U s
Page Used to Associate Permission Lists with a User
A I
O
User Profiles, General
l &
PeopleTools, Security, User Profiles, User Profiles
n a
te r
I n
c l e
r a
O

Use this page to associate permission lists with a user:
User Profiles, General page
Permission Lists Associated Directly with the User
Navigator Homepage Used by workflow.

Process Profile
Primary
PeopleSoft Process Scheduler authorization.
n l y
Global security. Also used to associate the user to the Org
Defaults by Permission Lst component to define user
defaults.
e O
Row Security
U s
Data-permission security.
A I
O
______________________________________________________________________
l &
______________________________________________________________________
n a
r
______________________________________________________________________
te
I n
______________________________________________________________________
cl e
______________________________________________________________________
r a ______________________________________________________________________
O ______________________________________________________________________
______________________________________________________________________

Setting Up User Defaults

To define user defaults, use the primary permission list that is associated with the user ID
on the User Profiles, General page to access the Org Defaults by Permission Lst
component.
The Org Defaults by Permission Lst component enables organizations to set up defaults
such as:
• Business unit • Country
• SetID • Company
• Currency • (JPN) Alternate character enabled
Slide 70 _______________________________________________________________________________________________________
Student Notes
n l y
Pages Used to Set Up User Defaults
e O
Page Name
Defaults
Navigation
U s
Set Up HRMS, Foundation Tables, Organization, Org Defaults by Permission
Settings
Lst
A I
Set Up HRMS, Foundation Tables, Organization, Org Defaults by Permission
Lst
O
l &
n a
te r
I n
c l e
r a
O

• Use this page to enter default information:
Defaults page
• Use this page to specify payroll system and standard hours defaults:
n l y
e O
U s
A I
O
l &
n a
te r
I n
cl e
Settings page
r a
O

Setting Up Business Unit Defaults

The Business Unit Options Defaults component works like the Installation Table. It lets
organizations set system defaults such as company, country, and currency for a specific
setID.
Consider the following facts when setting up business unit defaults:
• The setID is the high-level key for the Business Unit Options Defaults component.
• Since the setID is the high-level key, you can share these defaults among multiple
business units and these values will be supplied by default to fields throughout the
Human Resources system.
• You should associate the business unit to the setID by using record group HR_06
(BU Defaults) in the TableSet Control component.
Slide 71 _______________________________________________________________________________________________________
Student Notes
n l y
Page Used to Enter Business Unit Defaults
e O
Page Name
Business Unit Options
Navigation
U s
Set Up HRMS, Foundation Tables, Organization, Business Unit Options
Default Defaults
A I
O
l &
n a
te r
I n
c l e
r a
O

Use this page to enter business unit options defaults:
Business Unit Options Default page
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
n l y
e O
______________________________________________________________________
U s
______________________________________________________________________
A I
______________________________________________________________________
O
&
______________________________________________________________________
l
a
______________________________________________________________________
n
te r
______________________________________________________________________
I n
______________________________________________________________________
c l e
______________________________________________________________________
r a
O ______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 3: Establishing User and Business Unit Defaults

In this activity, you will review the activity overview and:
• Set up user defaults.
• Establish business unit defaults.
See Human Resources: Activity Guide, lesson 4, “Setting Up Core Foundation Tables
Related to Business Units and TableSet Sharing,” Activity 3: Establishing User and
Business Unit Defaults.
Slide 72 _______________________________________________________________________________________________________
Student Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
n l y
O
______________________________________________________________________
e
s
______________________________________________________________________
U
I
______________________________________________________________________
A
O
______________________________________________________________________
l &
______________________________________________________________________
n a
te r
______________________________________________________________________
______________________________________________________________________
I n
c l e ______________________________________________________________________
r a ______________________________________________________________________
O ______________________________________________________________________
______________________________________________________________________

Identifying Implementation and Worker-Level Default Options
Implementation Table Defaults

This diagram shows the implementation-level default options that are available from the
Business Unit and tableset sharing-related tables:
Org Defaults by
Business Unit
Business Unit Primary
Options Defaults
Permission Lst
SetID Company Business unit

Country SetID
Currency Company
Standard hours Country
Work period Currency
Standard hours
Work period
l
Regulatory region
n
Slide 73 _______________________________________________________________________________________________________
y
e O
Student Notes
U s
A I
______________________________________________________________________
O
______________________________________________________________________
l &
a
______________________________________________________________________
n
te r
______________________________________________________________________
I n
______________________________________________________________________
c l e
______________________________________________________________________
r a ______________________________________________________________________
O ______________________________________________________________________
______________________________________________________________________

D41114 PDF 76 100

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

D41114 PDF 76 100

Uploaded by

Copyright:

Available Formats

Setting Up Core Foundation Tables Related to Business Units and TableSet Sharing Lesson 4

Defining SetIDs, Business Units, and TableSet Sharing (continued)

Department View of all Department-Level

Delivered Human Resources Record Groups

HR_02 Job Codes.

HR_12 FP Actions Group.

• HR_04 Job Tasks and Requirements. O • HR_14 Labor Agreement.

• HR_05 Plan Salaries.

O ra • HR_10 Credit Card Vendor

66 PeopleSoft Proprietary and Confidential

Other Delivered HRMS Record Groups

• PY_01 Balance ID Tbl-Setid Company.

• PY_02 Shift Table-Setid Paygroup.

Page Used to Maintain Record Groups

PeopleSoft Proprietary and Confidential 67

Defining SetIDs, Business Units, and TableSet Sharing (continued)

Record Groups (continued)

Record Group SetID

HR_01 Departments SBA

Business Unit HR_02 Job Codes SHARE

HR_03 Locations SBA

68 PeopleSoft Proprietary and Confidential

Defining SetIDs, Business Units, and TableSet Sharing (continued)

Example: Analyzing Your Business Unit Needs

Default SetID Job Code

PeopleSoft Proprietary and Confidential 69

Defining SetIDs, Business Units, and TableSet Sharing (continued)

Example: Analyzing Your Business Unit Needs (continued)

Default SetID Job Code

70 PeopleSoft Proprietary and Confidential

Defining SetIDs, Business Units, and TableSet Sharing (continued)

Example: Analyzing Your Business Unit Needs (continued)

PeopleSoft Proprietary and Confidential 71

Defining SetIDs, Business Units, and TableSet Sharing (continued)

Example: Analyzing Your Business Unit Needs (continued)

72 PeopleSoft Proprietary and Confidential

Defining SetIDs, Business Units, and TableSet Sharing (continued)

Example: Analyzing Your Business Unit Needs (continued)

A I SBB Business Unit B Salary Plan

PeopleSoft Proprietary and Confidential 73

Defining SetIDs, Business Units, and TableSet Sharing (continued)

How the TableSet Control Table Works

Job Data component for a worker: TableSet Control component

Work Location page Set Control Value BUA

Business Unit BUA

Looks for only the

74 PeopleSoft Proprietary and Confidential

PeopleSoft Proprietary and Confidential 75

Defining SetIDs, Business Units, and TableSet Sharing (continued)

Page Used to Create SetIDs

Use this page to create setIDs:

76 PeopleSoft Proprietary and Confidential

Defining SetIDs, Business Units, and TableSet Sharing (continued)

Creating Business Units

• Maintain a tree structure to facilitate customer-specific roll-up reporting.

Page Used to Set Up Business Units

Use this page to enter business unit information: n l y

PeopleSoft Proprietary and Confidential 77

Defining SetIDs, Business Units, and TableSet Sharing (continued)

Setting Up the TableSet Control Record Groups

Page Used to Set Up Record Group Information

78 PeopleSoft Proprietary and Confidential

Use this page to maintain record-group information: