Results for “csd_ahl_w_contract_xref”

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

Overview

CSD_AHL_W_CONTRACT_XREF is a reference table owned by the CSD schema in Oracle E-Business Suite, delivered as part of the Depot Repair module. It is documented as the Supplier Warranty table and serves as the association layer that ties an Oracle warranty contract record to a specific depot repair line. In practical terms, the table answers the question of which supplier warranty contract applies to a given repair transaction, a determination that is central to warranty validation, entitlement checking, and downstream recovery of repair costs from the warranty provider.

The ETRM metadata records this object as VALID with a documented physical schema of 29 columns in release 12.2.2, and the same object is present in 12.1.1. Heuristic Data Vault classification mined from the foreign key structure suggests this table models as a link: it resolves a many-to-many style relationship between warranty contracts and repair lines, holding only relationship identifiers, audit columns, and descriptive attributes rather than a self-contained business entity. This classification is a modeling suggestion rather than a functional definition; Oracle does not publish it as a Data Vault construct.

Key Information Stored

The surrogate primary key is WARRANTY_CONTRACT_XREF_ID, enforced by the CSD_AHL_W_CONTRACT_XREF_PK constraint. Application logic, concurrent programs, and foreign key references should use this synthetic identifier rather than any composite of the business columns.

The business linkage is carried by two foreign key columns. WARRANTY_CONTRACT_ID points to AHL_WARRANTY_CONTRACTS_B and identifies the supplier warranty contract. REPAIR_LINE_ID points to CSD_REPAIRS and identifies the depot repair line being warranted. Together these two columns form the natural business key candidate for the relationship, though the documented metadata exposes only the surrogate primary key as a unique constraint.

Because this is a generic cross-reference structure, the row also stores the origin of the association through SOURCE_TABLE, SOURCE_COLUMN, and SOURCE_ID, which allow the application to record which source object generated the warranty-to-repair linkage and support extensibility for additional sourcing patterns. INSTANCE_ID supports multi-organization and instance-level partitioning of the data in environments that use multiple operating units or instance contexts.

Standard EBS audit and concurrency columns are present: OBJECT_VERSION_NUMBER provides optimistic locking for concurrent updates, while CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN capture the standard WHO-column audit trail. The fifteen ATTRIBUTE columns plus ATTRIBUTE_CATEGORY provide flexfield-style descriptive and extensibility storage, commonly used by implementations to persist warranty reference numbers, claim codes, or external provider identifiers without a schema change.

Common Use Cases and Queries

The most common scenario is locating every warranty contract that has been associated with a repair order or repair line, typically for warranty validation and cost recovery reporting. A representative query joins the cross-reference to the repair and contract tables:

• SELECT x.warranty_contract_xref_id, x.repair_line_id, x.warranty_contract_id, w.contract_number FROM csd.csd_ahl_w_contract_xref x, csd.ahl_warranty_contracts_b w WHERE x.warranty_contract_id = w.warranty_contract_id AND x.repair_line_id = :p_repair_line_id;
• Reverse lookup by contract: filter on WARRANTY_CONTRACT_ID to list all repair lines covered by a supplier warranty, useful when reconciling claims submitted to a warranty provider.
• Source provenance analysis: aggregate on SOURCE_TABLE and SOURCE_COLUMN to determine which integration or entry path created warranty linkages, supporting data quality and migration audits.
• Descriptive reporting: project ATTRIBUTE_CATEGORY and the ATTRIBUTE1 through ATTRIBUTE15 columns to expose implementation-specific warranty reference data in custom reports.

No public API is documented on this table itself; inserts and updates normally occur through Depot Repair warranty processing logic, and direct DML should be avoided in production to preserve the audit and version columns.

Related Objects

The following objects are the most significant in the referential neighborhood of CSD_AHL_W_CONTRACT_XREF:

• AHL_WARRANTY_CONTRACTS_B — parent warranty contract entity; joined on WARRANTY_CONTRACT_ID.
• CSD_REPAIRS — parent depot repair line entity; joined on REPAIR_LINE_ID.
• AHL_WARRANTY_CONTRACTS_TL — translation table supplying contract names and descriptions for the referenced contract.
• AHL_WARRANTY_CONTRACT_LINES — detail lines that define covered items and terms within the parent contract.
• CSD_REPAIR_ORDERS / CSD_REPAIR_LINES — repair contexts through which the linked CSD_REPAIRS rows are accessed.
• CSD_AHL_W_CONTRACT_XREF_PK — the primary key constraint that enforces uniqueness of WARRANTY_CONTRACT_XREF_ID.