You use this activity to define NC codes (see NC Code).
This activity allows you to do the following:
Assign disposition routings to NC codes
Define operations and disposition groups where NC codes can be logged
Assign NC groups to an NC code
Associate existing NC codes with the current NC code as secondary NC codes
Associate hook point activities with NC codes (see Setting Up Activity Hooks)
Enter values in fields defined for NC codes in Custom Data Maintenance
(see Custom Data Maintenance)
The following tables describe fields requiring explanation:
Field | Description |
---|---|
| Controls whether the NC code is available for use on the shop floor
|
| Affects at which level the NC data is stored
|
|
|
| The category to which the NC code belongs The category you assign to this NC code determines which calculation the system uses to calculate the defects per million opportunities (DPMO). Note that a DPMO category is only applicable when the NC category is set to |
| Displays additional fields as defined and assigned for NC data types in |
|
|
| Identifies which message type is triggered when this NC code is logged |
| The priority of this NC code The higher the number, the higher the priority. If operators log multiple NC codes, the NC code with the highest priority determines the disposition of the part. |
| The maximum number of times this NC code can be logged against the same SFC number |
| Identifies if and how the NC code logged for the SFC number is used to determine if this SFC number should be accepted or rejected. Total NC severity of all NC codes logged for an SFC number during processing on sampling routing is compared to NC severity threshold defined in sample plan to determine SFC accept or reject decision (see Sample Plan Maintenance). When the total severity values of the NC codes logged for the sample SFC number equals or exceeds NC severity threshold, the sample is counted as rejected. Otherwise, the sample is accepted.
|
| Displays the entered text when an operator logs this secondary NC code |
|
|
|
|
| If selected, automatically marks this NC code's primary NC code as closed when the operator logs this NC code |
| If selected, automatically closes the incident specified in |
|
|
| If selected, triggers a quality notification to SAP ERP; and makes the |
| The catalog type for the logged NC code |
| The code group for the logged NC code |
| Quality notification (QN) code in ERP for the logged NC code |
Field | Description |
---|---|
| Specifies the operations where operators can log this NC code The asterisk (*) indicates all operations. |
| Specifies the disposition group associated with the operation (see Nonconformance Disposition) |
|
|
Field | Description |
---|---|
| Specifies the order in which the system executes this hook point |
| Specifies when the system should execute the activity identified in the |
| Specifies the hook point activity. The system runs this activity when this hook point is triggered for this NC code. |
| Allows you to temporarily disable the activity hook, for example when troubleshooting a problem
|
| Used only with hook point activities; contains additional parameters or values to be passed to the activity during the hook execution |