Search Results wip_component_tbl_t




Overview
Explore in AI Chat

Overview

WIP_FLOWUTIL_PRIV is a private PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema that supports the Work in Process (WIP) flow manufacturing transaction infrastructure. Its principal responsibility is to derive, validate, and stage flow interface records for a given transaction header, and to explode bills of material into material requirement records. The package header comment describes its core purpose as deriving and validating flow interface records for a specified header identifier. The $Header line (wipfscms.pls 120.6.12000000.1, dated 2007/01/18) indicates this is a long-standing component of the WIP module rather than a recent addition.

The "PRIV" suffix identifies this as an internal implementation package. It is not intended as a public integration API; rather, it exists to service the WIP flow scheduling, material transaction interface, and work-orderless completion processes that drive flow manufacturing. The package is classified as OTHER in the ETRM metadata and is referenced by six other packages, confirming its role as a shared internal utility within the WIP dependency chain.

Key Procedures and Functions

The ETRM metadata documents twelve procedures and functions (12.2.2):

  • PROCESSFLOWINTERFACERECORDS — Derives and validates flow interface records for a given transaction header ID. This is the entry point into the core derivation logic.
  • EXPLODEREQUIREMENTSTOMTI — Explodes the BOM and inserts material requirements into the material transaction interface (MTI) table under a given header and parent ID. Where supply subinventory and locator are absent from the BOM, it defaults them using the rule: BOM level, then item level, then WIP parameter.
  • CREATEFLOWSCHEDULE — Creates entries in WIP_FLOW_SCHEDULES and WIP_ENTITIES for unscheduled work-orderless completion, which are required for subsequent resource and material transactions. Can be driven from either the MTI or the MMTT.
  • UPDATEFLOWSCHEDULE — Maintains existing flow schedule records in support of the transaction lifecycle.
  • SETMMTTERROR — Records error conditions against material transaction temporary records.
  • EXPLODEREQUIREMENTSANDDEFAULT — Combines requirement explosion with defaulting logic for supply subinventory and locator.
  • EXPLODEREQUIREMENTSTOMMTT — Explodes BOM requirements into material transaction temporary records.
  • CONSTRUCTWIPLINEOPS — Constructs WIP line operation records associated with flow transactions.
  • EVENTINPRIORSAMELINEOP — Determines event positioning relative to a prior operation on the same line.
  • GETTYPEFROMACTION — Derives a transaction or line type from an action code.
  • GETCHILDTXN — Resolves child transaction relationships for a given parent transaction.
  • GENERATECOMPLOCATOR — Generates completion locator values used during flow completion processing.

Tables Accessed

The package reads and writes a defined set of WIP, inventory, and BOM tables through APPS synonyms. BOM_OPERATIONAL_ROUTINGS and BOM_OPERATION_SEQUENCES supply routing and operation sequence data required for line operation construction. MTL_SYSTEM_ITEMS, MTL_ITEM_LOCATIONS, and MTL_PARAMETERS provide item, locator, and organization-level defaulting information. MTL_TRANSACTIONS_INTERFACE is the primary target for exploded material requirements, with MTL_MATERIAL_TRANSACTIONS_TEMP and MTL_MATERIAL_TRANSACTIONS_S holding temporary and staged transaction rows. WIP_ENTITIES_S and WIP_FLOW_SCHEDULES receive the flow schedule and entity records created for work-orderless completions. WIP_ACCOUNTING_CLASSES and WIP_PARAMETERS supply accounting class and WIP defaulting rules. DUAL and PLITBLM are used for standard expression evaluation and PL/SQL table handling.

Usage Notes

WIP_FLOWUTIL_PRIV is invoked internally by WIP flow transaction processing, including the flow scheduling and material transaction interface logic exposed through the WIP transaction forms and related concurrent programs. Because it is a private package, it should not be called directly from customer extensions where a supported public API exists; however, the derived MTI and WIP_FLOW_SCHEDULES records it produces are the substrate on which flow completion, resource, and material transactions depend. The parameter lists exposed in the source excerpt (for example, EXPLODEREQUIREMENTSTOMTI carries fix references including bug#5262858 and bug#5630078) confirm that the package has been patched repeatedly to address edge cases in subinventory defaulting and non-transaction exclusion. Custom developers encountering this package are typically tracing why material requirements were not staged into MTL_TRANSACTIONS_INTERFACE or why a flow schedule was not created for an unscheduled completion. In such cases the relevant procedures are EXPLODEREQUIREMENTSTOMTI, EXPLODEREQUIREMENTSTOMMTT, and CREATEFLOWSCHEDULE, and the primary diagnostic tables are MTL_TRANSACTIONS_INTERFACE and WIP_FLOW_SCHEDULES. The term "home tap saved folio request," from the originating search, does not correspond to any object or procedure within this package; it appears to be an unrelated query string.