Results for “trn_code”

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

Overview

OKC_LAUNCH_LGRID_V is an APPS-owned database view in the Oracle E-Business Suite Contracts Core (OKC) module. It is a reporting component of the Contracts Launchpad, specifically serving the Overview tab that displays contract line information. The view consolidates contract line header records, their translated descriptive attributes, line style information, and status meanings into a single denormalized projection, allowing the Launchpad user interface and any dependent reporting or integration logic to retrieve a contract's lines without performing multi-table joins at runtime.

The view is documented as VALID and is present in both Oracle EBS 12.1.1 and 12.2.2. It is read-only and does not itself hold data; all content is derived from the underlying contracts base tables. In the context of the search term date_terminated, the view exposes the DATE_TERMINATED column directly from OKC_K_LINES_B, making it a convenient source for identifying lines that have been terminated or for filtering out inactive lines in Launchpad-style queries.

Underlying Base Objects

The view text joins four base objects, all resolved through APPS synonyms, plus one PL/SQL package used for formatting:

• OKC_K_LINES_B (alias CLEB) — the contract line header base table, providing identifiers, status code, pricing, currency, dates, and audit columns.
• OKC_K_LINES_TL (alias CLET) — the translated line text table, supplying COMMENTS and ITEM_DESCRIPTION. The join is restricted by CLET.LANGUAGE = USERENV('LANG').
• OKC_LINE_STYLES_TL (alias LSET) — the translated line style table, supplying LSE_NAME and joined on LSE_ID with a matching language.
• OKC_STATUSES_TL (alias STS) — the translated status lookup, joined on STS.CODE = CLEB.STS_CODE to resolve STATUS_MEANING.
• OKC_QUERY (package) — its SETSUBLINEINDENT function computes the NAME column by de-normalizing the sub-line hierarchy indentation for display in the Launchpad grid.

The primary join key is CLEB.ID = CLET.ID, with the row identity further qualified by CLEB.CHR_ID, the contract header identifier.

Key Columns

• ROW_ID — the ROWID of the OKC_K_LINES_B row, usable for direct row access.
• ID, CHR_ID, DNZ_CHR_ID — line identifier, contract header identifier, and the owning (donor) contract identifier respectively.
• LINE_NUMBER, DISPLAY_SEQUENCE — ordering attributes for presenting lines in the Launchpad grid.
• STS_CODE, STATUS_MEANING — the line status code and its translated meaning.
• TRN_CODE — the transaction code associated with the line.
• NAME — the indented sub-line display name derived from OKC_QUERY.SETSUBLINEINDENT.
• ITEM_DESCRIPTION, COMMENTS — translated descriptive text for the line.
• PRICE_NEGOTIATED, CURRENCY_CODE, PRICE_TYPE — pricing information.
• DATE_TERMINATED — the date on which the line was terminated; NULL for active lines. This is the column most relevant to the user's search.
• START_DATE, END_DATE — the effective date range of the line.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

A frequent requirement is to list all active lines for a contract, excluding terminated ones. Because DATE_TERMINATED is exposed directly, no join back to OKC_K_LINES_B is required:

SELECT id, chr_id, line_number, name, status_meaning, date_terminated
FROM   okc_launch_lgrid_v
WHERE  chr_id = :p_chr_id
AND    date_terminated IS NULL
ORDER  BY display_sequence;

The view also supports reporting on terminated lines within a date window, for example to review contract reductions during a period:

SELECT chr_id, id, line_number, item_description, date_terminated
FROM   okc_launch_lgrid_v
WHERE  date_terminated BETWEEN :p_from_date AND :p_to_date;

Other practical scenarios include populating Launchpad overview grids, feeding contract analytics extracts, and reconciling line-level status via STATUS_MEANING. Because the view depends on USERENV('LANG') and USERENV('LANG') for translation, queries should be executed in the correct session language context to return the expected translated values.