Results for “internal_flag”

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

Overview

OKC_DELIVERABLE_TYPES_VL is a bilingual (MLS-compliant) validation view owned by the APPS schema within the OKC – Contracts Core product of Oracle E-Business Suite. It exposes the set of deliverable type definitions used throughout Oracle Contracts and related modules such as Project Contracts, Service Contracts, and Procurement Contracts. Deliverable types classify the tangible or intangible outputs that a contract obligates a party to produce — for example, a document, a service acceptance item, a milestone record, or a billing event.

The view presents one row per deliverable type code, combining descriptive, translatable text (name and description) with attributes held on the base table, including the INTERNAL_FLAG column referenced in the user's search. Its primary role is to serve as a user-facing read layer for reports, list-of-values (LOV) queries, and downstream integrations that require the deliverable type name in the session's language. Queries against the underlying _B table alone return only the code; the view resolves the language-specific label automatically.

Underlying Base Objects

The view is defined as a join between two documented base objects, both referenced through APPS synonyms:

• OKC_DELIVERABLE_TYPES_B — the base table holding non-translatable attributes: the primary key DELIVERABLE_TYPE_CODE, INTERNAL_FLAG, WHO audit columns, and OBJECT_VERSION_NUMBER (used for optimistic locking in the OAF/ADF framework).
• OKC_DELIVERABLE_TYPES_TL — the translation table holding NAME and DESCRIPTION for each supported language.

The join predicate links the two tables on DELIVERABLE_TYPE_CODE and constrains the translation row to the runtime session language via OKC_DELIVERABLE_TYPES_TL.LANGUAGE = USERENV('LANG'). Because USERENV('LANG') returns the language component only (e.g., "US"), the join returns exactly one translation row per deliverable type for the current session, giving the view its "VL" (view, language) designation. The view text also exposes the base table's ROW_ID rather than a surrogate primary key, reflecting its construction as an updatable-style validation view.

Key Columns

• DELIVERABLE_TYPE_CODE — the unique business key and primary identifier of the deliverable type; the column relied upon by foreign keys in contract deliverable and line tables.
• NAME — the language-specific display name resolved from the TL table.
• DESCRIPTION — the language-specific descriptive text.
• INTERNAL_FLAG — a flag on the base table indicating whether the deliverable type is reserved for internal (non-customer-facing) usage. This column is frequently queried to filter the LOV presented to end users, restricting selections to externally visible types.
• ROW_ID — the physical ROWID of the base table row.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns for change tracking.
• OBJECT_VERSION_NUMBER — the version token used to detect concurrent updates.

The columns START_DATE_ACTIVE, END_DATE_ACTIVE, and attribute/category columns sometimes associated with date-effective lookup views are not exposed by this view's documented text.

Common Use Cases and Queries

Typical usage includes populating LOVs for deliverable type selection on contract entry forms, joining deliverable records to their type names in reporting queries, and driving integration extracts. A representative query returning only externally visible types in the user's language is:

• SELECT deliverable_type_code, name, description FROM okc_deliverable_types_vl WHERE internal_flag = 'N' ORDER BY name;
• SELECT deliverable_type_code, name FROM okc_deliverable_types_vl WHERE internal_flag = 'Y'; — for administrative or internal-only reporting.
• SELECT d.deliverable_type_code, v.name FROM okc_deliverables d, okc_deliverable_types_vl v WHERE d.deliverable_type_code = v.deliverable_type_code; — a join to resolve deliverable type names in an output report.

Because the view relies on USERENV('LANG'), reports executed under a session language lacking a translation row will return no rows for that type; integrations should therefore confirm that the required language is installed and that translation rows exist in OKC_DELIVERABLE_TYPES_TL.