Search Results okl_invc_frmt_strms_v




Overview
Explore in AI Chat

Overview

OKL_INVC_FRMT_STRMS_V is a VALID database view owned by the APPS schema within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environment. It belongs to the OKL product family — Oracle Leasing and Finance Management — which forms part of the ETRM (Enterprise Transaction and Revenue Management) solution set. The view presents invoice format stream assignments, capturing the business rule that every stream type must be assigned to exactly one invoice type and be included within one invoice line. In this context, a "stream" represents a recurring or one-time billing component generated by a lease or loan contract, while the invoice format defines how those streams are grouped, labeled, and printed on a customer invoice. The view therefore acts as the configuration bridge between the stream-type catalog (OKL_STREAM_TYPES) and the invoice formatting structures.

Functionally, OKL_INVC_FRMT_STRMS_V is a thin, denormalized projection of its single base table. It primarily serves reporting, data extraction, and integration purposes: it allows concurrent programs, Oracle Reports/BI Publisher layouts, and external interfaces to read invoice-format-to-stream mappings without directly querying the transactional table. Because it is a view rather than a table, it inherits the security and grant model of the APPS schema and can be referenced freely in custom SQL, OAF pages, and Discoverer workbooks.

Underlying Base Objects

The view is defined over exactly one documented base object: the table OKL_INVC_FRMT_STRMS, accessed through its APPS synonym. The definition is a straightforward SELECT that projects every column of the base table, exposing the physical ROWID as ROW_ID and preserving the OBJECT_VERSION_NUMBER column used by the Oracle Applications framework for optimistic locking (WHO column). No joins, aggregations, filters, or DECODE logic are applied. Consequently, the view is a one-to-one logical mirror of OKL_INVC_FRMT_STRMS; row counts and cardinality are identical between the two, and any row inserted, updated, or deleted in the base table is immediately visible through the view. The three key foreign-key columns — STY_ID, INF_ID, and ILT_ID — reference the stream type, invoice format, and invoice line type respectively, enforcing the assignment rule described in the object documentation.

Key Columns

  • ROW_ID — the physical ROWID of the underlying OKL_INVC_FRMT_STRMS row; useful for high-performance direct-row access.
  • ID — the primary key of the assignment record.
  • OBJECT_VERSION_NUMBER — the standard EBS optimistic-locking version number; incremented on each update.
  • STY_ID — identifier of the stream type being assigned.
  • INF_ID — identifier of the invoice format (invoice type) to which the stream type is assigned.
  • ILT_ID — identifier of the invoice line type under which the stream appears on the printed or electronic invoice.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard descriptive flexfield (DFF) columns, allowing customers to capture additional implementation-specific attributes without customization.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — WHO audit columns identifying the user and timestamp of creation and last modification.

Common Use Cases and Queries

Typical use cases include validating that every stream type has been assigned an invoice format and line before go-live, troubleshooting invoice generation where a stream does not appear, and building custom reports that map contract streams to invoice presentation. A basic query lists all current assignments:

SELECT id, sty_id, inf_id, ilt_id
FROM apps.okl_invc_frmt_strms_v
ORDER BY inf_id, ilt_id, sty_id;

A more practical query joins the view to the stream-type and invoice-format base tables to produce readable output:

SELECT v.sty_id, st.name stream_type,
       v.inf_id, inf.name invoice_format,
       v.ilt_id, ilt.name invoice_line
FROM apps.okl_invc_frmt_strms_v v,
       apps.okl_stream_types st,
       apps.okl_invc_frmts inf,
       apps.okl_invc_line_types ilt
WHERE v.sty_id = st.id
  AND v.inf_id = inf.id
  AND v.ilt_id = ilt.id;

Because the view is unrestricted, developers should apply the appropriate ORG_ID or operating-unit predicates in their surrounding query logic where multi-org security is required, and should treat it strictly as a read-only access path for reporting and integration.