HCM Data Regulations

PeopleSoft HCM Data Regulated using the below setup information.
Business Units
Table Sets
Set ids
Record Groups
Business Unit Option Defaults
Org Defaults by Permission List

Now we will look at each item and try to understand what they meant to the organization.
Business Unit:

Set Up HRMS, Foundation Tables, Organization, Business Unit, Business Unit 

You create business units  to track and report specific business information.For HCM, you must establish at least one business unit.
If your organization uses same processing rules , it make sense to have a single business unit; if you use different rules in different companies, countries, or functional areas, you may choose to create multiple business units.

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


Tableset sharing:

Sharing rows of data in a tableset across business units or limiting rows to a single business unit.

Before you set up tableset controls setup Business Unit, Setid and Record Groups.

Understanding Table Set:
Table Set ID:
setID:
PeopleTools, Utilities, Administration, TableSet Ids
Use the above page to setup Logical SetID.
A set of data rows in a control table that is identified by the same high level key.

The highlevel key that identifies a set of data rows. There are two types of setIDs:

• Physical SetIDs
  The setID of a business unit (BUSINESS_UNIT = SETID). The rows of data in a physical setID have a one to one relationship with the business unit.
• Logical SetID
  A logical setID that is generic and determined by business rules other than business unit. Logical setIDs enable you to share rows of data across multiple business units.

Record Groups:
PeopleTools, Utilities, Administration, Record Group

Record Group is a group of records which will be shared by Setid across business units.You can make Record Group to be use of default Setid on this page, else it will be assigned using Table Set Control with group of Record Groups.

Table Set Control:
PeopleTools, Utilities, Administration, Table Set Control
Assigning Group of Record Groups to a Setid using a Set Control Value which could be business unit, country, reg region ...etc.

Example : When you give XXX as business unit on Job data page, it will pull the record groups for the set control value XXX and gets the list of all the departments or job codes from the record group corresponding to the Setid used on the set control page.

Org Defaults by Permission List:
Set Up HRMS, Foundation Tables, Organization, Org Defaults by Permission Lst, Defaults

On the Org Defaults by Permission List component (OPR_DEF_TBL_HR) set up primary permission lists with: Default values for the following fields: Business Unit, SetID,Company,Country,Regulatory Region, To Currency, Currency Rate Type.

Business Unit Option Defaults:
Set Up HRMS, Foundation Tables, Organization, Business Unit Options Defaults, Business Unit Options Defaults
When users access an HCM component, the system populates some of the fields, such as business unit, company, and country using the values you associated with the user's primary permission list. You can also associate default values with setIDs on the Business Unit Options Defaults page (BUS_UNIT_OPT_HR).

To set up business unit defaulting:
On the Tableset Control – Record Group page (SET_CNTRL_TABLE1), select the SetID that controls business unit defaulting for this business unit.

1. This enables you to share defaulting rules across business units.
   
2. Enter the setID's default values on the Business Unit Options Defaults component. 

Hope this gives fair understanding on Data Regulations using Business Unit, Set id and Table Set Sharing.