Search Results gmf_fiscal_policies




Overview
Explore in AI Chat

Overview

GMF_FISCAL_POLICIES is a Process Manufacturing Financials (GMF) configuration table that stores the fiscal and costing policy definitions applied at the legal-entity level. In Oracle EBS 12.1.1 and 12.2.2, the table acts as the single authoritative source that determines which cost basis, cost type, base currency, ledger, and default overhead rollup analysis codes Oracle Process Manufacturing uses when valuing inventory, computing manufacturing costs, and posting financial transactions. Because it drives downstream cost rollups and general ledger postings, records in this table must be maintained with care; incorrect or missing fiscal policy rows typically manifest as cost calculation failures or as unexpected account balances during the period close.

The ETRM metadata classifies this object heuristically as a standalone table in Data Vault terms, though it exhibits strong hub-like characteristics because the unique index GMF_FISCAL_POLICIES_U1 is defined on LEGAL_ENTITY_ID alone, making the legal entity the natural business key. A Data Vault model would therefore present GMF_FISCAL_POLICIES as a hub keyed on legal entity, with the remaining descriptive and reference columns (currency, ledger, cost basis, cost type) attached either directly or through link relationships.

Key Information Stored

Although the documented physical schema spans 48 columns, a much smaller subset carries the substantive business meaning. The most important columns include:

There is no separately documented surrogate primary key; the unique index on LEGAL_ENTITY_ID effectively functions as the identifying key.

Common Use Cases and Queries

Typical use cases include validating that a fiscal policy exists before running cost rollups, retrieving the active cost type or base currency for a legal entity, and auditing policy configuration across a multi-entity installation.

A straightforward lookup by legal entity:

  • SELECT legal_entity_id, ledger_id, base_currency_code, cost_basis, cost_type_id FROM gmf_fiscal_policies WHERE legal_entity_id = :p_entity AND delete_mark = 0;

A join to resolve the human-readable cost type name:

  • SELECT f.legal_entity_id, c.cost_type FROM gmf_fiscal_policies f, cst_cost_types c WHERE f.cost_type_id = c.cost_type_id AND f.delete_mark = 0;

For reporting, joining to FV_LEGAL_ENTITIES supplies the entity name and operating unit context, while joining to GL ledgers provides the ledger name and chart of accounts.

Related Objects

The table participates in two documented foreign-key relationships and interacts with several surrounding objects:

  • FV_LEGAL_ENTITIES — joined on LEGAL_ENTITY_ID; provides legal entity attributes.
  • CST_COST_TYPES — joined on COST_TYPE_ID; supplies valid cost type definitions.
  • GL_LEDGERS / GL_LEDGER_SET_NORM_ASSIGN — referenced through LEDGER_ID for accounting context.
  • FND_CURRENCIES — validates BASE_CURRENCY_CODE.
  • MTL_DEFAULT_CATEGORY_SETS and component class tables — associated with MTL_CMPNTCLS_ID and DEFAULT_OVH_CMPNTCLS_ID.
  • GMF_CM_CST_ROLLUPS and cost rollup APIs — consume the policy row to determine cost basis and cost type during rollup processing.

Because the classification is standalone, no dependent satellite or link table is documented in the schema; referential integrity is maintained directly through the two foreign keys listed above.