The Material Pickwave process includes the following steps:
Pick Release (Oracle Shipping Execution procedure
For information about Oracle Shipping Execution's pick release procedure, see: Overview of Pick Release and Releasing Sales Orders for Picking in Oracle Shipping Execution User's Guide.
Move Order Line Allocation
Oracle Shipping Execution's pick release procedure creates move order lines. In order to release those lines to the warehouse and print pick slips, the lines must be allocated. The process by which the Oracle Inventory picking engine generates transaction line suggestions is called allocation. The allocation process for a pick wave move order line also creates a high-level (organization-wide) reservation on the material if no reservations previously existed.
You can choose to have the system automatically allocate move order lines, or you can postpone this step and manually allocate the move order lines at a later time. In either case, pick release creates move orders in an approved status, so that no additional approval process is required in order to transact them. Postponing the allocating process can be useful to organizations that pick release across multiple warehouses but prefer to allow each warehouse to determine when to release its order lines to the floor. You use a shipping parameter in Oracle Shipping Execution to specify whether the allocating process is automatic or manual. See: Setting Up Shipping Parameters, Oracle Shipping Execution User's Guide.
You can override this default parameter at each pick release. See: Releasing Sales Orders for Picking, .
If you choose to postpone the allocation process and perform these steps manually, you use an Oracle Inventory procedure. However you postpone the allocation, the inventory allocation rules are still used when the moved order is allocated in the Transact Move Order from. for Pick Wave Move Orders, you cannot manually enter all the allocation details, but you can update certain attributes of the allocation that the system provides. See: Manually Allocating Pick Wave Move Orders.
Note: If the item and source subinventory are reservable and no reservation existed for the sales order prior to pick release, the allocation process will create a high-level (organization level) reservation on the material to be picked.
Move Order Line Pick Confirmation
The move order line allocations (transaction lines) created by the allocation process must be transacted to confirm the material drop-off in staging. This process is called pick confirmation. Pick confirmation executes the subinventory transfer that moves the material from its source location in the warehouse into the staging location. Pick confirmation automatically transfers any existing reservation to an allocated reservation (including lots, revision, subinventory, and locators) in the staging location. At pick confirmation, you can report a missing quantity or change the transaction line if the picker chooses to use material from a different lot, serial, locator, or subinventory. If an organization's picks rarely deviate from the suggested picking lines and the overhead of requiring a pick confirmation is unmanageable, the pick confirm transactions can occur automatically, immediately after the lines are allocated.
You use an Oracle Inventory parameter to specify whether pick confirmation occurs automatically or whether you want your picker to pick confirm move order lines manually. See: Defining ATP, Pick, Item-Sourcing Parameters.
You can override this default parameter at each pick release. See: Releasing Sales Orders for Picking, .
Note: If the organization is enabled for Oracle Warehouse Management, then move orders cannot be transacted on the desktop Transact Move Orders form. Rather, the move orders are transacted as tasks on mobile devices. However, the Transact Move Order from can be use to view the allocations, so long as LPNs have not been allocated. The allocations can still be manually updated from this form, but the Transact button is not available for move orders in a WMS enabled organization.
To pick confirm move order lines manually, you use Oracle Inventory's Transact Move Orders window. You use the same procedure as you do to transact move order requisitions and replenishment move orders. The manual pick confirm option allows you to transact each move order line or move order line allocation individually. This allows you to confirm the transaction of each pick. When you manually pick confirm (transact), you can update any pick details that were different from the suggestions generated by the system, including lot, serial number, and locator information. See: Transacting Move Orders.
Move orders can be over pick confirmed, within the shipping tolerances for the customer, in an Inventory organization. The operator can transact more than the requested quantity, adding additional lots and or serials as required.
If you use the automatic pick confirm process, the material is only transacted to the staging subinventory and reserved. You can still manage any discrepancies found by deleting the reservation and transacting the material back to its original subinventory. If you use mobile devices such as bar code scanners to perform inventory transactions, it is suggested that you use manual pick confirmation for greatest inventory accuracy and control. If you used the automatic pick confirm process, the the move order is not visible in the Transact Move Order form.
Note: Non-reservable items are always automatically pick confirmed, regardless of whether pick confirmation is required for the batch. If the item should be manually pick confirmed, then make the item reservable.
Ship Confirmation (Oracle Shipping Execution Procedure
You can customize the process by deciding when you want to allocate and pick confirm move order lines. See: Overview of Ship Confirm.