Results for “wms_xdock_source_assignments”

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

Overview

WMS.WMS_XDOCK_SOURCE_ASSIGNMENTS is a Warehouse Management (WMS) configuration table that stores the source type assignments attached to crossdock criteria. In Oracle EBS, crossdocking allows inbound material to be routed directly to outbound demand without being put away into storage. A crossdock criterion defines the rules by which eligible receipts are matched to demand, and this table records which inbound source types and source codes a given criterion is permitted to consider. Each row therefore binds one crossdock criterion to one specific source type and source code combination, with an associated priority that governs evaluation order.

The relationship metadata classifies this object as satellite-leaning under a heuristic Data Vault model. In practical terms, this is best treated as a descriptive modeling suggestion: the table carries attribute detail (source type and code pairings, priority, audit columns) keyed to a parent criterion, rather than acting as a pure intersection link or a standalone hub. The table structure is consistent with a configuration satellite subordinate to a crossdock criteria parent entity.

Key Information Stored

The documented physical schema for 12.2.2 contains nine columns. The most significant are:

• CRITERION_ID — Identifies the parent crossdock criterion to which the source assignment belongs. This is the principal business-key discriminator and the leading column of the primary key.
• SOURCE_TYPE — Specifies the category of inbound source being assigned to the criterion (for example, the kind of document or supply origin). It forms the second component of the primary key.
• SOURCE_CODE — Holds the specific value within the source type, completing the composite business key. Together with CRITERION_ID and SOURCE_TYPE it uniquely identifies each row.
• PRIORITY — Establishes the order in which competing source assignments are evaluated when more than one assignment could match a receipt, allowing deterministic rule resolution.
• LAST_UPDATE_DATE — Timestamp of the most recent modification; used for change detection and audit reporting.
• LAST_UPDATED_BY — The user or process responsible for the last change.
• CREATION_DATE — Timestamp recording when the assignment row was first created.
• CREATED_BY — The user or process that created the row.
• LAST_UPDATE_LOGIN — The login context associated with the last update, supporting traceability.

The surrogate primary key is defined by the constraint WMS_XDOCK_SOURCE_ASSIGNMENT_PK, which spans CRITERION_ID, SOURCE_TYPE, and SOURCE_CODE. There is no separate single-column surrogate; the primary key is itself the composite business key, making the criterion, source type, and source code the natural identifiers of the row.

Common Use Cases and Queries

Typical uses include auditing crossdock configuration, troubleshooting why a receipt was or was not crossdocked, and migrating or comparing criteria between environments. A representative query retrieves all source assignments for a criterion, showing evaluation order:

• SELECT criterion_id, source_type, source_code, priority FROM wms_xdock_source_assignments WHERE criterion_id = :p_criterion ORDER BY priority;
• SELECT source_type, COUNT(*) FROM wms_xdock_source_assignments GROUP BY source_type; — distribution of source types across criteria.
• Joining to the parent criteria table on CRITERION_ID to report criterion names alongside their assigned sources.
• Change auditing: SELECT * FROM wms_xdock_source_assignments WHERE last_update_date >= :p_since ORDER BY last_update_date DESC;

Because the table governs eligibility rather than transactions, reporting focuses on configuration completeness and conflicts, such as duplicate or overlapping source codes for a single criterion.

Related Objects

The most significant related objects are:

• WMS_XDOCK_CRITERIA (parent criteria definition) — joined on CRITERION_ID; supplies the rule context for each assignment.
• WMS_XDOCK_SOURCE_ASSIGNMENTS itself — self-referencing relationship shown in the FK metadata via CRITERION_ID, relevant when analyzing criteria hierarchies or shared identifiers.
• Crossdock execution and matching tables that consume criterion and source configuration during inbound receipt processing.
• WMS crossdock concurrent programs and DBA views that read criteria configuration for eligibility evaluation.
• Standard audit references via CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN to FND_USER for user traceability.

The documented foreign key originates from CRITERION_ID, confirming that the criteria definition table is the authoritative parent and should always be joined when interpreting assignment rows.