Results for “xml_document_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The WSM_STARTING_LOTS_INTERFACE table is an Oracle E-Business Suite interface (staging) table owned by the WSM (Shop Floor Management) schema. It serves as the child table to WSM_LOT_SPLIT_MERGES_INTERFACE and holds the "starting lot" records associated with an inbound Inventory Lot Transaction import. In discrete manufacturing and shop floor execution, lot split and merge operations require the system to know not only the resulting lot state but also the originating (starting) lot composition — quantity, item, subinventory, and locator. This table captures that starting-lot detail before the parent interface process validates and posts the transaction into the destination inventory tables.

Because it is an interface table, its rows are transient: they are populated by an external or concurrent import process, consumed and validated by an interface/import program, and are not part of the permanent transactional record. Records that pass validation flow into the destination inventory transaction tables; records that fail remain for correction and reprocessing. The table is registered as VALID in the WSM schema across both 12.1.1 and 12.2.2, and the documented physical schema shows 37 columns in the 12.2.2 ETRM repository.

Applying a heuristic Data Vault classification to the documented foreign key and key structure, this object most closely resembles a link table. It resolves associations between a parent interface header (WSM_LOT_SPLIT_MERGES_INTERFACE), an inventory item/organization context, a locator, and a subinventory — rather than representing a standalone business entity (hub) or a descriptive change-over-time record (satellite). This classification should be treated as a modeling suggestion only.

Key Information Stored

The documented primary key is the unique constraint WSM_STARTING_LOTS_INTERFAC_UK on the composite of HEADER_ID and LOT_NUMBER. The repository also documents a unique index WSM_STARTING_LOTS_IFC_U1 on the same two columns (HEADER_ID, LOT_NUMBER), meaning the business key and the surrogate uniqueness constraint coincide here. The most operationally significant columns are:

• HEADER_ID — Foreign key to WSM_LOT_SPLIT_MERGES_INTERFACE; identifies the parent import transaction. Part of the composite primary key.
• LOT_NUMBER — The starting lot being referenced. Part of the composite primary key.
• INVENTORY_ITEM_ID — The inventory item associated with the starting lot.
• ORGANIZATION_ID — The inventory organization context; also a foreign key to WSM_PARAMETERS.
• QUANTITY — Quantity of the starting lot involved in the transaction.
• SUBINVENTORY_CODE — Foreign key to MTL_SECONDARY_INVENTORIES.
• LOCATOR_ID — Foreign key to MTL_ITEM_LOCATIONS; the physical locator of the starting lot.
• REVISION — Item revision for the starting lot, where revision control applies.
• TRANSACTION_ID — Correlation identifier linking the staging row to a source or destination transaction.
• COMPONENT_ISSUE_QUANTITY — Quantity issued at the component level, relevant to split/merge component consumption.
• REPRESENTATIVE_FLAG — Indicator used in lot representative/grouping logic.
• XML_DOCUMENT_ID — Reference to the XML payload or document used for external import scenarios.
• GROUP OF ATTRIBUTE1–ATTRIBUTE15 and ATTRIBUTE_CATEGORY — Descriptive flexfield columns available for extensibility.
• WHO/audit and program columns — LAST_UPDATE_DATE, CREATED_BY, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE, which record which concurrent request and program wrote the interface row.

Common Use Cases and Queries

Typical scenarios involve troubleshooting failed lot split/merge imports, reconciling staging data before posting, and auditing what the interface program was asked to process.

-- All starting lots for a given import header
SELECT s.LOT_NUMBER, s.INVENTORY_ITEM_ID, s.ORGANIZATION_ID,
       s.SUBINVENTORY_CODE, s.LOCATOR_ID, s.QUANTITY
FROM   WSM.WSM_STARTING_LOTS_INTERFACE s
WHERE  s.HEADER_ID = :p_header_id;

Joining back to the parent interface to confirm which headers still have unposted starting-lot rows is a common reconciliation check:

SELECT h.*, s.LOT_NUMBER, s.QUANTITY
FROM   WSM.WSM_LOT_SPLIT_MERGES_INTERFACE h,
       WSM.WSM_STARTING_LOTS_INTERFACE s
WHERE  h.HEADER_ID = s.HEADER_ID
AND    s.REQUEST_ID = :p_request_id;

Identifying rows whose concurrent program failed or whose locator/subinventory references are invalid supports error-resolution reporting. Because the table carries REQUEST_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE, per-concurrent-request analysis is straightforward.

Related Objects

• WSM_LOT_SPLIT_MERGES_INTERFACE — Parent interface table; join on HEADER_ID.
• MTL_ITEM_LOCATIONS — Referenced via LOCATOR_ID (with ORGANIZATION_ID) for locator validation.
• MTL_SECONDARY_INVENTORIES — Referenced via SUBINVENTORY_CODE (with ORGANIZATION_ID).
• WSM_PARAMETERS — Referenced via ORGANIZATION_ID for organization-level defaults.
• MTL_SYSTEM_ITEMS_B — Not a documented FK on this table, but the standard destination for resolving INVENTORY_ITEM_ID descriptions.
• MTL_TRANSACTIONS_INTERFACE / MTL_MATERIAL_TRANSACTIONS — The downstream interface and posting targets that consumed validated starting-lot rows ultimately feed.

All references above are grounded in the documented ETRM foreign key and key metadata for the WSM schema.