Results for “entry_sequence”

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

Overview

WMS_STAGINGLANES_ASSIGNMENTS is a WMS (Warehouse Management) module table in the Oracle E-Business Suite 12.1.1 / 12.2.2 schema. Its documented purpose is to store the staging lane to dock door relationship — the physical configuration mapping that determines which staging lanes are associated with which dock doors within a warehouse. This relationship drives put-away, cross-docking, picking, and shipping staging logic, and is consumed by Oracle Warehouse Management for inbound and outbound material flow and by shipping execution for load consolidation and dock scheduling.

The table resides in the WMS schema and is classified as VALID in the ETRM dictionary. Under a heuristic Data Vault classification mined from its foreign-key structure, this object is best modeled as a link table: it resolves a many-to-many association between staging lanes and dock doors, each of which is itself an inventory location in MTL_ITEM_LOCATIONS. The link carries its own descriptive attributes (ENABLED flag, ENTRY_SEQUENCE, and the standard attribute flex columns), so a satellite companion would normally accompany the link in a Data Vault presentation.

Key Information Stored

The documented physical schema contains 27 columns, but the substantive configuration data is concentrated in a small set of keys and a control flag:

• DOCK_DOOR_ID — the inventory location identifier for the dock door; part of the primary key and of the unique business key.
• DOCK_DOOR_ORGANIZATION_ID — the inventory organization that owns the dock door location; ensures the door reference is organization-qualified.
• STAGE_LANE_ID — the inventory location identifier for the staging lane; the second link endpoint.
• STAGING_LANE_ORGANIZATION_ID — the organization that owns the staging lane location.
• ENTRY_SEQUENCE — ordinal used to order lanes assigned to a given door, governing the sequence in which the assignment is applied.
• ENABLED — flag indicating whether the lane-to-door assignment is active; disabled rows remain as historical configuration but are not used by the runtime logic.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard Oracle descriptive flexfield (DFF) segment set, providing the extensibility hook for customer-specific configuration attributes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the mandatory WHO audit columns present on every Oracle EBS transactional table.

The documented primary key is WMS_STAGINGLANES_ASSIGNMENT_PK, defined over the composite of DOCK_DOOR_ID, DOCK_DOOR_ORGANIZATION_ID, STAGE_LANE_ID, and STAGING_LANE_ORGANIZATION_ID. A second unique index, WMS_STAGINGLANES_ASSIGMNTS_U1, is defined over the identical four-column set; in this schema the primary-key constraint and the unique index coincide, so the PK columns are themselves the business-key candidates and the table carries no independent surrogate key column.

Common Use Cases and Queries

Typical usage centers on warehouse configuration, inbound staging, outbound shipment staging, and dock scheduling. A common query retrieves all enabled lanes assigned to a specific dock door, ordered by the configured sequence:

SELECT NVL(a.stage_lane_id,0) AS stage_lane_id, NVL(a.entry_sequence,0) AS entry_sequence, a.enabled FROM wms.wms_staginglanes_assignments a WHERE a.dock_door_id = :dock_door_id AND a.dock_door_organization_id = :org_id AND a.enabled = 'Y' ORDER BY a.entry_sequence;

Reverse lookups resolve which dock doors a staging lane is attached to, a pattern used when validating put-away directed to a specific lane. Because both keys resolve to MTL_ITEM_LOCATIONS, reporting joins that table twice — once for the dock door and once for the staging lane — to present human-readable location names. Data-governance queries scan for lanes or doors referenced by assignments, and for inactive (ENABLED = 'N') rows that may indicate stale setup. DFF reporting queries read ATTRIBUTE_CATEGORY and the ATTRIBUTE1–15 columns to surface organization-specific attributes.

Related Objects

• MTL_ITEM_LOCATIONS — referenced twice. The assignment's DOCK_DOOR_ID and DOCK_DOOR_ORGANIZATION_ID resolve to a dock-door inventory location, and STAGE_LANE_ID with STAGING_LANE_ORGANIZATION_ID resolve to a staging-lane inventory location. Both columns form the relationship back to the locations master.
• WMS_STAGINGLANES_ASSIGNMENTS PK/UQ constraints (WMS_STAGINGLANES_ASSIGNMENT_PK, WMS_STAGINGLANES_ASSIGMNTS_U1) — enforce uniqueness of the four-part business key and prevent duplicate lane-to-door configuration.
• WMS shipping and staging configuration objects — task and strategy setup that consumes staging lanes and dock door assignments when generating move orders, picking, and shipping load steps.
• MTL_PARAMETERS / organization setup — supplies the organization context validated by the organization ID columns.

Implementations extending this configuration typically join WMS_STAGINGLANES_ASSIGNMENTS to MTL_ITEM_LOCATIONS on both inventory location IDs (and their matching organization IDs) to produce lane-to-door reports, warehouse layout matrices, and validation lists for dock appointment and load-building processes.