When you transfer items within Oracle Purchasing both internally (called Receiving Transfers) and right before delivering them to their final destinations (called Receiving Deliveries), you can use Oracle Quality to collect quality data on these items.
In Oracle Purchasing, you can use Receiving Transfers to transfer items from receiving and inspection to inventory or the shop floor, or to transfer items to different locations in the receiving and inspection area. For example, you might need to move refrigerated items from the receiving dock into a cold storage area while you are waiting to inspect them.
In Oracle Purchasing, you can use Receiving Deliveries to deliver items to their final destinations. For example, you can deliver items in receiving and inspection to stock or expense.
Oracle Quality allows you to collect quality data on items during transfers and deliveries and trigger actions.
The context elements that can be added to Receiving transfer and delivery collection plans are listed in the Collection Transaction and Context Element Relationships table. See: Collection Transactions and Context Element Relationships.
You can also add user-defined collection elements to these collection plans so that you can collect data that is not dependent on the transaction itself. See: Collection Elements and Defining Collection Elements.
To simplify the process of creating transfer and delivery collection plans, a template collection plan, Template PO Receiving, is pre-seeded in Oracle Quality. See: Creating Collection Plans from Templates .
You can copy the elements from the PO Receiving template collection plan to the transfer or delivery collection plan you have created to ensure that certain collection elements are included. Once copied over to your own collection plan, you can delete certain collection elements that are copied. You can also add user-defined collection elements to these collection plans.
You can specify actions specific to purchasing transactions in your collection plan. See: Application Specific Actions. However, when you are creating a collection plan for a receiving transfer or delivery, we suggest that you not include the Accept the Shipment or Reject the Shipment actions as these actions have no effect in a receiving transfer delivery.
In addition to these actions, you can add message actions, alert actions, and actions that determine a value based on a user-defined formula. See: Quality Actions, Message Actions, Alert Actions, and User-Defined Actions.
The Receiving Transaction collection transaction must be associated with the collection plans you use for receiving transactions. Also, Receiving Transactions collection plans used for Receiving Transfers or Receiving Deliveries must be enabled.
You can make the entry of quality data mandatory for the receiving transaction by setting its Mandatory option. If data entry is required, you cannot save the parent transaction, in this case the receiving transaction, without entering quality data. See Mandatory Data Collection.
You can also specify that data should be collected in the background. See: Background Data Collection.
You can define one or more collection triggers for each collection transaction. Collection triggers allow you to specify the conditions under which quality data collection is invoked as receiving transactions are entered. See: Quality Data Collection During Transactions and Associating Collection Plans with Transactions.