Search Results interface_offset_days

Overview

OKS_STREAM_LEVELS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the Service Contracts (OKS) product family. The view is described in ETRM documentation as "Billing Stream Levels" and is classified as a VALID database object in both release 12.1.1 and 12.2.2. Its purpose is to expose the tiered or level-based structure of a billing stream, so that each level of a contract's billing schedule — its period, unit of measure, advance timing, level amount, and offset dates — is available for query, reporting, and integration.

In Service Contracts, a billing stream defines how recurring or usage-based charges are invoiced over time. Streams may be organized into multiple levels, where each level carries its own periodicity, quantity per period, lead time for advancing charges, and the amount to be billed. OKS_STREAM_LEVELS_V surfaces these levels in a single flattened structure, making it practical for extraction, reconciliation, and downstream interfaces that need to interpret billing schedules without navigating multiple base tables.

Underlying Base Objects

The view is defined over a single base object: OKS_STREAM_LEVELS_B, referenced in the view text through the alias SLL, with the synonym resolving to the underlying table in the APPS schema. OKS_STREAM_LEVELS_B is the transactional base table that stores billing stream level definitions. Because the view is built over the base table and its column list mirrors the base columns, OKS_STREAM_LEVELS_V can generally be used interchangeably with the base table for read operations.

The view text carries no joins, filters, or transformations — each column is a direct projection of the corresponding base column. There is therefore no data change, no deduplication, and no row-level filtering applied by the view. Its principal value is providing a consistent, supported read interface for concurrent programs, reports, and integration components that should not query the base table directly.

Key Columns

• ID — Primary identifier of the stream level record.
• CHR_ID — Identifier of the owning contract or header record; CLE_ID and DNZ_CHR_ID provide related linkage identifiers used to associate the level with its stream and contract context.
• SEQUENCE_NO — Ordering of the level within the stream.
• UOM_CODE, UOM_PER_PERIOD, LEVEL_PERIODS — Define the unit of measure, quantity per period, and number of periods covered by the level.
• START_DATE, END_DATE — Effective date range for the level.
• ADVANCE_PERIODS — Number of periods by which billing is advanced relative to the level start.
• INVOICE_OFFSET_DAYS — Offset, in days, applied when generating the invoice for the level.
• INTERFACE_OFFSET_DAYS — Offset, in days, applied when the level is passed to the interfacing or downstream accounting process. This is the column referenced by searches for "interface_offset_days".
• LEVEL_AMOUNT, AMOUNT — Monetary amounts associated with the level.
• DUE_ARR_YN, LINES_DETAILED_YN — Flags controlling due/arrears treatment and whether detail lines are generated.
• OBJECT_VERSION_NUMBER, SECURITY_GROUP_ID, REQUEST_ID — Concurrency, multi-tenant security, and concurrent request tracking columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns.
• ROW_ID — The row identifier projected from the base table.

Common Use Cases and Queries

Typical uses include extracting billing schedules for revenue recognition, validating offset values before invoice generation, and supporting integrations that consume stream level data. The INTERFACE_OFFSET_DAYS column is frequently queried to confirm the number of days between the level and its downstream interface processing.

Retrieve all levels for a contract:

SELECT id, chr_id, sequence_no, start_date, end_date, level_amount, invoice_offset_days, interface_offset_days FROM oks_stream_levels_v WHERE chr_id = :p_chr_id ORDER BY sequence_no;

Review interface and invoice offset values:

SELECT id, chr_id, sequence_no, invoice_offset_days, interface_offset_days FROM oks_stream_levels_v WHERE interface_offset_days IS NOT NULL;

Confirm recent changes to a level:

SELECT id, chr_id, last_updated_by, last_update_date FROM oks_stream_levels_v WHERE last_update_date >= :p_since ORDER BY last_update_date DESC;

Because the view projects the base table directly, queries against it return the same rows and values as queries against OKS_STREAM_LEVELS_B, while remaining aligned with the supported APPS-level interface.