The Move - Backflush Component Lot Selection client extension enables custom logic to derive the component lot numbers for backflush transactions during move, and move and complete transactions when using the Express Transact Components page. If the program does not return a value, the logic derives the lot number.
A PL/SQL package: WIP_WS_CUSTOM, contains the custom programming instructions invoked.
Procedure: LOT_HOOK
Parameter | IN/OUT | Type | Description |
---|---|---|---|
org_id | IN | NUMBER | Identification of the organization. |
wip_entity_id | IN | NUMBER | WIP entity identification of the job. |
operation_seq_num | IN | NUMBER | Operation sequence number of the operation. |
repetitive_schedule_id | IN | NUMBER | Identification of the repetitive schedule. |
inventory_item_id | IN | NUMBER | Identification of the component. |
supply_subinv | IN | VARCHAR2 | Supply subinventory. |
supply_locator_id | IN | NUMBER | Supply locator. |
revision | IN | VARCHAR2 | Revision of the assembly. |
primary_qty | IN | NUMBER | Quantity moved. |
lot_number | IN OUT | VARCHAR2 | Lot number derived by the program. |
return_status | OUT | VARCHAR2 | Value indicating performance status, choices are:
|
return_message | OUT | VARCHAR2 | Error string the program returns. |
Related Topics
Examples for Lot Selection Defaulting during Backflush Transactions
When there are multiple backflush transactions for the same component, on the same job—you can set the selection method for defaulting lot numbers used in the previous transactions. The following examples demonstrate how transactions and parameter setup determine the lot selection. See: Material Parameters
No Existing Previous Backflush Transactions
Lots cannot be derived because there is no backflush transaction history
Lot Selection Method—Transaction History
Alternate Lot Selection Method—Receipt Date
JobA is created to create AssemblyA with the following bill of material:
Operation Sequence | Component | Supply Type | Assembly Quantity |
---|---|---|---|
10 | A123 | operation pull | 1 |
20 | B345 | operation pull | 1 |
30 | A123 | push | 1 |
40 | B345 | assembly pull | 1 |
On-hand quantity for the following lot receipt dates:
Receipt Date | Component | Quantity | Lot |
---|---|---|---|
Day 1 | A123 | 10 | A |
Day 1 | B345 | 2 | A |
Day 2 | A123 | 5 | B |
Day 4 | B345 | 20 | B |
Day 5 | A123 | 8 | C |
When a quantity of 2 is moved from 10 Queue to 30 Queue:
Two each of A123, and two each of B345 are backflushed.
Since there is no previous backflush transaction, Lot A is defaulted based on receipt date for both components.
Manual Push Transactions
In this example, the Work in Process Parameter setup is:
Lots cannot be derived because default logic does not apply to manual push transactions
Lot Selection Method—Manual
The current backflush transaction history:
Transaction Reference | Component | Quantity | Lot | Transaction Type |
---|---|---|---|---|
JobA | A123 | 2 | A | Operation Backflush |
JobA | B345 | 2 | A | Operation Backflush |
On-hand quantity for the following lot receipt dates:
Receipt Date | Component | Quantity | Lot |
---|---|---|---|
Day 1 | A123 | 8 | A |
Day 1 | B345 | 0 | A |
Day 2 | A123 | 5 | B |
Day 4 | B345 | 20 | B |
Day 5 | A123 | 8 | C |
A quantity of three A123 is manually pushed from Lot C into the job to fulfill Operation 30 requirements—default logic does not apply to manual push transactions.
Previous Backflush Transaction History, No Alternate Lot Selection Method
Lot Selection Method—Transaction History
Alternate Lot Selection Method—Null
The current backflush transaction history:
Transaction Reference | Component | Quantity | Lot | Transaction Type |
---|---|---|---|---|
JobA | A123 | 2 | A | Operation Backflush |
JobA | B345 | 2 | A | Operation Backflush |
JobA | A123 | 3 | C | Manual Push |
On-hand quantity for the following lot receipt dates:
Receipt Date | Component | Quantity | Lot |
---|---|---|---|
Day 1 | A123 | 8 | A |
Day 1 | B345 | 0 | A |
Day 2 | A123 | 5 | B |
Day 4 | B345 | 20 | B |
Day 5 | A123 | 5 | C |
When a quantity of 4 is moved from 10 Queue to 10 To Move:
Four each of A123 are backflushed.
The lots are defaulted from the last backflush transaction, so Lot A is defaulted based on receipt date for the component.
Previous Backflush Transaction History with Alternate Lot Selection Method
Lot Selection Method—Transaction History
Alternate Lot Selection Method
The current backflush transaction history:
Transaction Reference | Component | Quantity | Lot | Transaction Type |
---|---|---|---|---|
JobA | A123 | 2 | A | Operation Backflush |
JobA | B345 | 2 | A | Operation Backflush |
JobA | A123 | 3 | C | Manual Push |
JobA | A123 | 4 | A | Operation Backflush |
When a quantity of 5 is moved from 10 Queue to 20 Queue:
The lot is defaulted from the last backflush transaction, if there is existing on-hand quantity in the lot.
Five each of A123 are backflushed, however only a default quantity of 4 is displayed in the Backflush window.
For the remaining quantity of 1, Lot B also displays as a quantity of 1 in the Backflush window.
Alternate Lot Selection Method with No On-hand Lot Quantity
Lot Selection Method—Transaction History
Alternate Lot Selection Method—Receipt Date
The current backflush transaction history:
Transaction Reference | Component | Quantity | Lot | Transaction Type |
---|---|---|---|---|
JobA | A123 | 2 | A | Operation Backflush |
JobA | B345 | 2 | A | Operation Backflush |
JobA | A123 | 3 | C | Manual Push |
JobA | A123 | 4 | A | Operation Backflush |
JobA | A123 | 4 | A | Operation Backflush |
JobA | A123 | 1 | B | Operation Backflush |
On-hand quantity for the following lot receipt dates:
Receipt Date | Component | Quantity | Lot |
---|---|---|---|
Day 1 | A123 | 0 | A |
Day 1 | B345 | 0 | A |
Day 2 | A123 | 4 | B |
Day 4 | B345 | 20 | B |
Day 5 | A123 | 5 | C |
When a quantity of 1 is moved from 20 Queue to 20 To Move:
One B345 is backflushed.
Lot A defaulted would be used as the default, however it contains 0 on-hand quantity.
The system considers the previous backflush transaction receipt date, and uses Lot B for the current backflush transaction.
All Backflush Transactions Considered as Transaction History
This includes assembly pull and operation pull
Lot Selection Method—Transaction History
Alternate Lot Selection Method—Receipt Date
The current backflush transaction history:
Transaction Reference | Component | Quantity | Lot | Transaction Type |
---|---|---|---|---|
JobA | A123 | 2 | A | Operation Backflush |
JobA | B345 | 2 | A | Operation Backflush |
JobA | A123 | 3 | C | Manual Push |
JobA | A123 | 4 | A | Operation Backflush |
JobA | A123 | 4 | A | Operation Backflush |
JobA | A123 | 1 | B | Operation Backflush |
JobA | B345 | 1 | B | Operation Backflush |
On-hand quantity for the following lot receipt dates:
Receipt Date | Component | Quantity | Lot |
---|---|---|---|
Day 1 | A123 | 0 | A |
Day 1 | B345 | 0 | A |
Day 2 | A123 | 4 | B |
Day 4 | B345 | 19 | B |
Day 5 | A123 | 5 | C |
When a quantity of 1 is completed
One of B345 is backflushed at Operation 40
Transaction history determines that Lot B is defaulted
Backflush History Does Not Span Across Jobs
Lot Selection Method—Transaction History
Alternate Lot Selection Method—Receipt Date
The current backflush transaction history:
Transaction Reference | Component | Quantity | Lot | Transaction Type |
---|---|---|---|---|
JobA | A123 | 2 | A | Operation Backflush |
JobA | B345 | 2 | A | Operation Backflush |
JobA | A123 | 3 | C | Manual Push |
JobA | A123 | 4 | A | Operation Backflush |
JobA | A123 | 4 | A | Operation Backflush |
JobA | B345 | 1 | B | Operation Backflush |
JobA | B345 | 1 | B | Assembly Backflush |
On-hand quantity for the following lot receipt dates:
Receipt Date | Component | Quantity | Lot |
---|---|---|---|
Day 1 | A123 | 0 | A |
Day 1 | B345 | 0 | A |
Day 2 | A123 | 4 | B |
Day 4 | B345 | 18 | B |
Day 5 | A123 | 4 | C |
Another job, JobB, has a quantity of 3 moved from 10 Queue to 10 To Move:
Three each of A123 are backflushed.
Transaction history does not exist for this job.
Alternate Lot Selection Method parameter determines that the quantity is defaulted from Lot B. You can override this default with a manual entry.
Backflush Transaction History Includes Multiple Lots with On-hand Quantity
Lot Selection Method—Transaction History
Alternate Lot Selection Method—Receipt Date
The current backflush transaction history:
Transaction Reference | Component | Quantity | Lot | Transaction Type |
---|---|---|---|---|
JobA | A123 | 2 | A | Operation Backflush |
JobA | B345 | 2 | A | Operation Backflush |
JobA | A123 | 3 | C | Manual Push |
JobA | A123 | 4 | A | Operation Backflush |
JobA | A123 | 4 | A | Operation Backflush |
JobA | A123 | 1 | B | Operation Backflush |
JobA | B345 | 1 | B | Operation Backflush |
JobA | B345 | 1 | B | Assembly Backflush |
JobB | A123 | 2 | B | Operation Backflush |
JobB | A123 | 1 | C | Operation Backflush |
On-hand quantity for the following lot receipt dates:
Receipt Date | Component | Quantity | Lot |
---|---|---|---|
Day 1 | A123 | 0 | A |
Day 1 | B345 | 0 | A |
Day 2 | A123 | 2 | B |
Day 4 | B345 | 18 | B |
Day 5 | A123 | 3 | C |
JobB has a quantity of 2 moved from 10 Queue to 10 To Move:
Two each of A123 are backflushed.
In the transaction history, Lot B and Lot C were the last transactions.
Both lots have on-hand quantity—lot default is then based on the lot number in numerical sequence. Therefore, Lot B is defaulted. Lot C is only used if there is not sufficient quantity in Lot B.
The following procedure contains the file of wipwsctb.pls to provide the client extension to default the component revision during backflush moves. You can insert your revision change code in this program.