Results for “std_note_type”

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

Overview

OKE_STD_NOTES_V is an APPS-owned reporting view in Oracle E-Business Suite 12.1.1 and 12.2.2 that exposes the seeded standard note type lookup values used by Oracle Contracts (OKE). Rather than storing note data itself, the view flattens a subset of the Oracle Application Object Library (FND) lookup framework into a compact, contract-specific projection. Its definition applies two fixed filters to the underlying lookup view: LOOKUP_TYPE = 'STD_NOTE_TYPE' and VIEW_APPLICATION_ID = 777, where 777 is the application identifier for Oracle Contracts. This design means the view returns only those lookup codes registered as standard note types for the Contracts product, isolating them from the far larger pool of FND lookup values that coexist in the shared FND_LOOKUP_VALUES_VL object.

The view is read-only in practice and is intended for reporting, validation, and integration rather than for direct maintenance. Because lookup values are maintained through the Application Developer responsibility or through concurrent programs that load lookup data, the view acts as a stable query surface over configuration data that is otherwise buried in generic FND tables.

Underlying Base Objects

The documented base object for OKE_STD_NOTES_V is FND_LOOKUP_VALUES_VL, itself a view. OKE_STD_NOTES_V therefore layers a second view on top of an existing one, adding the STD_NOTE_TYPE and VIEW_APPLICATION_ID filters. FND_LOOKUP_VALUES_VL exposes translated lookup meanings and descriptions alongside the base lookup definition, which is why the OKE view can present MEANING and DESCRIPTION without joining FND_LOOKUP_TYPES or language tables directly. In 12.2.2 the referenced object remains FND_LOOKUP_VALUES_VL, so the view inherits the same multi-language behavior and the same columns as the underlying FND object.

Key Columns

• LOOKUP_CODE — The internal code identifying each standard note type; this is the value stored on contract or note records that reference a standard note type.
• MEANING — The translatable display name shown to users for the corresponding lookup code.
• DESCRIPTION — Optional descriptive text for the note type, also translatable.
• START_DATE_ACTIVE — The date from which the lookup value becomes effective.
• END_DATE_ACTIVE — The date on which the lookup value is retired; NULL indicates an open-ended value.
• ENABLED_FLAG — Indicates whether the lookup value is currently active (Y) or disabled (N).

Together these columns give both the machine-readable key and the user-facing label for each standard note type, plus the effective-dating and enablement controls that govern whether the value should be offered.

Common Use Cases and Queries

Typical uses include populating LOVs in custom contract pages, validating that a stored LOOKUP_CODE is still an enabled standard note type, and generating reports that translate stored codes into readable meanings. A basic listing of all current values can be produced with:

• SELECT lookup_code, meaning, description FROM apps.oke_std_notes_v ORDER BY meaning;

To restrict output to values that are presently active, the effective-dating and enablement columns are used as follows:

• SELECT lookup_code, meaning FROM apps.oke_std_notes_v WHERE enabled_flag = 'Y' AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, TRUNC(SYSDATE)) AND NVL(end_date_active, TRUNC(SYSDATE));

A third common pattern joins the view to contract note tables to resolve stored codes, for example linking a note's type code to its meaning through oke_std_notes_v.lookup_code so that reports display descriptions rather than raw codes. Because the view already applies the STD_NOTE_TYPE and application filters, queries do not need to repeat those predicates, which reduces the risk of retrieving unrelated FND lookup values.