Requests: Discrepancy Tab – Net-Inspect

Navigation Path: Requests > View All > [Select Requests Record from table] > Discrepancy Tab

The Discrepancy tab is where non-conformances and quality issues are documented and dispositioned within a Request. This tab allows both supplier and customer users to add detailed information about discrepancies, upload supporting documents, and manage dispositions.

Overview

The Discrepancy tab displays summary information at the top showing Part Number, Part Name, Qty Manufactured, Discrepant Qty, and Associated Requests (described below).

By Parts/Supplier: Count of related Requests records grouped by part # and supplier combination (excluding current record)
By Supplier: Count of related Requests records from the same supplier

This helps track patterns and related issues across multiple requests.

Adding and Managing Discrepancies

All fields within discrepancies, even required fields, are required when signing but not at save. If clicking a submit/sign/return button does not work, press these buttons again and the application will highlight fields in red which are missing but required.

Discrepancies Header

Use the collapse/expand button to collapse individual discrepancies into their header
+ ADD DISCREPANCY button
- Located in the top-right corner of the Discrepancies section. Click to add a new discrepancy (maximum of 10 per request)

Discrepancies

Editable by both supplier and customer.

Each discrepancy has a collapsible header containing the following:

Discrepancy #: Discrepancies are automatically numbered sequentially (Discrepancy #1, Discrepancy #2, etc.)
Defect Type and Disposition: Pull from the selections made within the discrepancy as quick glance information
Delete button: removes the discrepancy it is found within

Defect Type
Required. Dropdown selection that categorizes the type of non-conformance. Dropdown is defined by the record's license holder (usually the customer).

Non-Conformity Description
Required. Free-text field for detailed description of the non-conformance or quality issue.

Characteristic #
Optional. Reference number or identifier for the specific characteristic that is non-conforming.

Should Be Requirement
Required. Description of what the requirement should be or the correct specification.

Is Condition
Required. Description of the actual condition found during inspection.

Cause
Required when visible. Dropdown selection for primary cause category. This field's visibility and its dropdown options are defined by the record's license holder (usually the customer).

Sub-Cause
Conditionally required. Dropdown selection for specific sub-cause within the primary cause category. This field's visibility and its dropdown options are defined by the record's license holder (usually the customer).

Root Cause Comments
Optional. Analysis of the underlying cause of the non-conformance.

Proposed Corrective Action
Optional. Suggested actions to address and prevent recurrence of the non-conformance.

Affected Part Numbers

Optional. When the Info tab has "Assembly" selected for "Detail or Assembly Part," an additional table appears allowing entry of individual components affected by the discrepancy. This table tracks Part Number, Part Rev, Drawing #, and Drawing Rev Lvl. Click "+ ADD" to add more rows.

Disposition Section

Available only to the customer listed on the record.

Disposition
Required. Dropdown for final disposition decision. Dropdown is defined by the record's license holder (usually the customer).

Liability
Optional. Field indicating responsibility or liability assignment for the non-conformance. Options are Supplier, Customer, and Sub-Tier.

Disposition Comments
Free-text field for additional comments related to the disposition decision.

Acceptance Type
Optional. Dropdown selection for the type of acceptance decision made for the disposition. Does not have logic based on the disposition selected.

Discrete Qty: selecting this makes an additional field appear called "Qty Accepted" which is required
Discrete PO: indicates acceptance is for all PO information found in the Scope table
Effective Dates: selecting this makes two additional fields appear called "Start Date" and "Expiration Date" (latter is required)
Permanent: indicates acceptance is permanent and no additional Requests are necessary.

Disposition by Discrepancy (default) vs Disposition by Scope

By default, each discrepancy has the above disposition fields, allowing different disposition decisions for each non-conformance.

Toggling to "Disposition by Scope" allows allows the user to disposition once for the whole record or, if desired, against individual rows in the Scope table for PO, Lot/Batch #, and/or Serial #'s. Switching to this option will open a warning modal confirming the following actions (which cannot be undone):

Removes all disposition-related fields and their data from individual discrepancies (but not discrepancy data)
Adds disposition fields as columns in the Scope table (see this article for the scope table)

Documents Section

Both supplier and customer users can upload supporting documents specific to each discrepancy. These are also tracked on the Documents tab.

Internal View Only
Customer users can mark documents as "Internal View Only," meaning supplier users can see that a document exists but cannot open or download it. This setting can be modified after upload.

Scope

This section defines reference information for the Requests record. Read this article for more information.

Submission

Suppliers submit the record to the customer by clicking the "Submit" button in the "Submission Signature" column. This opens a modal where the supplier user can enter the following information. Title/Function, email, and comments are stored in the Submission table.

Title/Function: Required. This will pull from the user's profile but can be modified
Comments: Optional.
Submission acknowledgement: Required when visible.
Email: is not visible on the modal - this pulls from the user's profile "Alert and Notifications Email"

Additional Requirements

This section defines additional requirements from the customer. Read this article for more information.

Review Signatures

This table defines the functions of customer users required to review the Requests record. Read this article for more information.