Search Results fii_com_pmv_agrt_nodes

Overview

The FII_COM_PMV_AGRT_NODES table belongs to the FII (Financial Intelligence) product family, a legacy analytical component within Oracle E-Business Suite. Per the ETRM metadata, the module is classified as Obsolete, and the table carries the implementation status "Not implemented in this database." This status indicates that the object is documented in the ETRM repository for historical and schema-compatibility reference only, and it should not be expected to hold data in a standard 12.1.1 or 12.2.2 environment. Its described purpose is narrow and specific: it stores whether a given aggregation node is aggregated and available for selection through a "viewby" dimension.

From a heuristic Data Vault modeling perspective, the mined FK structure classifies this object as standalone, suggesting a structure closer to a hub with attached descriptive attributes or a reference/lookup satellite. There is no documented parent-child FK chain beyond the single outward reference to PN_COMPANIES_ALL, meaning the table does not behave as a transactional link between multiple business entities. Its role is effectively an aggregation control or flag registry for a Financial Intelligence aggregation hierarchy.

Key Information Stored

The documented physical schema consists of 8 columns. The most significant of these are summarized below.

• COMPANY_ID — The sole documented foreign key, referencing PN_COMPANIES_ALL. This identifies the company or organization context to which the aggregation node belongs and is the primary candidate for a business key in any reconstructed model.
• FOR_VIEWBY_FLAG — Indicates whether the node is exposed as an available "viewby" option in the Financial Intelligence UI. This is the core functional flag described by the table's stated purpose.
• AGGREGATED_FLAG — Indicates whether the node has been aggregated and is therefore valid for analysis or display. Together with FOR_VIEWBY_FLAG, it governs node availability.
• LAST_UPDATE_DATE, LAST_UPDATED_BY — Standard EBS audit attributes tracking when and by whom the row was last modified.
• CREATION_DATE, CREATED_BY — Standard EBS audit attributes recording initial row creation.
• LAST_UPDATE_LOGIN — Records the login/session that performed the most recent update, supporting audit traceability.

Notably, no standalone surrogate primary key column is documented among the 8 columns. The metadata supplied does not list a unique index definition, so the combination of COMPANY_ID plus the aggregation context (as encoded in the flags and any implicit node identifier) should be treated as the candidate business key. In practice, any reconstruction should assume a composite key rather than a single surrogate.

Common Use Cases and Queries

Because the object is obsolete and not implemented, practical usage is limited to migration analysis, schema archaeology, and compatibility checks during upgrades from 12.1.1 to 12.2.2. Where the table does exist in a historical or customized instance, the primary use case is determining node availability for the viewby dimension. A representative query pattern would be:

• Filtering nodes available for viewby: SELECT COMPANY_ID FROM FII_COM_PMV_AGRT_NODES WHERE FOR_VIEWBY_FLAG = 'Y'
• Identifying nodes already aggregated: SELECT COMPANY_ID FROM FII_COM_PMV_AGRT_NODES WHERE AGGREGATED_FLAG = 'Y'
• Audit inspection: selecting CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE to trace configuration changes.
• Company-scoped reporting: joining to PN_COMPANIES_ALL on COMPANY_ID to resolve company names for aggregation readiness reporting.

Related Objects

The documented relationship data identifies a single outward reference, which constrains the related-object landscape:

• PN_COMPANIES_ALL — Referenced by COMPANIES_ID via the FK FII_COM_PMV_AGRT_NODES.COMPANY_ID → PN_COMPANIES_ALL; the principal join target for company resolution.
• Other FII_COM_PMV_* tables — Sibling objects in the Financial Intelligence aggregation framework that share the COM_PMV naming prefix and logically participate in the same node/aggregation model.
• FII application schema objects — General FII tables and views that consume node availability flags for analytical presentation.

Given the standalone classification and the obsolete status, no further documented dependencies should be assumed; integrators should verify any additional relationships directly against the target instance before relying on them.