Search Results okl_invoice_formats_v




Overview
Explore in AI Chat

Overview

OKL_INVOICE_FORMATS_V is a conventional (non-materialized) Oracle EBS view owned by the APPS schema within the OKL — Leasing and Finance Management product family. Its documented purpose is to describe the presentation of invoice information, providing a language-resolved, operating-unit-enriched read interface over the invoice format configuration data maintained by the Oracle Lease and Finance Management module. In release 12.1.1 and 12.2.2 the view is shipped with a status of VALID and is installed as part of the standard APPS database objects.

Invoice formats in OKL govern how lease and finance contract invoices are rendered — that is, the visual structure, labeling, and layout applied when invoice data is presented to customers. Because that configuration is stored across a translation table, a base table, and the HR operating unit hierarchy, the view exists to present a single, joined, language-filtered result set that reports, concurrent programs, and integration extracts can consume directly without reconstructing the join logic themselves. Its most common role is as a read-only reference source: report queries join to it to resolve a format name and description from a foreign key, and integration routines use it to audit which formats are active for a given operating unit and date range.

Underlying Base Objects

The view text joins three documented base objects:

Because the driving table is OKL_INVOICE_FORMATS_B and the translation join is an inner join constrained by language, a format lacking a translation row in the session language will not appear. Similarly, an ORG_ID without a matching HR operating unit is excluded by the inner join.

Key Columns

  • ID — primary identifier of the invoice format, replicated from the base table and used as the join key to the translation table.
  • NAME / DESCRIPTION — the language-specific format name and description retrieved via the translation join.
  • SFWT_FLAG — the standard "seed data / free-form?" style flag carried on the translation record, used to distinguish seeded formats from user-defined ones.
  • CONTRACT_LEVEL_YN — indicates whether the format applies at the contract level rather than at a lower granularity.
  • START_DATE / END_DATE — the effective date window during which the format is valid; these are the primary predicates for point-in-time lookups.
  • ILT_ID — reference to the invoice line type associated with the format.
  • ORG_ID / OPERATING_UNIT — the operating unit identifier and its resolved display name.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield context and segment values.
  • OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, ROW_ID — standard concurrency and audit columns exposed for downstream processing.

Common Use Cases and Queries

Typical uses include validating that a format is active on a given date before invoice generation, resolving a format name for reporting, and auditing formats by operating unit. All queries are normally executed with the APPS schema or a reporting account granted SELECT on the view, and with the FND language environment set correctly, since the translation join depends on USERENV('LANG').

  • Active formats for an operating unit: 
    SELECT id, name, contract_level_yn, start_date, end_date
FROM   apps.okl_invoice_formats_v
WHERE  org_id = :p_org_id
AND    TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, TRUNC(SYSDATE));
  • Resolving a format name for a report: 
    SELECT name, description, operating_unit
FROM   apps.okl_invoice_formats_v
WHERE  id = :p_format_id;
  • Listing seeded versus user-defined formats: 
    SELECT id, name, sfwt_flag
FROM   apps.okl_invoice_formats_v
ORDER  BY sfwt_flag, name;

Because the view is a simple join without aggregation, it supports indexed access on ID and ORG_ID and can be safely embedded in larger reporting queries. Consumers should treat it strictly as a read interface to the underlying B and TL tables.