Search Results user_updateable_flag

Overview

FII_AP_RLSE_RELEASE_LCV is a Financial Intelligence (FII) collection view representing the Release level of the Release dimension within the Oracle E-Business Suite. In the Oracle EBS 12.1.1 and 12.2.2 release streams, this object belongs to the FII (Financial Intelligence) product family, which supplied the extract, staging, and dimensional structures used by Oracle's financial analytics and data warehouse offerings. The view is documented as obsolete in current ETRM metadata and is explicitly marked in the documentation as "Not implemented in this database."

Functionally, the view exposes a normalized set of Release dimension attributes—identifiers, descriptive names, posting and updateable flags, and audit columns—so that downstream ETL processes, FII collection programs, and dimensional loads can consume release reference data in a consistent shape. Its "LCV" naming suffix denotes a collection view (a level or load collection view) used within the FII architecture rather than an end-user reporting view.

Underlying Base Objects

According to the documented view text, FII_AP_RLSE_RELEASE_LCV is defined over a single underlying object, FIIBV_AP_RLSE_RELEASE_LCV. The metadata records no other referenced base objects. This corresponds to the standard FII layering pattern, in which a collection view (typically a "BV" or "_LCV" object) sits one layer above the FII base table and is in turn wrapped by a level-specific collection view.

Notably, the SELECT list supplies literal NULL values for DELETION_DATE, RELEASE_DP, and USER_ATTRIBUTE1 through USER_ATTRIBUTE5, projecting columns that are not populated by the underlying source. This technique preserves a uniform column contract across dimensional collection views even when the source lacks those attributes. The view also passes through audit columns (CREATION_DATE, LAST_UPDATE_DATE) drawn from the source.

Because the object is documented as obsolete and not implemented, no physical instantiation or dependency chain can be assumed in a given environment; it exists in ETRM only as historical architectural metadata.

Key Columns

• RELEASE_PK — Primary key of the Release dimension member; the surrogate identifier used in FII fact and dimension joins.
• RELEASE_TYPE_FK — Foreign key identifying the release type to which the member belongs.
• INSTANCE / NAME / RELEASE_NAME — Descriptive identifiers and labels for the release member.
• USER_RELEASEABLE_FLAG / USER_UPDATEABLE_FLAG — Control flags indicating whether the release can be released or updated by users.
• POSTABLE_FLAG — Indicates whether the release is valid for posting to the general ledger.
• INACTIVE_DATE — Date on which the release becomes inactive, supporting slowly changing dimension logic.
• DESCRIPTION — Text description of the release.
• CREATION_DATE / LAST_UPDATE_DATE — Standard audit columns.
• DELETION_DATE, RELEASE_DP, USER_ATTRIBUTE1–5 — Placeholder columns projected as NULL for schema consistency.

Common Use Cases and Queries

In FII collection routines, this view would have been referenced when loading or reconciling the Release dimension, validating postable and active releases, and mapping release members to their type hierarchies. Typical diagnostic queries include:

• Listing valid, postable releases: SELECT RELEASE_PK, RELEASE_NAME, RELEASE_TYPE_FK FROM FII_AP_RLSE_RELEASE_LCV WHERE POSTABLE_FLAG = 'Y' AND (INACTIVE_DATE IS NULL OR INACTIVE_DATE > SYSDATE);
• Checking user-maintainable members: SELECT RELEASE_PK, NAME, USER_UPDATEABLE_FLAG FROM FII_AP_RLSE_RELEASE_LCV WHERE USER_RELEASEABLE_FLAG = 'Y';
• Auditing recent changes: SELECT RELEASE_PK, LAST_UPDATE_DATE FROM FII_AP_RLSE_RELEASE_LCV WHERE LAST_UPDATE_DATE >= TRUNC(SYSDATE) - 30;

Because the object is obsolete and unimplemented in documented environments, these patterns should be treated as historical reference; in 12.1.1 or 12.2.2, equivalent Release dimension data should be sourced from the current supported FII or subledger objects.