Tableset Sharing

Tableset sharing is the sharing of common control tables among business units. There are two types of tables in the PeopleSoft system that are used to store data.

Term	Definition
Control Tables	These tables store control lists of information; for example, department names and account codes. This data is maintained centrally by the institution and is generally entered once at implementation, and it changes little over time. The structure and processing rules for each of the PeopleSoft applications you are using are defined in a series of control tables. Control tables are usually keyed by tableset ID and are usually effective-dated.
Transaction Tables	These tables store day-to-day business activity and are updated frequently. They are keyed by business unit.

Control tables enable you to use tableset IDs, which make tableset sharing possible. The tableset ID indicates which of the rows in the control table a particular business unit can access. Each row in the control table has a tableset ID associated with it and business units are associated with tableset IDs through record groups:

Business units pass data through record groups to tableset IDs.

Note:

The tableset ID is also referred to as the setID. These terms are interchangeable.

If much of the control table data is the same from business unit to business unit, tableset sharing enables you to share that information among business units instead of having to enter the same data multiple times. For example, suppose that an institution has 10 business units and they all use the same accounts. Instead of having to enter all of the accounts 10 times, you could enter them once and set up tableset sharing to enable all of the business units to access them.

Tableset sharing also enables you to manage exceptions within the organization. For example, suppose that 9 of the 10 business units use the same accounts, but the tenth business unit uses entirely different accounts. This is easily accommodated through tableset sharing.

The two following tables show how different business units access a centralized control table based on tableset ID. In the example, there are three tableset IDs—MAINC, EASTC, and WESTC—representing three campuses. The account number information for all campuses is contained in a single control table. Allowing access to certain tableset IDs can restrict access to the account number information. For example, East Campus (EASTC) can view only its two account numbers when it accesses the control table.

Here are the accounts for all three campuses:

Tableset ID	Account Number
MAINC	0000090345
MAINC	0000090346
EASTC	0000090347
MAINC	0000090348
EASTC	0000090349
WESTC	0000090350

This view shows only the accounts for East Campus:

Tableset ID	Account Number
EASTC	0000090347
EASTC	0000090349

See PeopleTools: Data Management, "PeopleTools Utilities."