Backflush Component Lot and Revision Selection

Backflush Lot and Component Selection

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:
  • E: Error

  • S: Success

return_message OUT VARCHAR2 Error string the program returns.

Related Topics

Examples for Lot Selection Defaulting during Backflush Transactions

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

Manual Push Transactions

In this example, the Work in Process Parameter setup is:

Previous Backflush Transaction History, No Alternate Lot Selection Method

Previous Backflush Transaction History with Alternate Lot Selection Method

Alternate Lot Selection Method with No On-hand Lot Quantity

All Backflush Transactions Considered as Transaction History

Backflush History Does Not Span Across Jobs

Backflush Transaction History Includes Multiple Lots with On-hand Quantity

Component Revision Default During Backflush

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.

the picture is described in the document text