Understanding Quality Functions
This chapter provides an overview of quality functions and discusses how to:
Maintain quality functions.
Integrate with other PeopleSoft applications.
Understanding Quality Functions
Most production environments comprise several processing or data-collection areas. Each area can perform a different function and potentially yield unique process and traceability information. This makes it necessary to configure the quality control environment to ensure that it is capable of collecting information that is relevant to the business needs.
You can configure Quality to emulate these various data collection requirements through the use of quality functions. A quality function is a set of fields that identifies nonparametric information and maps process-specific field information into Quality for process identification, data tracking, and analysis.
Quality manages individual data-collection requirements simultaneously by not imposing a fixed-field hierarchy or traceability structure. Identifying key process information is essential to implementing effective quality control plans. You create a new configuration level (quality function) that defines the fields and attendant information that provides a base level for inspection plan creation and integration.
Common Elements Used in This Chapter
|
Quality Function |
Identifies a unique set of fields for collecting data. |
|
Field Name |
Displays the PeopleSoft database object name. |
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 section discusses how to:
Establish a Quality business unit.
Define quality functions.
Pages Used to Maintain Quality Functions|
Page Name |
Definition Name |
Navigation |
Usage |
|
BUS_UNIT_QS |
Set Up Financials/Supply Chain, Business Unit Related, Quality, Quality Definition, Quality Bus Unit |
Establish a Quality business unit. Note. You can't create an independent Quality business unit. |
|
|
QS_APP_DEF |
Quality, Define Methods and Procedures, Quality Functions, Define Quality Function |
Maintain application fields that are categorized as hierarchy or traceability to control data entry and analysis field input requirements. |
|
|
QS_COPY0_PNL |
Click the Copy From button on multiple pages in Quality. |
Create a new quality function by copying an existing quality function. |
Establishing PeopleSoft Quality Business
Units
Access the Quality Bus Unit (Quality business unit) page (Set Up Financials/Supply Chain, Business Unit Related, Quality, Quality Definition, Quality Bus Unit).
Quality business units are derived from Inventory, Purchasing, or Manufacturing business units. You can change the description.
Defining Quality Functions
Access the Define Quality Function page (Quality, Define Methods and Procedures, Quality Functions, Define Quality Function).
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.
|
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
|
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.
|
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.
See Also
Integration With Other PeopleSoft Applications
A quality function parents control plans with associated sample data and is the first point of integration between Quality and other PeopleSoft applications. The function provides awareness of the different fields that are common to an integrating application. Quality functions are created to synchronize fields with other PeopleSoft applications and eliminate the need to enter placeholders in unused fields.
To configure Quality to operate in a given data collection environment:
Define a quality function.
Identify the characteristics that you want to monitor on a measurement plan.
Create control plans that bring together a measurement plan and specific process identifiers.
Currently, Quality integrates with Purchasing, Inventory, and Production Management and delivers the following predefined quality functions to accommodate the integration between products:
|
PeopleSoft Application |
Quality Function |
Function Description |
Hierarchy Fields |
Trace Fields |
|
Purchasing |
RECV_INSPECT |
Receiving inspection. |
INV_ITEM_ID VENDOR_ID |
DISTRIB_LINE_NUM DISTRIB_SEQ_NUM LOT_ID OPRID RECEIVER_ID RECV_LN_NBR SERIAL_ID TAG_NUMBER VENDOR_LOT_ID |
|
Inventory |
RMA |
Inspect items on a returned material authorization. |
INV_ITEM_ID |
CONFIG_CODE CONTAINER_ID INV_LOT_ID QTY_INV_RECV RECEIPT_DTTM RECEIVER_ID RETURN_FROM_BU RETURN_FR_CUST_ID RMA_ID RMA_LN_NBR SERIAL_ID STORAGE_AREA |
|
Production Management |
COMPLETIONS |
Record completions against a production ID or schedule. |
COMPL_OP_SEQ INV_ITEM_ID MACHINE_CODE PRDN_AREA_CODE PRODUCTION_TYPE WORK_CENTER_CODE |
BOM_CODE DT_TIMESTAMP INV_LOT_ID OPRID PRODUCTION_ID RTG_CODE |
|
Production Management |
COMPL_NO_MC |
Same as COMPLETIONS, except no machine code field. |
COMPL_OP_SEQ INV_ITEM_ID PRDN_AREA_CODE PRODUCTION_TYPE WORK_CENTER_CODE |
BOM_CODE DT_TIMESTAMP INV_LOT_ID OPRID PRODUCTION_ID RTG_CODE |
|
Production Management |
COMPL_NO_OP |
Same as COMPLETIONS, except no machine code, work center code, or compl op seq (completion operation sequence) fields. |
INV_ITEM_ID PRDN_AREA_CODE PRODUCTION_TYPE |
BOM_CODE DT_TIMESTAMP INV_LOT_ID OPRID PRODUCTION_ID RTG_CODE |
|
Quality |
QUALITY |
Emulates the field structure that PeopleSoft 7.5 Quality uses. Use this if you upgrade from PeopleSoft 7.5 to PeopleSoft 8. |
INV_ITEM_ID MACHINE_CODE QC_STEP_ID STATION_CODE WORK_CENTER_CODE |
CREW_CODE DT_TIMESTAMP LOT_ID OPRID OP_SEQUENCE PRDN_AREA_CODE PRDN_DUE_SHIFT PRODUCTION_ID SERIAL_ID TASK_CODE TOOL_CODE |
See Also
Reviewing Control Plan Configurations
Integrating PeopleSoft Quality With Other PeopleSoft Applications