Results for “fiibv_ap_rlse_release_lcv”

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

Overview

FIIBV_AP_RLSE_RELEASE_LCV is a base view in the Oracle E-Business Suite Financial Intelligence (FII) product family, owned by the APPS schema. It functions as the source object for the Release level of the Release dimension within the Financial Intelligence data model, which supports extract, transform, and load (ETL) processing for the Oracle Business Intelligence and Enterprise Data Warehouse (EDW) reporting stack. In releases 12.1.1 and 12.2.2, this view presents release-type hold codes from Oracle Payables as conformed dimension members, allowing downstream warehouse objects and analytical dashboards to resolve a surrogate or natural key for each release definition. Because it is a view rather than a base table, it introduces no physical storage and derives its rows at runtime from transactional and lookup tables in the Payables and Application Object Library schemas. Its status is VALID in the APPS schema, and its column RELEASE_DP carries the descriptor marker "_DF:FND:FND_COMMON_LOOKUPS:FND", indicating that the dimension attribute is sourced from the FND_COMMON_LOOKUPS lookup foundation.

Underlying Base Objects

The ETRM metadata records no separately documented base objects; the view text itself defines its dependencies over three tables joined by lookup semantics:

• AP_HOLD_CODES (AHC) — the Payables hold and release code definitions. This is the primary driver of the row set and supplies the release primary key, flags, and date attributes.
• AP_LOOKUP_CODES (ALC) — the Payables lookup codes repository, providing the displayed field name, release name, and description text.
• FND_LOOKUP_VALUES (FND) — the common lookups table in Application Object Library, used to validate that the lookup type, code, and meaning agree across the Payables and common lookup definitions.

The join predicates restrict output to records where the Payables lookup code matches the common lookup code and displayed field matches the common meaning, and where the hold type contains the string "RELEASE" or equals "SUFFICIENT INFORMATION", with the lookup type fixed to "HOLD CODE".

Key Columns

• RELEASE_PK — natural key derived from AP_HOLD_CODES.HOLD_LOOKUP_CODE; the release dimension primary key.
• RELEASE_TYPE_FK — foreign key to the release type, sourced from AP_HOLD_CODES.HOLD_TYPE.
• INSTANCE — EDW instance identifier, a substring of EDW_INSTANCE.GET_CODE limited to 40 bytes.
• NAME / RELEASE_NAME — the displayed lookup field value used for the release name.
• USER_RELEASEABLE_FLAG, USER_UPDATEABLE_FLAG, POSTABLE_FLAG — Payables control flags governing whether users can release, update, or post holds.
• INACTIVE_DATE, LAST_UPDATE_DATE, CREATION_DATE — standard effective-dating and audit attributes.
• DESCRIPTION — descriptive text from the Payables lookup code.
• DELETION_DATE, RELEASE_DP — placeholders; DELETION_DATE is NULL and RELEASE_DP holds the FND common lookups descriptor tag.

Common Use Cases and Queries

The view is typically consumed by FII ETL mappings that populate the Release dimension used in Payables spend, hold, and payment analytics. A representative query lists active release codes:

• SELECT release_pk, release_name, release_type_fk, postable_flag, inactive_date FROM fiibv_ap_rlse_release_lcv WHERE inactive_date IS NULL;
• SELECT release_pk, release_name FROM fiibv_ap_rlse_release_lcv WHERE release_type_fk LIKE '%RELEASE%';
• SELECT release_type_fk, COUNT(*) FROM fiibv_ap_rlse_release_lcv GROUP BY release_type_fk;

Validation of a specific release, joined to invoice holds for reconciliation, is also common. Performance depends on the underlying lookup indexes on AP_LOOKUP_CODES and FND_LOOKUP_VALUES.