Preparing Data for Use with PCC
To prepare data in other parts of the system for use in PCC, do the following:
1 Print existing ECOs, if any, using ECO by ECO Number Report (13.13.3). Implementing PCC disables ECO functions. You print ECOs in order to reenter them as PCOs.
2 Determine which manufacturing processes you want to control with PCC, and activate the appropriate sections. There are four possible activation programs:
• Execute Enable PCC Structure Maintenance (13.13.22). Set Structures to Yes to control product structures. This automatically disables ECO functionality in menu 13.13.
• Execute Enable PCC Routing Maintenance (14.22). Set Routings to Yes to control product routings.
• Execute Enable PCC Formula Maintenance (15.22). Set Formulas and Processes to Yes to control formulas and processes.
• Execute QM Enable PCC Item Spec Maintenance (19.26.1.22). Set Item Specifications to Yes to control item specification.
Important: Once you enable PCC and thereby disable ECO functions, do not use the ECO functions. Enabling PCC makes changes to your system that cannot be reversed.
3 Set up e-mail definitions for your system in E-mail Definition Maintenance (36.4.20). PCC uses e-mail to contact users during the approval process and life cycle of change documents. See
QAD System Administration User Guide for information on E‑Mail Definition Maintenance.
4 Create user IDs in User Maintenance (36.3.1). PCC users must be defined before they can be added to groups involved in PCC activities. Assign user passwords, or have users select their own. You can increase PCC security by requiring users to reenter passwords before accessing PCR/PCO Approval.
If you are using e-mail to notify users of PCC activities, make sure that each user has a valid e-mail address and definition.
Note: For security audit purposes, you cannot delete a user ID in User Maintenance after it has been successfully used for login. Instead, unneeded IDs are deactivated. When a user who is involved in the PCC life cycle is deactivated, be sure to update PCC groups and routing slips so that e-mail notifications are not sent to users who no longer can access the system; for example, those who have left the company. See
QAD Security and Controls User Guide for information on users and security.
5 Set up printers and batch IDs (36.13.2, 36.14.1, 36.14.3). Users can be notified at various points in the PCC life cycle either by printed reports or e-mail. Batch IDs are useful for running large print jobs during off-hours. Also, PCOs can be distributed (1.9.7.1), incorporated (1.9.7.5), and implemented (1.9.7.13) using batch IDs that execute nightly.
6 Initialize PCOs in PCC Control (1.9.24). The first time you enter PCC Control, you are prompted to initialize PCOs to current revision level. Answer Yes to have the system create PCO *000000*, which records current revision numbers for all items in the system. The initial revision numbers serve as a starting point for Item Revision History Browse (1.9.9.6).
7 It is important for purchase orders and for the operation of the Product Change Control module that the engineering revision level for an item is the same in Item Master Maintenance and Item-Site Planning Maintenance. Use the Item Revision No Variation Report (1.9.9.9) to highlight any revision variations for review and correction.