When you decide to inspect item quantities and make a decision as to whether or not to accept or reject them, you can use Oracle Quality in place of Oracle Purchasing to conduct an inspection (called a Receiving Inspection).
Inspection collection plans must be associated with the Receiving Inspection collection transaction and are unique in several ways:
Receiving Inspection collection transactions must be set as mandatory for items that have inspection required attributes. They are not mandatory for items with direct delivery or standard receipt attributes. Also, because Accept and Reject actions cannot be performed when the data collection is background, Receiving Inspection collection transactions cannot be set as background.
Note: You can override a mandatory collection plan. For example, you can change the inspection required attribute to direct delivery within the purchase order.
Receiving Inspections collection plans used for Receiving Inspections must be enabled.
Receiving Inspection collection plans must include the following collection elements:
Inspection Result
Quantity
UOM Name
Transaction Date
Note: These collection elements must be defined as Displayed, Mandatory and Enabled. If you disable any of these required collection elements or make them non-mandatory, the collection plan cannot be used for inspections.
Note: The collection elements Lot Number and Serial number will work in an Inspection transaction only when the receipt is created through WMS using the Mobile application and then inspected through the Desktop receiving inspection. Hence, the License Plate Number element is added by default to the collection plan when Lot and serial number elements are added to a Receiving Inspection plan.
The Accept the shipment and Reject shipment actions should be associated with the Inspection Result collection plan element.
To ensure that these conditions are met, when you associate the Receiving Inspection collection transaction with an enabled collection plan, the system prompts you to complete the setup. You cannot save your work until you have entered quality results or had them defaulted in.
To simplify the process of creating inspection collection plans, two template collection plans, PO Inspection (for discrete manufacturing organizations) and Template OPM Receiving Inspection Collection Plan (for process manufacturing organizations), are pre-seeded in Oracle Quality. See: Creating Collection Plans from Templates.
You can copy the elements from either template collection plan to the inspection collection plan you have created to ensure that the required collection elements are included. Both template collection plans also include collection elements that are not required. Once copied over to your own collection plan, you can delete those collection plan elements - Comments, Quality Code, Reason Code, Supplier Lot Number - that are copied but are not required. You can also add user-defined and additional context elements.
You can optionally define specifications and specification sub-types. When quality data is collected, you can choose a specification to be used during quality data collection.
RMAs are created in Order Management, and distinguished from sales orders via the Order Type field on the Sales Order form. When an item is returned in Order Management, the original sales order number is used as the RMA number.
RMA receiving and inspection is performed in Oracle Purchasing, and uses the same process as Oracle Purchasing receiving and inspection transactions. The receipt sources are distinguished by Source Type. Oracle Quality's existing receiving and inspection functionality supports RMA. You can define collection plans and associate them with receiving and inspection transactions.