Search Results object1_source_id

Overview

The WSH.WSH_FTE_COMP_CONSTRAINTS table is a core configuration object within the Oracle E-Business Suite Shipping Execution module (WSH). It stores the definitions of compatibility constraints that govern how shipping entities may be combined during planning, rating, and load-building operations. Representative constraint pairings include Item-to-Facility, Facility-to-Mode, and Facility-to-Carrier combinations. By persisting these rules centrally, the table enables the Shipping Execution engine to validate whether a proposed association between two shipping objects is permissible before a delivery, trip, or shipment is confirmed.

The table resides in the WSH schema and is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2. Its role is essentially that of a rule repository: each row defines a single compatibility pairing between two constraint objects, scoped to a compatibility class and bounded by effective dates. From a Data Vault modeling perspective, the metadata heuristic classifies this object as standalone. In practice, it functions as a satellite-like rule table keyed to a class dimension, and could be modeled as a link between the two constraint object references with descriptive satellite attributes for effectiveness and audit columns.

Key Information Stored

The table comprises 41 documented columns. The most significant are:

• COMPATIBILITY_ID — Surrogate primary key, enforced by WSH_FTE_COMP_CONSTRAINTS_PK.
• COMPATIBILITY_CLASS_ID — Foreign key to WSH_FTE_COMP_CLASSES, grouping constraints into logical classes. Also the leading column of the unique index WSH_FTE_COMP_CONSTRAINTS_U1.
• CONSTRAINT_TYPE — Classifies the nature of the compatibility rule.
• CONSTRAINT_OBJECT1_TYPE / CONSTRAINT_OBJECT2_TYPE — Identify the entity types being paired (for example, Item, Facility, Mode, Carrier).
• OBJECT1_SOURCE_TYPE / OBJECT1_SOURCE_ID and OBJECT2_SOURCE_TYPE / OBJECT2_SOURCE_ID — Describe the source from which each constraint object is derived.
• CONSTRAINT_OBJECT1_ID / CONSTRAINT_OBJECT2_ID — Reference the actual constraint object instances.
• CONSTRAINT_OBJECT1_VALUE_CHAR / CONSTRAINT_OBJECT2_VALUE_CHAR — Character value overrides for each side of the pairing.
• EFFECTIVE_DATE_FROM / EFFECTIVE_DATE_TO — Date-range bounds controlling when the constraint is active.
• DESCRIPTION — Free-text description of the rule.
• ATTRIBUTE_CATEGORY through ATTRIBUTE15 — Descriptive flexfield columns supporting user-defined extensibility.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, PROGRAM_ID, REQUEST_ID — Standard audit and concurrent-program tracking columns.

The unique index WSH_FTE_COMP_CONSTRAINTS_U1 spans the full combination of class, both object types, both source references, both constraint object IDs, and both value columns, ensuring no duplicate pairing exists within a class. WSH_FTE_COMP_CONSTRAINTS_PK on COMPATIBILITY_ID remains the true surrogate key.

Common Use Cases and Queries

Typical use cases include verifying whether a given item may ship from a facility, whether a facility supports a given mode or carrier, and resolving the effective constraint set for a shipment date. A representative query retrieves active constraints for a class:

SELECT c.COMPATIBILITY_ID, c.CONSTRAINT_OBJECT1_ID,
       c.CONSTRAINT_OBJECT2_ID, c.EFFECTIVE_DATE_FROM
FROM   WSH_FTE_COMP_CONSTRAINTS c
WHERE  c.COMPATIBILITY_CLASS_ID = :class_id
AND    SYSDATE BETWEEN c.EFFECTIVE_DATE_FROM
                   AND NVL(c.EFFECTIVE_DATE_TO, SYSDATE + 1);

Reporting scenarios include auditing expired constraints, listing facility-to-carrier compatibility for a region, and detecting overlapping effective-date ranges. Joining to WSH_FTE_COMP_CLASSES on COMPATIBILITY_CLASS_ID enriches results with class-level context.

Related Objects

• WSH_FTE_COMP_CLASSES — Parent class definition; joined via COMPATIBILITY_CLASS_ID.
• WSH_FTE_COMP_CONSTRAINTS — Referenced by shipping validation logic and concurrent programs.
• WSH_DELIVERY_DETAILS and WSH_TRIPS — Consume constraint results during planning.
• WSH_CARRIERS and WSH_LOCATIONS — Supply carrier and facility context for constraint evaluation.
• WSH_FTE_COMP_CONSTRAINTS_U1 — Business-key unique index enforcing uniqueness.

These objects collectively form the compatibility framework underpinning Shipping Execution rule enforcement.