|
|
|
|
|
This page allows you to create inspection request for inspection plans having the origin as “All” or “Quality Management”. Tell me more.
Click the “Create Inspection Request” link from the “Quality Management” business component.
The “Create Inspection Request” page appears.
Enter the following in the “Request Details” group box:
|
Request Number |
A unique code identifying the inspection request (Alphanumeric, 18). Mandatory. If the field is left blank the system generates the number if a template has been specified in the “Setup QC Parameters” activity for automatic request number generation. |
|
Press <Enter> key. |
|
|
The system displays the request details in the page. |
|
|
Requested Date Time |
The date and time when the inspection request was raised (Date Format). The system displays the system date and time by default on launch of the page. This date should be later than the current date. |
|
Type |
Use the drop-down list box to select the request type. You can select “Quality Clearance” or “In Process”. The system displays “Quality Clearance” by default on launch of the page. |
|
Result Requested Expected Date Time |
The date and time when the feedback of the inspection is expected (Date Format). The system displays the system date and time by default on launch of the page. This date should be later than the current date and the date of inspection request. |
|
Inspection Plan ID |
The code identifying the inspection plan to be associated with the request (Alphanumeric, 50). Mandatory. |
The system displays the following:
|
Description |
The textual description of the inspection plan. |
|
Control Point ID |
The code identifying the control point for which the inspection needs to be carried out. The control point id is retrieved from the “Create Controlpoint Definition” page of the current business component. |
|
Description |
The textual description of the control point. |
The system displays the following in the “Item Details” group box:
|
Item Code |
The code identifying the item for which the inspection request is raised. |
|
Variant |
The code identifying the variant of the item. |
|
Description |
The textual description of the item or item variant. |
|
Origin ID |
The application from where the inspection request is raised, which could be “Quality Management”, “Production”, “Sales”, “Purchase”, "Inventory" or “All”. |
Enter the following:
|
Lot Number |
The code identifying the item that is lot controlled, for which the inspection request is raised (Alphanumeric, 18). The item code is displayed from the “Item Administration” business component. |
|
Sub Lot Number |
The code identifying the item that is sub-lot controlled, for which inspection request is raised (Alphanumeric, 03). The item code is displayed from the “Item Administration” business component. |
|
Reference Document Type |
Use the drop-down list box to select the type of reference document that is associated with the request. You can select from “Inventory”, “Production”, “Sales” and “Purchase”. The system leaves the field blank by default on launch of the page. |
|
Reference Document Number |
The number identifying the reference document (Alphanumeric, 20). For example, If the “Ref Doc Type” field is set to “Production”, then “Ref Doc No.” will be “Production Order No.”. |
|
Reference Line Number |
The number identifying the reference line (Integer). For example, If the “Ref Doc Type” field is set to “Production”, then “Ref Line No.” will be “Production Order Line No.”. |
|
Container Item Code |
The code identifying the item in the container (Alphanumeric, 32). |
|
Container ID |
The code identifying the container (Alphanumeric, 18). |
Enter the following in the “Sampling Details” group box:
|
Inspection Quantity |
The quantity of the samples to be inspected (Integer). Quantity entered should be a positive integer. |
|
UOM |
The unit of measurement of the inspection quantity. It is mandatory to enter the UOM if “Inspection Quantity” has a value. UOM entered should be a positive integer and should be in “Active” status. |
|
Help facility available. |
|
|
Number of Samples |
The value indicating the number of samples that must be inspected (Integer). The system displays an error if this field is left blank when the Sampling Type is set to “Fixed” or “Variable”. The value entered should be a positive integer. |
The system displays the following:
|
Retention Samples |
The value indicating the number of samples retained for some specific reason. For example, if the sample size is 100 and if “10” is specified here, it implies that 10 items are retained for a specific reason, which could be inspected later. |
Enter the following:
|
Quantity per Sample |
The quantity specifying the sample size (Integer). The value entered should be a positive integer. |
Note: If the Sampling Type is “'%based” or “Square Root”, either Sample Size or Quantity Per sample must be entered.
|
UOM |
The unit of measurement in which the quantity is measured (Integer). It is mandatory to enter the UOM if “Quantity per Sample” has a value. UOM should be a positive integer and should be in “Active” status. |
|
Help facility available. |
Note: Fractions can be entered only if the UOM has been set to “Allow fractions” in the “Create UOM” activity of the “Unit of Measurement Administration” business component. Also, the system displays an error if there is no conversion factor exists in the UOM component between the UOM specified for Inspection Qty and the UOM for Quantity per Sample.
Enter the following in the “Reason Code Details” group box:
|
Reason Code |
Use the drop-down list box to select the code identifying the reason for creating the request. This code should have been defined in the “Maintain Reason Code” activity of the “Process Manufacturing Setup” business component. |
The system displays the following:
|
Description |
The textual description of the reason code. |
Enter the following:
|
Identification |
Any additional remarks pertaining to reason code (Alphanumeric, 100). |
Click the “Create” pushbutton to create the request.
The system displays the following:
|
Created By |
The name of the user who created the inspection request. |
|
Created Date |
The date on which the request was created. |
|
Modified By |
The name of the user who last modified the inspection request. |
|
Modified Date |
The date on which the request was last modified. |
Select the “Record Inspection Details” link provided in the page to update the inspection details along with the sample results.
Select the ”View Pending Requests” link provided in the page to view the requests pending for inspection.
Select the “Attach Notes” link provided in the page to specify the notes.
Select the “Specify Serial Number” link at the bottom of the “Create Inspection Request” page.
The “Serial Number for Inspection” page appears.
Note: The link is applicable only for serial controlled items.
Create Inspection Request – An overview
|
|
This page captures all the request details such as request number, request type, date on which the request was raised and the control point. The request can be raised based the origin id and the inspection plan. The origin could be purchase, production, sales, inventory or quality departments. These applications describe from where the inspection request may be received to the “Quality Model” application. For example, when an item is manufactured, a quality clearance request could be sent from “Production” application to “Quality” application for final clearance inspection. Similarly when an item is purchased a request may originate from “Purchase” application to “Quality” application for quality clearance inspection.
You can define a unique code for the inspection request. Otherwise the system displays the request number as set in the “Setup QC Parameters” page. You can attach a reason code to every request that is being raised. You are also allowed to view the pending requests and record the inspection details.
The system stores the login user id and the server date along with its modification details.
Mandatory
The inspection plan id must be defined in the “Create Inspection Plan” activity.
