Search Results default_default

Overview

The view APPS.OKS_BILL_SUBLINE_DTLS_V is a Service Contracts (OKS) reporting object shipped in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the contents of the billing sub-line details table that underpins the contract pricing, billing, and revenue-recognition engines. Billing sub-line details store the individual rating components that are evaluated for a given billing sub-line — fixed amounts, actual values, averaged quantities, usage readings, and adjustment rules — and the view presents these attributes in a single, denormalized projection suitable for concurrent programs, Oracle Reports, OAF pages, and third-party integrations.

The view is read-oriented and does not itself perform joins or filtering; it is a straight projection of the base table with a ROWID pseudo-column aliased as ROW_ID for row identification. This design keeps the view stable across patch levels while allowing ETRM-driven customizations to reference the underlying detail table indirectly.

Underlying Base Objects

According to documented metadata, the view is defined exclusively over the base object OKS_BILL_SUB_LINE_DTLS, accessed through an APPS synonym of the same name (alias BSDB in the view text). No joins, unions, or additional tables are present. Consequently, every column in the view maps one-to-one to a column in the base table, with only the ROWID being renamed to ROW_ID. The base table holds one row per billing sub-line detail record, keyed by the primary key ID and related to the parent sub-line via BSL_ID and to the associated billing schedule detail via BSD_ID.

Key Columns

• ROW_ID — the physical row identifier from the base table; useful for direct row updates or diagnostics.
• ID / OBJECT_VERSION_NUMBER — surrogate primary key and optimistic-locking version number.
• BSL_ID / BSL_ID_AVERAGED — identifiers of the billing sub-line to which the detail belongs, including the averaged counterpart.
• BSD_ID / BSD_ID_APPLIED — billing schedule detail identifiers that the detail is associated with and ultimately applied to.
• FIXED / ACTUAL / DEFAULT_DEFAULT — rating flags controlling whether the detail is a fixed amount, an actual charge, or the default candidate for the sub-line. DEFAULT_DEFAULT is the column returned by the user's search term.
• UNIT_OF_MEASURE, START_READING, END_READING, ESTIMATED_QUANTITY — usage-based billing attributes for counter and meter contracts.
• ADJUSTMENT_LEVEL, ADJUSTMENT_MINIMUM, RESULT, AMOUNT — adjustment and computed pricing values produced by the pricing engine.
• AMCV_YN, CCR_ID, CGR_ID — averaging/currency-conversion indicators and reference identifiers.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the standard EBS descriptive flexfield columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

The view is typically queried to reconcile billing sub-lines with their rating details, to audit default detail selection, and to extract usage readings for usage-based contracts. Common patterns include:

• Listing all detail rows for a given billing sub-line, including the default candidate:

  SELECT id, bsl_id, bsd_id, fixed, actual, default_default, amount
    FROM apps.oks_bill_sublin_dtls_v
   WHERE bsl_id = :p_bsl_id;

• Identifying default detail rows across a contract set:

  SELECT bsl_id, id, amount
    FROM apps.oks_bill_sublin_dtls_v
   WHERE default_default = 'Y';

• Extracting usage readings for metered contracts:

  SELECT bsl_id, start_reading, end_reading, unit_of_measure
    FROM apps.oks_bill_sublin_dtls_v
   WHERE end_reading IS NOT NULL;

Because the view performs no joins, it is inexpensive and can be safely used in high-volume extracts; join it to OKS_BILL_SUB_LINES or OKS_BILL_SCHEDULE_DTLS in the calling query when parent context is required.