Search Results mtl_transaction_type

Overview

WIP_POPULATE_TEMP is a Work in Process (WIP) package body in the Oracle E-Business Suite Applications schema. Its business purpose is to stage material transaction records for WIP manufacturing activity prior to committing them to the transaction interface and eventually to the inventory transaction tables. The package inserts rows into the temporary transaction table, resolving item, locator, subinventory, unit of measure, and transaction type attributes for a discrete job or repetitive schedule operation. It is a supporting utility within the WIP transaction processing flow, invoked during component issue, assembly completion, and related shop-floor transactions. The user search term "mtl_transaction_type" is relevant because INSERT_TEMP accepts a transaction type identifier and the package reads the MTL_TRANSACTION_TYPES table to determine validation logic and attribute defaults for the staged transaction.

Key Procedures and Functions

• INSERT_TEMP — The sole documented procedure in the package. It accepts parameters describing the transaction context, including the transaction mode, WIP entity identifier, line identifier, transaction date, transaction type identifier, transaction action identifier, subinventory, locator, assembly quantity, operation sequence number, department, organization, accounting period, entity type, calendar code, exception set, and transaction header identifier. The procedure returns a commit counter as an OUT parameter, which callers use to drive periodic commits during bulk transaction staging. Internally, INSERT_TEMP resolves the transaction source type and source identifier, validates locator and subinventory control flags, computes the component transaction quantity through the WIP_COMPONENT.Determine_Txn_Quantity logic (including component yield handling introduced by the Component Yield enhancement), and applies inventory precision rounding before inserting into the temporary table.

Tables Accessed

• MTL_MATERIAL_TRANSACTIONS_TEMP — The primary insert target; rows staged here are subsequently processed by the transaction manager.
• MTL_TRANSACTION_TYPES — Consulted to validate the supplied transaction type and derive transaction source and action semantics.
• MTL_SYSTEM_ITEMS — Used to validate the item and retrieve item attributes required for the transaction.
• MTL_ITEM_LOCATIONS — Accessed to validate the locator and to resolve locator segments and locator control status.
• MTL_SECONDARY_INVENTORIES — Used to validate the subinventory and confirm it is valid for the organization.
• MTL_PARAMETERS — Read for organization-level defaults such as locator control and inventory precision.
• MTL_UNITS_OF_MEASURE — Consulted for unit of measure validation and conversion context.
• WIP_DISCRETE_JOBS and WIP_REPETITIVE_SCHEDULES — Source of job or schedule attributes, including assembly quantity and calendar information.
• WIP_REQUIREMENT_OPERATIONS — Provides the component requirements and operation sequence detail that drive the computed transaction quantity.
• WIP_PARAMETERS — Supplies WIP module defaults, including commit behavior.
• BOM_DEPARTMENTS and BOM_CALENDAR_DATES — Validate the department and resolve repetitive scheduling dates and calendar codes.

Usage Notes

WIP_POPULATE_TEMP is not an end-user API and is not designed as a public integration point. It is invoked internally by WIP transaction processing logic, typically from WIP component issue and assembly completion flows initiated through the Work In Process forms, the WIP Material Transactions window, or Mobile Supply Chain Applications. Custom code should not call INSERT_TEMP directly; instead, extensions should use the supported WIP transaction APIs or the inventory transaction interface. Because the package writes to MTL_MATERIAL_TRANSACTIONS_TEMP, callers must ensure that staged rows are subsequently processed by the standard transaction manager, and they should honor the commit counter returned by INSERT_TEMP to manage transaction sizing. The package is documented as referenced by zero other packages, confirming its role as a downstream helper rather than a shared entry point.