Results for “rle_code”

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

Overview

OKS_K_DEFAULTS_V is a public APPS view in the Service Contracts (OKS) module of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. It presents the defaulting data that Oracle Service Contracts applies when a contract is renewed automatically or when a contract is created directly from an order. The underlying defaults are classified by CDT_TYPE: a "Master" default, identified by the value 'MDT', or a "Segmented" default, where the record is qualified by one or more segment identifiers. Because the view is a thin projection of the base table with no joins or filters in the documented view text, it behaves as a reporting and integration façade rather than a transformed data set. ETRM reports the object status as VALID with owner APPS.

Underlying Base Objects

The documented definition is a direct SELECT from OKS_K_DEFAULTS, referenced through the public synonym in the APPS schema. All columns in the view originate from that single base object; no lookup, master-detail, or security joins are performed inside the view text. Consequently, row-level filtering, segment resolution, and any reference to price lists, templates, or billing profiles occur in the calling forms and APIs rather than in the view itself. The view exposes the base table's ROWID as ROW_ID plus its surrogate ID, making both a stable key and the physical row address available to consumers.

Key Columns

• ID, CDT_TYPE, OBJECT_VERSION_NUMBER — primary identifier, default classification ('MDT' for master defaults), and the optimistic locking counter used by the OAF and Forms layers.
• SEGMENT_ID1, SEGMENT_ID2 — segment qualifiers that distinguish segmented defaults.
• THRESHOLD_CURRENCY, THRESHOLD_AMOUNT, THRESHOLD_ENABLED_YN — the threshold amount and currency plus its enablement flag. When the threshold is enabled, the service contract value is compared against THRESHOLD_AMOUNT to determine whether the default applies; this is the column set most frequently queried by users searching on threshold_amount.
• EVERGREEN_THRESHOLD_CURR, EVERGREEN_THRESHOLD_AMT — threshold values governing evergreen-style renewal behavior.
• PAYMENT_THRESHOLD_CURR, PAYMENT_THRESHOLD_AMT — monetary threshold applied to payment processing.
• RENEWAL_TYPE, RENEWAL_PRICING_TYPE, MARKUP_PERCENT, RENEWAL_* — renewal policy and pricing attributes applied as defaults.
• PRICE_LIST_ID1, PRICE_LIST_ID2, PAYMENT_TERMS_ID1, PAYMENT_TERMS_ID2, BILLING_PROFILE_ID, TEMPLATE_SET_ID, PDF_ID, QCL_ID — foreign keys to the pricing, terms, billing, template, and document objects used during defaulting.
• START_DATE, END_DATE, GRACE_PERIOD, GRACE_DURATION, PO_REQUIRED_YN, PAYMENT_METHOD, EMAIL_ADDRESS, USER_ID, INTERFACE_PRICE_BREAK — operational defaults including validity window, grace handling, purchase order requirement, notification target, and price-break interface control.

Common Use Cases and Queries

Typical uses include confirming which defaults Oracle Service Contracts will apply to a renewal or order-sourced contract, auditing threshold configuration, and troubleshooting why a threshold-based default did not fire. A query locating threshold defaults is:

• SELECT id, cdt_type, threshold_currency, threshold_amount, threshold_enabled_yn FROM oks_k_defaults_v WHERE threshold_enabled_yn = 'Y';
• SELECT id, cdt_type, renewal_type, renewal_pricing_type, markup_percent FROM oks_k_defaults_v WHERE cdt_type = 'MDT';
• SELECT id, segment_id1, segment_id2, payment_threshold_amt, evergreen_threshold_amt FROM oks_k_defaults_v WHERE threshold_amount > 0;

Because the view performs no filtering, callers should constrain by CDT_TYPE and segment columns to isolate the applicable default row.