Search Results postable_flag




Overview
Explore in AI Chat

Overview

FII_AP_RLSE_RELEASE_LCV is an Oracle EBS Applications (APPS) view that exposes release-related reference data used by the Financial Intelligence (FII) / Oracle Financials Intelligence components in Oracle E-Business Suite 12.1.1 and 12.2.2. The object name suffix "LCV" indicates a "List of Values" style view — a derived, presentation-oriented query typically consumed by Oracle Forms LOVs, concurrent program parameters, or downstream ETL/reporting layers that need a normalized, joined representation of release records against the base release entity.

The view presents a single denormalized row per release, combining identity columns (RELEASE_PK, RELEASE_TYPE_FK, INSTANCE, NAME, RELEASE_NAME), status and control flags (USER_RELEASEABLE_FLAG, USER_UPDATEABLE_FLAG, POSTABLE_FLAG, INACTIVE_DATE), descriptive text (DESCRIPTION), and audit columns (LAST_UPDATE_DATE, CREATION_DATE). It also exposes several placeholder NULL columns (DELETION_DATE, RELEASE_DP, USER_ATTRIBUTE1–5) to preserve a fixed column contract expected by the applications that reference it. This pattern is common in EBS where an LOV view maintains interface stability while underlying storage evolves.

Underlying Base Objects

The documented view text selects exclusively from FIIBV_AP_RLSE_RELEASE_LCV, which in turn resolves to the base release tables within the FII application schema. The ETRM metadata for this object does not enumerate any referenced base objects, and the view is defined with no explicit join in the exposed text — the joins and business logic reside beneath the FIIBV_AP_RLSE_RELEASE_LCV layer. Consequently, the tables of record (release definitions, release types, and instance context) are abstracted away from direct callers.

Because the view is defined over a single underlying FIIBV source, it inherits the security and definition of that layer. In Oracle EBS, such views are often created with a synonym under the APPS schema to allow access across product schemas without exposing the base table grants directly. This indirection also isolates consumers from changes to the underlying release data model.

Key Columns

  • RELEASE_PK — Primary key identifying the release record.
  • RELEASE_TYPE_FK — Foreign key linking the release to its release type definition.
  • INSTANCE — Instance context for the release record.
  • NAME / RELEASE_NAME — Internal and user-facing names for the release.
  • USER_RELEASEABLE_FLAG — Controls whether the release can be selected/released by a user.
  • USER_UPDATEABLE_FLAG — Controls whether the release definition is user-maintainable. This is the column most commonly targeted by searches for "user_updateable_flag", since it governs editability of release setup data.
  • POSTABLE_FLAG — Indicates whether the release is eligible for posting.
  • INACTIVE_DATE — Date after which the release is no longer active.
  • DESCRIPTION — Free-text description of the release.
  • LAST_UPDATE_DATE / CREATION_DATE — Standard audit columns.
  • DELETION_DATE, RELEASE_DP, USER_ATTRIBUTE1–5 — Placeholder columns returned as NULL to satisfy a fixed column contract.

Common Use Cases and Queries

The view is typically queried to populate LOVs, validate user input against the USER_UPDATEABLE_FLAG or USER_RELEASEABLE_FLAG controls, and drive reporting on release configuration. A representative query retrieving user-updateable releases is shown below.

SELECT release_pk,
       release_name,
       release_type_fk,
       user_updateable_flag,
       user_releaseable_flag,
       postable_flag
  FROM apps.fii_ap_rlse_release_lcv
 WHERE user_updateable_flag = 'Y'
   AND (inactive_date IS NULL OR inactive_date > SYSDATE);

Because the view filters and joins are encapsulated below the FIIBV layer, queries against this object remain stable across both 12.1.1 and 12.2.2. Developers should avoid relying on the NULL placeholder columns as functional data and instead treat them purely as interface scaffolding.