Search Results maximum_load_weight




Overview
Explore in AI Chat

Overview

INV_ITEM_TEMP is a transient staging table residing in the INV (Inventory) schema of Oracle E-Business Suite. It is used by the item import and interface processing framework to hold item master attribute data in a temporary form before validation and insertion into the permanent item definition tables. The table carries 279 documented columns, reflecting the breadth of the MTL_SYSTEM_ITEMS_B item attribute model, which it mirrors almost column for column. Records are keyed by TRANSACTION_ID and grouped by TRANSACTION_GROUP_ID, supporting set-based processing of bulk item loads submitted through the Item Import concurrent program.

From a Data Vault modeling perspective, the ETRM heuristic classifies this object as standalone, meaning it participates in no formal hub, link, or satellite dependencies within the mined constraint structure. This classification is consistent with its role as an ephemeral work table rather than a durable master or transactional entity. Because rows are consumed and typically purged once the import completes, the table should not be treated as a system of record for item data.

Key Information Stored

The principal identifier is TRANSACTION_ID, which serves as the surrogate key for each staged row. TRANSACTION_GROUP_ID associates related rows into a single import batch, and DELETE_GROUP_NAME provides batch-level identification for purge operations. ORGANIZATION_ID and ORGANIZATION_CODE identify the target inventory organization, while INVENTORY_ITEM_ID and ITEM_NUMBER identify the item being created or updated. The twenty SEGMENT1 through SEGMENT20 columns hold the concatenated item key flexfield values that ultimately form the item's business identifier in MTL_SYSTEM_ITEMS_B.

Control attributes that determine processing behavior include SUMMARY_FLAG, ENABLED_FLAG, START_DATE_ACTIVE, END_DATE_ACTIVE, and ITEM_TYPE. Descriptive and unit data reside in DESCRIPTION, LONG_DESCRIPTION, PRIMARY_UOM_CODE, and PRIMARY_UNIT_OF_MEASURE. Three foreign keys anchor the staging row to reference data: ITEM_CATALOG_GROUP_ID references MTL_ITEM_CATALOG_GROUPS_B, UN_NUMBER_ID references PO_UN_NUMBERS_B, and HAZARD_CLASS_ID references PO_HAZARD_CLASSES_B. Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) plus the concurrent program columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) allow audit and traceability of each import run. Both ATTRIBUTE1–15 and GLOBAL_ATTRIBUTE1–10 flexible attribute sets are present to carry customer-specific descriptive data through the interface.

Common Use Cases and Queries

The table is most frequently queried during troubleshooting of Item Import failures. A typical diagnostic pattern isolates rows from a specific concurrent request and inspects their processing state:

  • SELECT TRANSACTION_ID, TRANSACTION_GROUP_ID, ITEM_NUMBER, ORGANIZATION_CODE, DESCRIPTION, PRIMARY_UOM_CODE FROM INV.INV_ITEM_TEMP WHERE REQUEST_ID = :request_id;
  • Counting staged rows per organization to verify load completeness: SELECT ORGANIZATION_CODE, COUNT(*) FROM INV.INV_ITEM_TEMP GROUP BY ORGANIZATION_CODE;
  • Pre-import validation of required flexfield segments: SELECT ITEM_NUMBER FROM INV.INV_ITEM_TEMP WHERE SEGMENT1 IS NULL OR PRIMARY_UOM_CODE IS NULL;

Reporting use cases include reconciliation of submitted item counts against successfully imported MTL_SYSTEM_ITEMS_B rows, auditing custom ATTRIBUTE columns carried through the interface, and verifying that catalog group, UN number, and hazard class references resolve to valid parent records before commit.

Related Objects

INV_ITEM_TEMP is tightly coupled to the item master and its import infrastructure. In addition to the three referenced foreign key tables, the most significant related objects are:

  • MTL_SYSTEM_ITEMS_B / MTL_SYSTEM_ITEMS_TL — the permanent item master that receives validated rows.
  • MTL_ITEM_CATALOG_GROUPS_B — joined via ITEM_CATALOG_GROUP_ID.
  • PO_UN_NUMBERS_B — joined via UN_NUMBER_ID.
  • PO_HAZARD_CLASSES_B — joined via HAZARD_CLASS_ID.
  • MTL_ITEM_IMPORT_INTERFACE — the primary external interface table feeding item creation logic.
  • FND_CONCURRENT_REQUESTS — joined via REQUEST_ID for concurrent program tracing.
  • The Item Import concurrent program (INCOIN) and the MTL_SYSTEM_ITEMS_PUB / INV_ITEM_PUB APIs that consume staged data.