Results for “okl_invoice_mssgs_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKL_INVOICE_MSSGS_V is a standard Oracle E-Business Suite view owned by the APPS schema in the OKL (Lease and Finance Management) product family. As documented in the ETRM metadata, the view exposes standard messages intended to be printed on lease and finance invoices. It presents a bilingual, organization-aware list of invoice message definitions, combining the base transactional attributes held in OKL_INVOICE_MSSGS_B with the translatable, language-specific text stored in OKL_INVOICE_MSSGS_TL. The view is marked VALID and is defined in both Oracle EBS 12.1.1 and 12.2.2.

Because it encapsulates the join between the base and translation tables and filters on the runtime language, the view is the preferred access point for reporting, integration, and concurrent programs that need to retrieve invoice message text already resolved for the session language. This avoids re-implementing the language join in every consumer. The presence of a PKG_NAME column reflects that some invoice messages can be dynamically generated by a PL/SQL package and procedure rather than being entirely static text.

Underlying Base Objects

The documented metadata lists the following referenced base objects:

• OKL_INVOICE_MSSGS_B (SYNONYM) — the base table holding non-translatable invoice message attributes, aliased IMSB in the view text.
• OKL_INVOICE_MSSGS_TL (SYNONYM) — the translation table holding language-specific message text, aliased IMST.
• MO_GLOBAL (PACKAGE) — the multi-org initialization package referenced in the view's dependency chain, used to set up organization context and MO security for the session.

The view definition joins the two tables on ID (IMSB.ID = IMST.ID) and restricts the translation row to the current session language using the condition IMST.LANGUAGE = USERENV('LANG'). Effectively, the view presents one row per invoice message per language, with base attributes such as ORG_ID, PRIORITY, START_DATE, END_DATE, PKG_NAME, and PROC_NAME merged with the translatable NAME, MESSAGE_TEXT, DESCRIPTION, and SFWT_FLAG.

Key Columns

• ROW_ID — the ROWID of the base table row.
• ID — primary identifier shared between the base and translation tables.
• ORG_ID — operating unit identifier; drives multi-org filtering.
• OBJECT_VERSION_NUMBER — optimistic locking version for the row.
• NAME / DESCRIPTION / MESSAGE_TEXT — the translatable identity and the actual text printed on invoices.
• SFWT_FLAG — flag controlling whether the message text is treated as a "soft" (no word-wrap) message or subject to wrapping.
• PRIORITY — ordering value determining the sequence in which messages appear on an invoice.
• START_DATE / END_DATE — effective period during which the message is active.
• PKG_NAME / PROC_NAME — the PL/SQL package and procedure used to generate message text dynamically, if applicable.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1..ATTRIBUTE15 — descriptive flexfield segments.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

The user search term "pkg_name" maps directly to the PKG_NAME column, which identifies the package responsible for producing the message content at invoice print time.

Common Use Cases and Queries

Typical uses include reporting on the messages configured for invoices, verifying the package used to generate dynamic messages, and building integration extracts of invoice text. A simple query listing active messages ordered by priority might read:

SELECT id, name, message_text, priority, pkg_name, proc_name FROM okl_invoice_mssgs_v WHERE org_id = :org_id AND TRUNC(SYSDATE) BETWEEN start_date AND end_date ORDER BY priority;

To locate messages driven by a named package, filter on PKG_NAME, for example:

SELECT id, name, pkg_name, proc_name FROM okl_invoice_mssgs_v WHERE pkg_name IS NOT NULL;

Because translation is resolved at query time, no additional language join is required by the caller, making the view suitable for both on-line report queries and ETL extraction into downstream systems.