You can do all of the following on the Work Order-less Completions window:
Complete unscheduled or scheduled assemblies to Inventory
Return unscheduled or scheduled assemblies from Inventory
Scrap assemblies from and return scrapped assemblies to any operation
Explode the assembly's bill of material and add, delete, and change components-and review items under lot and serial number control
Specify lot, serial, and lot and serial information for assemblies and components.
Create material reservations for assemblies that are linked to sales orders
Replenish production kanbans
If Oracle Mobile Supply Chain Applications is installed, you can use a mobile client device networked with a computer system to complete or return unscheduled and scheduled assemblies to inventory, and return unscheduled assemblies. See: Work Order-Less Transactions, Oracle Mobile Supply Chain Applications User's Guide.
If Oracle Warehouse Management is installed, you can perform work order-less completions into license plate numbers (LPN). License plate numbers are identifiers for tracking both inbound and outbound material - providing genealogy and transaction history for each license plate. For work order-less return transactions, you must first unpack the LPN before performing the assembly return transaction See: Explaining License Plate Management
When you complete assemblies in this window, components are automatically backflushed. Resources that are specified as item based, when you perform return transactions all resource charges are reversed. For lot based resources, return transactions do not reverse charges.
When adding a component through the Material Transaction interface, with an operation sequence that does not exist on the routing, the backflush transaction is still processed with the invalid operation sequence.
Backflush completions for components under lot number control can be identified manually or automatically depending on how the WIP Backflush Lot Selection Method parameter is set.
For backflush components under serial, or lot and serial control, you can manually identify which lot and serial number combinations to backflush using the Lot/Serial action in the Components window. If you return assemblies using this window, you must always identify the lot, serial, and lot or serial numbers of the components being returned to inventory.
See: Lot and Serial Backflushing and Material Parameters.
On the Routings window in Oracle Bills of Material, in the WIP tabbed region-the Count Point and Autocharge flags are enabled and not modifiable. Therefore, resources are set up to be charged.
If an operation and event combination is disabled, the resources linked to those departments are not charged. However, components tied to those operations and events are backflushed.
If the event is not assigned to a line operation, the resource and material associated with that operation is charged when performing completion and scrap transactions.
When performing scrap transactions, all components are backflushed in the line operations prior to, and including, the line operation scrapped.
For component quantity changes using desktop assembly completions - the Backflush window displays for component information for supply type Push, and Pull components requiring additional information such as lot or serial number. You can change the transaction quantity when the Work in Process parameter, Allow Quantity Changes During Backflush, is enabled. For Mobile Applications work orderless completions, Pull components requiring additional information can also be over or under issued when this parameter enabled. See: Material Parameters
If Oracle Quality is installed and at least one qualified collection plan exists, both the Enter Quality Results option on the Tools menu and the Quality button on the toolbar are enabled. When mandatory collection plans are used, quality results data must be entered and saved before you can save your transaction. See: Using Oracle Quality with Oracle Work in Process.
Sales order line information defaults only for open and active sales order statuses. Otherwise the Sales Order field is null on the Work Order-less Completions window. The following information applies to sales order defaults on this window:
Sales order information does not default if the original sales order line associated with the Flow schedule is cancelled or closed.
You can create reservations for assemblies linked to sales orders.
When completing unscheduled assemblies, you can select sales orders that are open for standard items or configured items in at least one of the order lines.
Sales order lines selected should not be linked to a discrete job.
If the sales order has been split into several sales order lines, the new lines do not display on the Work Order-less Completions window.
If the sales order has been split into new sales order lines, and only one order line is valid, that new line displays on the Work Order-less Completions window.
For Flow schedules with sales order reservations, you can reserve overcompletion quantities. This is set in the item master attributes for the following values:
Overcompletion Tolerance Type and Overcompletion Tolerance Value in the Work In Process Attribute Group
Over Shipment Tolerance in the Order Management Attribute Group
If the overcompletion quantity is within the over shipment tolerance value, the quantity is reserved to the sales order within that tolerance amount.
For a serialized item returned to stock, validations occur to prevent re-issuing to a different flow schedule. At the time of completion, serialized assemblies and components for flow schedules are available from stock if they have the following values set in the Serial Numbers window in Oracle Inventory:
Flow Schedule Work Order-less Completions
State value: Defined but not used.
State value: Issued out of stores. This is restricted to serial numbers that were previously returned to the same flow schedule that you are completing.
Unscheduled Work Order-less Completions
State value: Defined but not used.
State value: Issued out of stores. This is restricted to serial numbers that were previously transacted for an unscheduled work order-less return.
Maintaining Serial Number Information
See: Serial Number Validations for Component Returns and Assembly Completions
The following table lists the fields that cannot be updated in the Work Order-less Completions window:
| WIP Assembly Completion | WIP Assembly Return | Scrap | Return from Scrap | |
|---|---|---|---|---|
| Unscheduled Assemblies | Build Sequence | Build Sequence | Build Sequence, Subinventory/Locator, Lot/Serial button | Build Sequence, Subinventory/Locator, Lot/Serial button |
| Scheduled Flow Schedule | Assembly, Line, Schedule Group, Build Sequence, Schedule Number, Accounting Class, Project/Task | Assembly, Line, Schedule Group, Build Sequence, Schedule Number, Accounting Class, Project/Task | Assembly, Line, Schedule Group, Build Sequence, Schedule Number, Accounting Class, Project/Task, Subinventory/Locator, Lot/Serial button | Assembly, Line, Schedule Group, Build Sequence, Schedule Number, Accounting Class, Project/Task, Subinventory/Locator, Lot/Serial button |
| Unscheduled Assemblies with a Kanban Reference | Build Sequence, Subinventory/Locator | DISALLOWED | DISALLOWED | DISALLOWED |
| Scheduled Flow Schedule with a Kanban | Build Sequence, Subinventory/Locator | DISALLOWED | DISALLOWED | DISALLOWED |
| Unscheduled Assemblies with a Sales Order Reference | Build Sequence | DISALLOWED | Build Sequence, Subinventory/Locator, Lot/Serial button | Build Sequence, Subinventory/Locator, Lot/Serial button |
| Scheduled Flow Schedule with a Sales Order Reference | Build Sequence | Assembly, Line, Schedule Group, Build Sequence, Schedule Number, Accounting Class, Project/Task, Subinventory/Locator, Lot/Serial button | Assembly, Line, Schedule Group, Build Sequence, Schedule Number, Accounting Class, Project/Task, Subinventory/Locator, Lot/Serial button | Assembly, Line, Schedule Group, Build Sequence, Schedule Number, Accounting Class, Project/Task, Subinventory/Locator, Lot/Serial button |
| WIP assembly completion | Receive completed assemblies into inventory. If backflush components are under lot or serial number control, the lots and serial control numbers to backflush must be identified. Lots for backflush components under lot number control can be identified manually or automatically based on how the WIP Backflush Lot Selection parameter is set. See: Material Parameters. For backflush components under serial number control or manual lot control, you must manually identify which serial numbers or lot numbers to backflush using the lot/serial number action in the Components window. |
| WIP assembly return | Return assemblies from inventory. All operation pull, assembly pull and push components are automatically returned to inventory. If the returned components are under lot or serial number control, the lots and serial numbers to return must be identified using the Lot/Serial action in the Components window. |
| WIP scrap transactions | Scrap assemblies at any operation. You can scrap assemblies even if the assembly does not have a routing. When this is done, the Scrap Operation defaults to 1. All operation pull, assembly pull and push components are backflushed when a flow schedule assembly is scrapped. If the WIP Require Scrap Account parameter is set to Yes, and a scrap account is entered, the system debits this account and credits the elemental accounts associated with the flow schedule through the operation at which the assemblies are scrapped. Resource and overhead cost elements at scrap operations that are non-autocharge operations are also charged. However resource and overhead cost elements at the non-autocharge operations prior to the scrap operation are not charged. If you do not provide a scrap account, the cost of scrap remains in the flow schedule until job or period close and is then written off as a variance. You must enter a scrap account if the Require Scrap Account parameter is enabled. See: Move Transaction Parameters. |
| WIP return from scrap | Return assemblies from scrap. If you enter a reversing scrap transaction, the system credits this account and debits the job or schedule elemental accounts through the operation at which the assemblies are returned. |