Understanding PeopleSoft HCM System Data Regulation
As companies grow larger and more complex, they often need to collect the same type of data across many locations. PeopleSoft business units and setIDs enable you to organize businesses into logical units other than companies and departments and to define how organizational data is shared among these units.
PeopleSoft HCM system data is regulated through the use of business units, tablesets and set IDs, and tableset sharing. Business units are logical devices that enable you to implement PeopleSoft HCM based on how your business is organized. Tablesets, set IDs, and tableset sharing are organizational devices that enable you to share – or restrict – the information stored in your HCM system across business units:
Term |
Definition |
|---|---|
Business Unit |
A logical organizational entity. |
Set ID |
A high-level key on many control tables. |
TableSet |
Set of rows on a control table, grouped by set ID, that is available to specific business units. |
Once you've developed your business unit map, use the following components to set up business units and set IDs and to define system defaults based on permission lists or business units:
|
Component |
Location |
|---|---|
|
TableSet IDs component (SETID_TABLE) |
|
|
Business Unit component (HR_BUSINESS_UNIT) |
|
|
Record Groups component (REC_GROUP_TABLE) |
|
|
Org Defaults by Permission Lst component (OPR_DEF_TBL_HR) |
|
|
Business Unit Options Defaults component (BUS_UNIT_OPT_HR) |
|
|
TableSet Control component (SET_CNTRL_TABLE1) |
|