Maintaining Quality Functions
To define Quality Business Units, use the Quality Definition component (QUALITY_BU). To define quality functions, use the Quality Functions component (QS_APP_DEF). Use quality functions to specify hierarchy and trace field requirements inherent in a given process or family of processes. Quality functions enable interaction with Quality using native terms and eliminate the need for special placeholder fields.
Quality functions are defined at the system level to ensure continuity of access and analysis across multiple business units; therefore, you don't define quality functions by SetID or business unit. Quality also uses quality functions to determine which fields appear on pages when fields are available for data entry or data query on subsequent Quality pages.
This topic discusses how to maintain Quality functions.
|
Page Name |
Definition Name |
Usage |
|---|---|---|
|
BUS_UNIT_QS |
Establish a Quality business unit. You can't create an independent Quality business unit. |
|
|
QS_APP_DEF |
Maintain application fields that are categorized as hierarchy or traceability to control data entry and analysis field input requirements. |
|
|
QS_COPY0_PNL |
Create a new quality function by copying an existing quality function. |
Use the Quality Bus Unit page (BUS_UNIT_QS) to establish a Quality business unit.
Navigation:
Quality business units are derived from Inventory, Purchasing, or Manufacturing business units. You can change the description.
Use the Define Quality Function page (QS_APP_DEF) to maintain application fields that are categorized as hierarchy or traceability to control data entry and analysis field input requirements.
Navigation:
Note: After you associate a control plan with a quality function, you cannot add or delete fields. You can specify up to 12 trace fields and 12 hierarchy fields for a quality function.
Field or Control |
Description |
|---|---|
Graph Preference ID |
Select the default graph preference for the system to apply in those instances where a summary analysis is performed across multiple process streams and bar charts or Pareto charts appear. |
Data Persistence
Field or Control |
Description |
|---|---|
Session Data Life Days |
Specifies the number of days (1 to 120) to retain incomplete data-entry sessions for completion. This setting applies to all process streams that are created under the quality function. |
Edit Data Limit Days |
Specifies the number of days (1 to 365) that historical data is available for editing or correction. This setting applies to all process streams that are created under the quality function. |
Application Fields
Select how you use a field when entering quality data against control plans in the Field Use field. Field selections must be unique within a quality function and are categorized as either stream hierarchy fields or traceability fields. The list of available fields is system-defined by PeopleSoft and may vary depending on which PeopleSoft applications you have installed.
Field or Control |
Description |
|---|---|
Stream Hierarchy |
The field becomes a stream component, and the system uses it to maintain control limits. |
Traceability |
Identifies trace information when collecting sampling data. |
The field name (actual database object name) and default prompt table or view, which is used to populate drop-down lists if one exists for the field, appear when you select a field. You can override the prompt table or view on this page if you define a replacement or special-case view.