SetID Considerations in PeopleSoft Maintenance Management
PeopleSoft Maintenance Management uses system data, which is set up in PeopleSoft Asset Management, Project Costing, PeopleSoft Purchasing, PeopleSoft Expenses, PeopleSoft Inventory, PeopleSoft Resource Management, and other subsystems to create and process work orders. Much of the data that is set up in these subsystems is organized by SetID.
It is important to understand the difference between business units, SetIDs, and records:
| Name | Description |
|---|---|
|
Business units |
A business unit enables you to track specific business information for reporting and other data consolidation. A business unit may be, but is not required to be, a legal entity. You define and implement business units to suit the organizational needs of the company. The data from one business unit is segregated from the data of other business units in the organization, although it exists in the same physical database table. The entire organization may have only one business unit if every department uses the same processing rules. Multinational or otherwise diversified companies, such as those that contain multiple cost centers, divisions, or subsidiaries, may have multiple business units. |
|
SetIDs |
The accounting structure and processing rules for each PeopleSoft application are defined in a series of control tables, or tablesets. A tableset is a group of rows across control tables, identified by the same SetID, that allow sharing of control data among business units. Many business units may share the same set of data on the physical tables in the PeopleSoft HRMS or Financials system. In order for a business unit to process transactions, it must have an associated tableset. In simple terms, the business unit contains the actual data; the tableset contains the rules by which the data is processed. A SetID identifies each tableset. You must create at least one SetID even if you are not taking advantage of tableset sharing. You can have as many SetIDs as necessary, but tableset sharing becomes more complex with multiple SetIDs. Define tablesets when you implement any PeopleSoft application. |
|
Record Groups |
A record group is a set of logically and functionally related control tables and views. Record groups save time by enabling tableset sharing to be accomplished quickly without the burden of redundant data entry. Record groups also ensure that tableset sharing is applied consistently across all related tables and views in the system. The PeopleSoft TableSet Record Group control table associates a business unit or SetID value with a SetID value for each record group. One business unit or SetID can be associated with different SetIDs by record group. Group the record definitions for the tables that you want to share, as well as any dependent record definitions. If a new table is added to a PeopleSoft application, the appropriate record group may already be defined. However, if tables are added for a new business function, a new record group may also be required. |
SetID mapping is used to coordinate the various set control record groups. For example in PeopleSoft Maintenance Management, work order task and work order job templates reference SetIDs from various subsystems. You must set these templates to copy labor, PeopleSoft Inventory, purchase/on hand materials, and tool task requirement values, which are derived from various subsystems, to a work order task. These requirements must be compatible with the various work order business units used for each work order. To accomplish this, you set up the SetIDs as set control values using SetID mapping:
The following table lists some of the record groups used in PeopleSoft Maintenance Management:
| Record Group | Records within Record Group |
|---|---|
|
WM_01 |
|
|
WM02 |
Work order service group |
|
WM03 |
Work order type |
|
WM05 |
Work order priority |
|
WM06 |
WM business unit options |
|
WM07 |
Work order management status |
|
WM08 |
Work management crew schedule |
|
FS_18 |
|
|
RS_02 |
Labor Crafts |
|
AM_13 |
|
|
Ma AM_15 |
Asset Subtypes |
You must follow one rule and guideline to perform SetID mapping for work order job and work order task templates.