Results for “ph_min_amt”

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

Overview

OKS_AUTH_LINES_V is an APPS-owned, VALID view in the Oracle E-Business Suite Service Contracts (OKS) module. It exposes authorized contract line data used by the Service Contracts Authoring and pricing engines, and is commonly consumed by reporting, integration, and extension code that must read contract line attributes without touching the underlying transactional base tables directly. The view is defined as a projection over service contract line entities, surfacing line-level pricing, status, currency, and descriptive flexfield information in a single queryable structure. Because the object is a view rather than a table, it is read-only by convention; the DML is performed against the underlying base entities and the view is refreshed through those underlying data changes. The "AUTH" (authorization) naming reflects the Service Contracts process in which line-level entitlement, coverage, and pricing data are validated and made available to downstream billing and renewal flows.

Underlying Base Objects

The documented ETRM metadata for 12.1.1 and 12.2.2 identifies the following referenced base objects, exposed as synonyms in the APPS schema:

• OKC_K_LINES_B — the base contract line table.
• OKC_K_LINES_TL — the translated (TL) contract line table holding language-specific descriptions.
• OKS_K_LINES_B — the Service Contracts extension of the contract line table.
• OKS_K_LINES_TL — the translated Service Contracts line table.

The view text aliases the core line source as CLEB (contract line entity base), indicating it is built primarily over the contract line entities, with the OKS-specific objects supplying Service Contracts attributes. In practice the view joins the common Contracts Core (OKC) line structures with the Service Contracts (OKS) line structures so that both generic contract line columns and OKS-specific columns are available in one row. The presence of translated siblings (OKC_K_LINES_TL, OKS_K_LINES_TL) indicates the view may also expose or support language-dependent line description retrieval, though the exposed column list is dominated by base (non-translated) and DFF columns.

Key Columns

The view exposes well over fifty columns. Notable ones include:

• CLE_ID, CLE_ID_RENEWED, CLE_ID_RENEWED_TO — line identifiers supporting renewal lineage.
• CHR_ID, DNZ_CHR_ID — contract header references for the current and "do-not-zone" header contexts.
• LINE_NUMBER, DISPLAY_SEQUENCE — ordering of lines within a contract.
• STS_CODE, TRN_CODE — status and transaction codes governing line state.
• PRICE_NEGOTIATED, PRICE_NEGOTIATED_RENEWED, PRICE_LEVEL_IND, PRICE_UNIT, PRICE_UNIT_PERCENT, PRICE_TYPE — pricing attributes, including renewed pricing.
• CURRENCY_CODE, CURRENCY_CODE_RENEWED — currencies for original and renewed pricing.
• START_DATE, END_DATE, DATE_TERMINATED, DATE_RENEWED — effective-dating and termination tracking.
• INVOICE_LINE_LEVEL_IND, DPAS_RATING, TEMPLATE_USED, EXCEPTION_YN, HIDDEN_IND — billing, rating, and display flags.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield support.
• UPG_ORIG_SYSTEM_REF, UPG_ORIG_SYSTEM_REF_ID, ORIG_SYSTEM_SOURCE_CODE — upgrade and original-system lineage.
• SECURITY_GROUP_ID — Multi-Org security grouping.
• Standard WHO columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Note that the searched term "price_basis_yn" does not appear in the documented column list for this view. Pricing-basis behavior is instead represented via PRICE_LEVEL_IND, PRICE_TYPE, and the PRICE_* columns. If your code expects a PRICE_BASIS_YN column, verify the object or version, since it is not documented here.

Common Use Cases and Queries

Typical usage includes contract line reporting, renewal analysis, pricing extraction, and integration extracts. A basic query retrieving active lines and pricing follows:

• SELECT cle_id, chr_id, line_number, sts_code, price_type, price_negotiated, price_level_ind, currency_code, start_date, end_date FROM apps.oks_auth_lines_v WHERE chr_id = :p_chr_id ORDER BY display_sequence;
• Renewal lineage: SELECT cle_id, cle_id_renewed, cle_id_renewed_to, date_renewed, price_negotiated, price_negotiated_renewed, currency_code_renewed FROM apps.oks_auth_lines_v WHERE cle_id IN (:p_line_ids);
• Filtering by DFF: SELECT cle_id, attribute_category, attribute1, attribute2 FROM apps.oks_auth_lines_v WHERE attribute_category = :p_cat;

Because the view is built over OKC/OKS base and translated tables, joins to OKC_K_HEADERS and OKS contract header objects are common to retrieve header-level context. Multi-Org security should be respected by filtering SECURITY_GROUP_ID or querying under the appropriate operating unit. Treat the view as read-only and rely on Service Contracts APIs for any data modification.