Search Results chr_type




Overview
Explore in AI Chat

Overview

APPS.OKX_CONTRACTS_V is a reporting and integration view in Oracle E-Business Suite that exposes a consolidated, denormalized representation of contract headers. It is owned by the APPS schema and is defined over the core Oracle Contracts (OKC) header tables. The view is intended to present contract master data — contract identifiers, names, descriptions, validity dates, status, financial and organizational attributes, and the contract type flag (CHR_TYPE) — in a single flat structure suitable for concurrent program output, Oracle Discoverer/BI Publisher reports, interface staging, and external integrations.

The user search term "chr_type" maps directly to a column exposed by this view. CHR_TYPE is sourced from the OKC_K_HEADERS_B base table and carries the classification of the contract record (for example, distinguishing contract categories as maintained by the Contracts core). Because it is surfaced unchanged from the base table, it retains the same domain and semantics as the underlying OKC column.

Underlying Base Objects

Per the documented view text, OKX_CONTRACTS_V is defined over two synonym-referenced base objects:

  • OKC_K_HEADERS_B — the base (non-translated) contract header table, aliased CHR. Supplies the majority of columns, including CHR_TYPE.
  • OKC_K_HEADERS_TL — the translated (language) contract header table, aliased TL. Supplies language-dependent descriptive text.

The two tables are joined on CHR.ID = TL.ID, further restricted by TL.LANGUAGE = USERENV('LANG'), so that the view returns exactly one row per contract header in the session's current language. This join pattern is characteristic of Oracle's _B/_TL table pairs, where the _B table holds language-independent data and the _TL table holds translatable attributes.

Key Columns

  • ID1 — the contract header primary key (CHR.ID). The literal ID2 value of '#' is a placeholder for interface mapping.
  • NAME — concatenation of CONTRACT_NUMBER and CONTRACT_NUMBER_MODIFIER, with the modifier appended after a period when present.
  • DESCRIPTION — TL.SHORT_DESCRIPTION, the language-specific short description of the contract.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — the contract's start and end dates from the base header record.
  • STATUS — derived at runtime from the start and end dates: 'I' (inactive) if the current date precedes the start date or exceeds the end date, otherwise 'A' (active).
  • CHR_TYPE — the contract type/classification flag carried from OKC_K_HEADERS_B.
  • SCS_CODE, STS_CODE — contract status codes (system/status code columns) exposed for status reporting.
  • ORG_ID / INV_ORG_ID — the authoring organization and inventory organization identifiers.
  • BUY_OR_SELL — indicates whether the contract is a purchasing or sales contract.
  • CURRENCY_CODE — the contract currency.
  • PRIMARY_UOM_CODE — always NULL in this definition; retained for interface/column-shape compatibility.

Common Use Cases and Queries

The view is commonly used to list active contracts, filter by contract type, or drive downstream interfaces that expect a flat header extract. Because STATUS and NAME are computed, consumers should be aware that results are session-language dependent and date driven.

Listing active contracts of a given type:

  • SELECT id1, name, description, chr_type, currency_code, buy_or_sell
    FROM apps.okx_contracts_v
    WHERE status = 'A' AND chr_type = :p_chr_type;

Joining the view to contract lines for reporting detail:

  • SELECT v.name, v.chr_type, v.start_date_active, v.end_date_active
    FROM apps.okx_contracts_v v
    WHERE v.org_id = :p_org_id
    ORDER BY v.name;

Because the view performs no aggregation and joins only the header and translated-header tables, it is inexpensive and safe for high-volume reporting. Filters on ID1, CHR_TYPE, ORG_ID, and STATUS are the most effective predicates, since CHR_TYPE and the identifier columns pass directly to the base table.