Search Results okl_invc_line_types_v




Overview
Explore in AI Chat

Overview

OKL_INVC_LINE_TYPES_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKL – Leasing and Finance Management (Oracle Lease and Finance Management, often referred to as ETRM) product family. The view presents the definition of invoice line types, which determine the "type" of an invoice line in terms of how transactions, stream types, and cash flows are grouped onto that line. In other words, an invoice line type acts as a classification and grouping mechanism that governs how individual contractual events and cash flows are summarized and presented on a generated invoice.

The view exists primarily to support reporting, integration, and lookup requirements. Because Oracle stores the translatable descriptive text of these definitions in a separate table from the base (non-translatable) attributes, the view joins the two together and filters the translation rows by the session language. This makes the view the natural access point for concurrent programs, OAF pages, BI Publisher reports, APIs, and external integrations that need a language-resolved list of invoice line types together with their identifiers and descriptive flexfield (DFF) attributes.

Underlying Base Objects

OKL_INVC_LINE_TYPES_V is defined over two documented base objects, both referenced through synonyms:

  • OKL_INVC_LINE_TYPES_B — the base table holding the language-independent attributes, including the primary identifier, object version number, sequence number, the invoice type reference, and the DFF attribute columns. The alias ILTB is used for this table in the view definition.
  • OKL_INVC_LINE_TYPES_TL — the translation table holding the language-dependent NAME and DESCRIPTION text, along with the SFWT_FLAG column. The alias ILTT is used for this table.

The two tables are joined on their common identifier (ILTB.ID = ILTT.ID) and the translation row is restricted by ILTT.LANGUAGE = USERENV('LANG'), so the view returns descriptive text in the language of the current user session. The view also exposes ILTB.ROWID, which allows consumers to address base rows directly when required.

Key Columns

  • ID — the unique identifier of the invoice line type.
  • NAME — the user-facing (translated) name of the invoice line type.
  • DESCRIPTION — the translated description of the grouping rule the line type represents.
  • ITY_ID — the invoice type identifier to which the invoice line type belongs, linking the line type to its parent invoice type.
  • SEQUENCE_NUMBER — the ordering value used to position the invoice line type in presentation and processing sequences.
  • SFWT_FLAG — a sourcing/flag indicator carried from the translation table.
  • OBJECT_VERSION_NUMBER — supports optimistic locking for updates against the underlying base record.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield columns available for customer-specific extension data.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns derived from the base table.
  • ROW_ID — the base table ROWID, exposed for direct row addressing.

Common Use Cases and Queries

The view is typically used to drive list-of-values regions, invoice generation logic, and reporting on how invoices are structured. A common pattern is to retrieve all invoice line types for a given invoice type, in sequence order:

SELECT id, name, description, ity_id, sequence_number, sfwt_flag
FROM apps.okl_invc_line_types_v
WHERE ity_id = :invoice_type_id
ORDER BY sequence_number;

For a language-resolved lookup of a single line type by name, consumers can filter on the translated NAME column, relying on the view's session-language restriction. Integration developers should treat the view as read-only: because it joins a base table and a translation table, DML must be performed against OKL_INVC_LINE_TYPES_B and OKL_INVC_LINE_TYPES_TL directly, respecting the multi-language architecture. Reporting users should also account for the possibility that, if no translation row exists for the current session language, a given invoice line type may not be returned by the view.