Results for “fiibv_ap_rlse_release_type_lcv”

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

Overview

FIIBV_AP_RLSE_RELEASE_TYPE_LCV is a base view owned by the APPS schema in Oracle E-Business Suite, classified under the FII (Financial Intelligence) product family. In the ETRM 12.2.2 documentation it carries a status of VALID and is described as the base view for the Release Type level of the Release dimension. Its purpose is to expose a normalized, star-schema-friendly representation of the release types used within Oracle Payables, so that Financial Intelligence and Enterprise Data Warehouse (EDW) style reporting can integrate with the payment release dimension without depending directly on the raw lookup tables.

The view sits at the "Release Type" level of the Release dimension hierarchy. Rather than requiring report authors to join FND_LOOKUP_VALUES to AP_LOOKUP_CODES and filter for the correct lookup type, the view pre-applies these joins and filters, returning a clean list of release types with surrogate key columns and standardized audit attributes. This makes it consistent with other FIIBV views that follow the same convention for dimensions such as Payment Terms or Payment Formats.

Underlying Base Objects

The view text is defined over two base objects:

• AP_LOOKUP_CODES (aliased LC) — the Oracle Payables lookup codes table, which supplies the lookup code, displayed field, description, and start date.
• FND_LOOKUP_VALUES (aliased FND) — the shared Oracle Application Object Library lookup values table, used as the validated join target against AP_LOOKUP_CODES.

The join is performed on three columns simultaneously: LOOKUP_TYPE, LOOKUP_CODE, and the relationship between LC.DISPLAYED_FIELD and FND.MEANING. A constant filter restricts the result set to LOOKUP_TYPE = 'HOLD TYPE', and a further predicate keeps only lookup codes matching the pattern '%RELEASE%', or exactly 'SUFFICIENT INFORMATION'. This is why the view is described as the release-type level of the Release dimension: the Payables release types are modeled as a logical subset of hold types. A cross join to EDW_INSTANCE.GET_CODE provides the INSTANCE column, and no referential base objects are documented beyond the two lookup tables above.

Key Columns

• RELEASE_TYPE_PK — the primary key at this level, taken from LC.LOOKUP_CODE. It uniquely identifies each release type.
• ALL_FK — a literal 'ALL' foreign key, providing a degenerate "all values" parent used to anchor the dimension to its ALL level.
• INSTANCE — SUBSTRB(EDW_INSTANCE.GET_CODE,1,40), identifying the source EBS instance.
• NAME and RELEASE_TYPE — both sourced from LC.DISPLAYED_FIELD, giving the presentation name of the release type.
• DESCRIPTION — the lookup description.
• LAST_UPDATE_DATE and CREATION_DATE — derived from NVL(LC.START_DATE_ACTIVE, SYSDATE-1), so both reflect the effective start date of the lookup.
• DELETION_DATE and RELEASE_TYPE_DP — explicitly returned as NULL placeholders so downstream ETL can treat all release types as open and current.
• _DF:FND:FND_COMMON_LOOKUPS:FND and the metadata marker "_DF:FND:_EDW" — Data Foundation descriptors that drive FII/EDW dimension loading.

Common Use Cases and Queries

The most common use is to populate or validate the Release Type dimension in a financial data warehouse. A simple query returns all release types:

• SELECT RELEASE_TYPE_PK, NAME, RELEASE_TYPE, DESCRIPTION FROM APPS.FIIBV_AP_RLSE_RELEASE_TYPE_LCV;

This is typically used for dimension extraction, joining to fact tables on RELEASE_TYPE_PK, or for reconciliation to confirm that all expected Payables release types exist. A second pattern filters to stable release types for historical analysis, and a third joins the view to payment or release fact tables from FIIBV_AP_RLSE_* objects to build a complete Release dimension report.