Results for “fii_fin_cat_type_assgns”

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

Overview

FII_FIN_CAT_TYPE_ASSGNS is a Financial Intelligence (FII) module table in Oracle E-Business Suite 12.1.1 and 12.2.2, owned by the FII schema. It stores the assignment of Financial Category types to Financial Categories, persisted in a denormalized form for query efficiency and reporting. In practical terms, the table acts as the definitive mapping between a given financial category and the category types that apply to it, and it drives how FII classification, aggregation, and hierarchical reporting logic resolves a category's type behavior. The primary key FII_FIN_CAT_TYPE_ASSGNS_PK is composed of the composite columns FIN_CATEGORY_ID and FIN_CAT_TYPE_CODE, indicating that a category may carry more than one type assignment while each (category, type) combination remains unique.

Per the heuristic Data Vault classification supplied with the object metadata, this table is characterized as standalone. That is a modeling suggestion rather than a physical constraint: within a Data Vault treatment, FII_FIN_CAT_TYPE_ASSGNS would not act as a hub or a link on the strength of its FK structure alone, though its composite natural key of FIN_CATEGORY_ID and FIN_CAT_TYPE_CODE would still qualify it as a candidate link between a financial category hub and a financial category type hub. The denormalized description confirms that descriptive attributes are carried alongside the key rather than being fully normalized into separate satellite structures.

Key Information Stored

The documented physical schema comprises eight columns. The most significant are:

• FIN_CATEGORY_ID — Identifier of the Financial Category to which a type assignment applies; part of the composite primary key.
• FIN_CAT_TYPE_CODE — The Financial Category type being assigned; the second component of the composite primary key.
• TOP_NODE_FLAG — Indicator designating whether the assignment corresponds to the top node of the category hierarchy; used to control hierarchy traversal and aggregation roll-ups.
• LAST_UPDATE_DATE — Timestamp of the most recent modification to the row, standard for EBS audit and incremental extraction.
• LAST_UPDATED_BY — User identifier responsible for the last update.
• CREATION_DATE — Timestamp when the assignment row was created.
• CREATED_BY — User identifier that created the row.
• LAST_UPDATE_LOGIN — Login identifier associated with the last update, used for audit traceability.

The surrogate primary key is FII_FIN_CAT_TYPE_ASSGNS_PK over (FIN_CATEGORY_ID, FIN_CAT_TYPE_CODE). The unique index FII_FIN_CAT_TYPE_ASSGNS_U1 covers the same column pair and is a business-key candidate, confirming that the combination of category and type code is unique. The audit columns (LAST_UPDATE_DATE, CREATED_BY, and related) follow standard EBS WHO column conventions and support change tracking and data-warehouse extraction.

Common Use Cases and Queries

Typical uses include: resolving which types apply to a financial category; identifying top-node assignments for hierarchy roll-ups; validating configuration completeness before running FII classification or reporting; and extracting incremental changes for downstream analytics.

Sample queries:

• All type assignments for a category: SELECT fin_cat_type_code, top_node_flag FROM fii_fin_cat_type_assgns WHERE fin_category_id = :p_category_id;
• Locating top nodes: SELECT fin_category_id FROM fii_fin_cat_type_assgns WHERE top_node_flag = 'Y';
• Incremental extraction: SELECT * FROM fii_fin_cat_type_assgns WHERE last_update_date >= :p_since;

Because the table is denormalized, it is well suited to direct reporting joins without intermediate lookups.

Related Objects

Although the mined relationship data classifies this table as standalone, the following objects are structurally significant in the same FII financial-category domain:

• FII_FIN_CATEGORIES (or equivalent Financial Category definition table) — joined on fin_category_id.
• Financial Category type lookup/definition — joined on fin_cat_type_code.
• FII_FIN_CAT_HIERARCHY (category hierarchy structures) — related through fin_category_id and the top node concept.
• FII_FIN_INTELLIGENCE / FII fact and reporting views — consume the assignments for classification and aggregation.
• General Ledger and Financials category references — reconciled through the shared fin_category_id identifier where FII categories align with GL or subledger classifications.

These joins rely on the composite key and the TOP_NODE_FLAG to produce accurate category-type reporting.