Search Results okl_invoice_types_v




Overview
Explore in AI Chat

Overview

The OKL_INVOICE_TYPES_V view is a seeded, APPS-owned database object supplied by the Oracle Leasing and Finance Management (OKL) module, part of the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 technology stacks. The view presents the definition of an invoice type, which determines how transactions, stream types, and cash flows are grouped onto a specific invoice. In other words, the invoice type controls the aggregation logic applied when OKL generates invoices from contract streams. Because it is a view rather than a table, it exposes a read-only, language-aware projection of the underlying invoice type configuration. Reporting tools, concurrent programs, and integration layers query this view to resolve invoice type codes, descriptions, and grouping behaviour without needing to join the base and translation tables directly. The view is documented as VALID and is intended for reference and read access within the OKL application schema.

Underlying Base Objects

The view is defined over two base objects, both referenced in the ETRM metadata as synonyms accessed by APPS:

  • OKL_INVOICE_TYPES_B — the base (non-translated) table holding the invoice type identifier, grouping flags, foreign key references, descriptive flexfield attribute columns, and standard who-columns.
  • OKL_INVOICE_TYPES_TL — the translation table holding the language-dependent NAME and DESCRIPTION columns, along with the SFWT_FLAG that indicates whether the row requires translation.

The view joins these on ITYB.ID = ITYT.ID and filters ITYT.LANGUAGE = USERENV('LANG'), so each query returns only the translation matching the current session language. It also exposes the ROWID of the base row for tools that require it. This join pattern is the standard Oracle multi-language ("_B"/"_TL") design, and the view therefore inherits the existing base and translation rows rather than duplicating them.

Key Columns

  • ROW_ID / ID — the base row identifier and the surrogate primary key of the invoice type.
  • OBJECT_VERSION_NUMBER — optimistic locking column used by the OKL framework when records are updated.
  • NAME / DESCRIPTION — the translated invoice type name and description sourced from OKL_INVOICE_TYPES_TL.
  • SFWT_FLAG — translation flag indicating whether the row requires supplemental translation handling.
  • INF_ID — foreign key linking the invoice type to its associated invoice format or grouping definition.
  • GROUP_ASSET_YN — indicates whether assets are grouped onto the invoice.
  • GROUP_BY_CONTRACT_YN — indicates whether invoice lines are grouped by contract.
  • ATTRIBUTE_CATEGORY / ATTRIBUTE1–15 — descriptive flexfield columns for customer-defined invoice type attributes.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit (who) columns.

Common Use Cases and Queries

Typical uses include LOV (list of values) population in OKL setup forms, validation of invoice type codes during invoice generation, and reporting on grouping behaviour per invoice type. A simple lookup of all invoice types with their grouping flags is:

SELECT id, name, description, group_asset_yn, group_by_contract_yn FROM apps.okl_invoice_types_v ORDER BY name;

To join the view to invoice-related data, developers relate on the invoice type ID, for example: SELECT i.invoice_number, t.name invoice_type FROM apps.okl_invoices i, apps.okl_invoice_types_v t WHERE i.invoice_type_id = t.id; Reporters should always query the view rather than the base tables so that the correct language translation is applied automatically, and should avoid DML through the view, as it is intended for read-only reference within the EBS 12.1.1 and 12.2.2 environments.