Search Results wip_leadtime_temp_pkg




Overview
Explore in AI Chat

Overview

The APPS.WIP_LEADTIME_TEMP_PKG package is a PL/SQL utility within the Oracle E-Business Suite Work in Process (WIP) module. Its principal business function is to compute and stage manufacturing lead time information for a routing into a temporary working table, and to subsequently clear that table when the data is no longer required. The package operates using AUTHID CURRENT_USER, meaning that its SQL statements execute with the privileges of the invoking session rather than the defining schema, a characteristic common to utility packages that must respect the caller's security context and organization (operating unit) access.

The package is closely associated with lead time calculation for discrete manufacturing routes, allowing the application to derive operation-level and cumulative lead times without committing the intermediate results permanently. The temporary staging approach isolates the calculation activity from base routing tables, supporting re-calculation, comparison, or display scenarios.

Key Procedures and Functions

  • WIP_POPULATE_LEADTIME_TEMP — The primary function of the package. It is invoked to populate lead time records into the temporary table based on a specific routing sequence. It accepts a routing sequence identifier and a debug level as inputs and returns a numeric status value. The debug parameter indicates the routine supports diagnostic tracing, typically enabling DBMS_OUTPUT messages at varying verbosity levels for troubleshooting.
  • WIP_DELETE_LEADTIME_TEMP — The companion cleanup function. It removes the rows previously staged in the temporary table, accepting a debug level and returning a numeric status. This routine ensures the staging area is cleared between successive calculations, preventing stale lead time data from contaminating subsequent runs.

Both functions return a number, conventionally interpreted as a success/failure or error code consistent with Oracle EBS API conventions. No additional documented procedures exist in this package.

Tables Accessed

Based on the ETRM metadata, the package reads and writes the following tables via APPS synonyms:

  • WIP_LEADTIME_TEMP — The temporary staging table. WIP_POPULATE_LEADTIME_TEMP inserts computed lead time rows here, and WIP_DELETE_LEADTIME_TEMP deletes them. This table serves as the working buffer for the calculation, keeping intermediate results separate from permanent routing data.
  • BOM_OPERATION_SEQUENCES — The source of routing operation definitions. The package reads operation sequence information (including the routing sequence identified by the input parameter) to determine which operations and associated attributes form the basis of the lead time computation. This is the Oracle Bills of Material table that stores the operation sequence segments which make up a routing.

The dependency on BOM_OPERATION_SEQUENCES confirms that the lead time determination is driven by the operation sequence structure of the routing, extracting sequence-level timing attributes to populate the temporary table.

Usage Notes

This package is an internal utility rather than a public, fully documented API; the ETRM classification for the object is OTHER, indicating it is not part of an officially supported public interface. It is referenced by zero other packages according to the metadata, suggesting its callers are application forms, concurrent programs, or internal form-level logic rather than other PL/SQL APIs.

Typical invocation follows a paired pattern: a caller first removes any residue with WIP_DELETE_LEADTIME_TEMP, then stages fresh data using WIP_POPULATE_LEADTIME_TEMP for the routing sequence of interest, reads the results, and finally cleans up. Because the package relies on AUTHID CURRENT_USER, invocation should occur from a session with valid APPS-level access and appropriate organization context.

In both EBS 12.1.1 and 12.2.2 the header revision indicates the source predates the R12 release (2003 timestamp), and it has remained stable across these releases. Because customizations invoking this package bypass supported public APIs, developers should treat it as subject to change and avoid direct dependency in custom code where an officially documented alternative lead time API exists.