Search Results wsh_fte_comp_classes_u2

Overview

WSH.WSH_FTE_COMP_CLASSES is a seed data table in the Oracle E-Business Suite Warehouse Management (WSH) schema. It stores the different types of classifications of compatibility constraints, along with a severity indicator that is either "Error" or "Warning". This severity indicator allows the system to determine whether an incompatibility detected between freight items or containers should abort the transaction/process or merely continue with a warning. In essence, the table defines a library of compatibility classes, where each class captures the business rule for how a violation of that class should be treated by the freight and transportation execution logic.

In terms of Data Vault modeling heuristics, this table is classified as standalone, with no foreign keys pointing outward to other parent entities. Its natural role in a Data Vault model would be a hub-like reference (or a reference/lookup hub) because it holds a stable, business-keyed set of classification codes. It is a candidate to be modeled as a hub for the compatibility class business concept, with the severity attribute (CONSTRAINT_VIOLATION) functioning as a descriptive satellite attribute. Because it is seed data in the APPS_TS_SEED tablespace, it changes infrequently and is generally maintained by Oracle rather than by end users, though extensions through descriptive flexfields are possible.

Key Information Stored

The table contains 29 documented columns in the 12.2.2 physical schema, though its core identity and meaning are carried by a small number of key fields:

• COMPATIBILITY_CLASS_ID – The surrogate Primary Key of the table, defined by WSH_FTE_COMP_CLASSES_PK. It uniquely identifies each compatibility class row and is the column referenced by child tables.
• COMPATIBILITY_CLASS_CODE – A lookup-based value that identifies the compatibility class. It is the business-key candidate, backed by unique index WSH_FTE_COMP_CLASSES_U2 (COMPATIBILITY_CLASS_CODE, ZD_EDITION_NAME).
• CONSTRAINT_VIOLATION – Defines the violation severity: "Error" (abort the process) or "Warning" (continue with a warning).
• COMPATIBILITY_CLASS_ID also appears in unique index WSH_FTE_COMP_CLASSES_U1 (COMPATIBILITY_CLASS_ID, ZD_EDITION_NAME), reinforcing that the surrogate key plus ZD_EDITION_NAME forms a unique composite.
• ZD_EDITION_NAME – Editioning column introduced for Online Patching in 12.2, included in both unique indexes to support edition-based redefinition and multi-tenant compatible access.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 – Descriptive flexfield (DFF) structure and segment columns, allowing customers to capture additional, installation-specific classification attributes without schema change.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID – Standard "Who" and concurrent program audit columns that record who created and last modified the row and which program or request performed the change.

Common Use Cases and Queries

This table is referenced by the freight compatibility engine to resolve the severity of a detected constraint violation. A typical reporting query joins the class definitions to the constraints that use them to show which compatibility rules are configured as hard errors versus soft warnings:

• List all compatibility classes: SELECT compatibility_class_id, compatibility_class_code, constraint_violation FROM wsh.wsh_fte_comp_classes ORDER BY compatibility_class_code;
• Find classes that abort processing (errors only): SELECT compatibility_class_code FROM wsh.wsh_fte_comp_classes WHERE constraint_violation = 'Error';
• Join to constraints to see severity per rule: SELECT c.compatibility_class_code, c.constraint_violation, con.constraint_id FROM wsh.wsh_fte_comp_classes c, wsh.wsh_fte_comp_constraints con WHERE c.compatibility_class_id = con.compatibility_class_id;
• Descriptive flexfield reporting: query ATTRIBUTE_CATEGORY and ATTRIBUTE1..15 to surface customer-defined extensions on each class.

Because the table is seed data, it is also useful for validation and setup reviews to confirm that expected classes (and their Error/Warning severities) exist before running freight compatibility checks.

Related Objects

The most significant dependent object is the constraints table that references this class definition:

• WSH_FTE_COMP_CONSTRAINTS – Child table; its COMPATIBILITY_CLASS_ID foreign key points to WSH_FTE_COMP_CLASSES.COMPATIBILITY_CLASS_ID. This is the principal relationship, linking each constraint rule to the class that determines its Error/Warning behavior.
• WSH_FTE_COMP_CLASSES_PK – Primary key constraint on COMPATIBILITY_CLASS_ID.
• WSH_FTE_COMP_CLASSES_U1 – Unique index on (COMPATIBILITY_CLASS_ID, ZD_EDITION_NAME).
• WSH_FTE_COMP_CLASSES_U2 – Unique index on (COMPATIBILITY_CLASS_CODE, ZD_EDITION_NAME), the index referenced in the search term "wsh_fte_comp_classes_u2" and the business-key access path.
• FND Lookups – COMPATIBILITY_CLASS_CODE is lookup-based, so its values are governed by an Oracle EBS lookup type maintained in the application's lookup framework.
• Freight/Transportation Execution (FTE) APIs and concurrent programs – Program IDs and request IDs captured in the audit columns indicate the seed/maintenance processes that populate this class library.

In practice, most customizations and integrations should treat WSH_FTE_COMP_CLASSES as a read-only reference source, joining on COMPATIBILITY_CLASS_ID or COMPATIBILITY_CLASS_CODE rather than modifying its seed rows directly.