Search Results insert_temp

Overview

WIP_LEADTIME_TEMP_PKG is a temporary staging package used within Oracle E-Business Suite manufacturing to populate and clean up the WIP_LEADTIME_TEMP table. This table is an intermediate workspace used during lead time calculation for a given routing. The package walks the operation network defined on a routing sequence, derives the sequence in which operations must be traversed (network order), and records that ordered result in WIP_LEADTIME_TEMP. Downstream lead time processing then consumes this ordered population to roll up cumulative lead times across operations without having to repeatedly resolve the routing network graph.

The package belongs to the APPS schema and is classified as OTHER in the ETRM metadata, meaning it is an internal helper package rather than a published, customer-facing API. It is referenced by no other packages, which underlines its role as a leaf-level utility invoked directly by the lead time calculation logic. The header identifies the source as wipltcab.pls, and the versioned comments reference defect fixes for bugs 5691032 and 5572730, indicating the package has been maintained to correct duplicate-row issues in routing network resolution.

Key Procedures and Functions

• WIP_POPULATE_LEADTIME_TEMP — Populates WIP_LEADTIME_TEMP for a routing sequence and returns a numeric status. Internally it identifies the root operation of the routing network (the operation that is never a "to" node in a transition), inserts that root into the temporary table, and then recurses through the network to insert each subsequent operation with an incrementing network order. A network_found flag is used to signal when no network exists for the routing sequence. Debug output is written to the concurrent program log when a debug level is supplied.
• WIP_DELETE_LEADTIME_TEMP — Removes rows previously staged in WIP_LEADTIME_TEMP. This companion procedure allows the temporary workspace to be reset between runs or after lead time processing completes, preventing stale ordering data from being reused.

The internal procedure insert_temp, visible in the source excerpt, is not documented as a separate ETRM procedure but is the private workhorse used by WIP_POPULATE_LEADTIME_TEMP to perform each row insert into WIP_LEADTIME_TEMP; the term "insert_temp" is therefore the recognizable internal anchor for this package's behavior.

Tables Accessed

• BOM_OPERATION_SEQUENCES — Read to obtain the distinct operation sequence numbers defined for the routing sequence that have a non-null implementation date. These represent the operations eligible for lead time placement.
• WIP_LEADTIME_TEMP — Written by the populate routine (routing_sequence_id, operation_seq_num, network_order) and cleaned by the delete routine. It serves as the ordered staging area for lead time computation.

The source also queries BOM_OPERATION_NETWORKS_V, the routing network view, to discover "from" and "to" operation relationships and locate the root node; this view is not listed among the documented APPS-synonym tables but is central to the traversal logic.

Usage Notes

WIP_LEADTIME_TEMP_PKG is an internal implementation package, not a formal public API. It is typically invoked by the lead time calculation routines that run as part of manufacturing planning and scheduling, and it may be called from custom code or concurrent programs that need to reconstruct routing network ordering. The populate function accepts a routing sequence identifier and a debug level, returning a status value; callers should invoke WIP_DELETE_LEADTIME_TEMP before repopulating to guarantee a clean workspace. Because the package writes to a temporary table scoped by routing_sequence_id, concurrent invocations for different routing sequences do not interfere, but the same routing sequence should not be processed simultaneously. The debug path writes diagnostic lines to the concurrent manager log through FND_FILE, which is useful when troubleshooting missing or duplicated operations on a routing.