Fundamentals

Control Tables, Transaction Tables and Prompt Tables

Control Tables :
• Is used to process and validate the day-to-day business activities (transactions)

• Is common and shared across an organization

• 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.

• It is generally static and is updated only when fundamental changes occur to business
policies, organizational structures, or processing rules.

Note : Control tables are tables that include the SETID key field (setID). As you set up control
tables, you’ll notice that it is the setID that enables control table information to be shared across
business units.
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.

Note. Transaction tables are tables that include the BUSINESS_UNIT field (which may or may not
be used as a key field).

Prompt Tables

• 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
Business Units, Tablesets and SetIDs
Business Units
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 enable you to implement PeopleSoft HRMS based on how your business is organized.

Tablesets and SetIDs

Tablesets and setIDs are devices that enable you to share – or restrict – information across
business units. For example, with tablesets and setIDs you can centralize redundant information
such as country codes while keeping information such as departments and job codes
decentralized. The overall goal of tablesets and setIDs is to minimize data redundancy, maintain
data consistency, and reduce system maintenance tasks.

PeopleSoft HRMS system data is regulated through the use of business units, tablesets and
setIDs, and tableset sharing. Business units are logical devices that enable you to implement
PeopleSoft HRMS based on how your business is organized. Tablesets, setIDs, and tableset
sharing are organizational devices that enable you to share – or restrict – the information stored
in your HRMS system across business units:
Possible Business Unit Structures :

How you define a business unit depends on your industry, statutory requirements,
regulatory reporting demands, or how you’ve organized operating responsibilities.
Consider the following scenarios:

• LGC Banking treats each branch as a business unit, which means that the bank could do reporting for
its people within each branch.

• 123 Global Business is a multinational company that separates its operations geographically because of
the necessities of conducting business abroad. What is more important to this organization may not be
each office, but each location. What’s happening in their American facility versus their European or
Asian market? Then they can track their business requirements and business needs accordingly.

• XYZ Entertainment has subsidiary companies. A highly diversified organization like this one might
choose to define each subsidiary company or cost center as a business unit. They might have a hotel
business as well as a retail business and they might want to keep this information separate, yet still be
able to roll everything up into one database and maintain it in a single location.

• 789 Inc. chooses to organize information by functionality or purpose, such as what is going on in Sales
versus Customer Service. It has created business units that reflect the administrative needs of their
human resources, benefits, and payroll departments.
Business units can represent branches, regions, subsidiaries, functional areas.
Implementing Business Units

While you can implement one business unit for your entire organization, establishing
multiple business units can offer important reporting and data control options. Multiple
businesses units enable you to:

• Maintain a tree structure to facilitate organization-specific, rollup reporting.

• Distribute administration of certain control tables, such as the Department component

(DEPARTMENT_TBL) or the Location component (LOCATION_TABLE) to different
business units.

• For large or multinational companies, this feature of business unit functionality in

PeopleSoft HRMS is useful for controlling data flow across different parts of the
enterprise.
PeopleSoft Enterprise Human Resources control tables that are keyed according to setID include the:

• Location component.
• Department component.
• Salary Plan component.
• Job Code component

Tableset Sharing

Record Groups and Tableset Sharing :

For the purpose of tableset sharing, control tables are divided into record groups. A record group is a
set of control tables and views that use the same group of setIDs in the same manner
Setting Up TableSet Sharing

Use tableset controls to make data available across business units or restrict to certain
business units. Before you set up tableset controls, create:

• Record groups
• Business units
• SetIDs

When you create and save a business unit, the system creates a record in the TableSet Control
component for the business unit (the Set Control Value) and populates the setID for each record
group with the setID you selected for the business unit. If you want the business unit to have
access to the rows in other setIDs for certain record groups, change the default setID to the
appropriate setID. This means that a lot of tableset sharing set up is done for you behind the
scenes.
Controlling Data Sets

The system filters the field options available to the user in the transaction components
based on the tableset controls you set up.

Example : When a user is creating a job data record for a new worker and selects the
drop down list for the Job Code field, the system filters the available options be
determining the following:

• What business unit is this job data record in?

USA

• What table controls data for this field?

JOBCODE_TBL

• What record group is that table in?

HR_02

• What SetID is assigned that record group for this business unit?
SHARE

• What rows in the control table are keyed by that setID?

The system makes available to the user only the rows keyed by the USA setID.
Navigations

• Peopletools-> Utilities->administration-> table setids

• Setup HRMS> foundation tables > Organisation > Business unit
• Setup HRMS> foundation tables > Organisation > Company
• Setup HRMS> foundation tables > Organisation > Location
• Setup HRMS> foundation tables > Organisation > Department
• Setup HRMS> foundation tables > Organisation > Business unit default options (defining
business unit rules)
• Setup HRMS> foundation tables > job attributes> job code table
• Tree Manager> Tree Utilities > Treee manager
• Setup HRMS> Security> Core row level security > refresh SJT_class_all
• Home>Set Up HRMS>Product Related>Compensation>Base Compensation>Salary
Grades
• Home>Set Up HRMS>Product Related>Compensation>Base Compensation>Salary Plan
• Home>Compensation>Base Compensation>Maintain Plans>Define Salary Plan