Results for “gl_plcy_mst”

50+ results




Overview
Explore in AI Chat

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

Overview

GMF.GL_PLCY_MST is the fiscal policy master table in Oracle Process Manufacturing Financials (GMF). It stores the General Ledger attributes that define how a process manufacturing company or legal entity posts financial transactions. Each row represents a fiscal policy for a single operating company, and together these attributes drive GL account derivation, currency handling, cost method selection, and calendar/period determination for the organization.

In Oracle EBS 12.1.1 and 12.2.2, the table resides in the GMF schema and is documented in ETRM with 69 columns and a single unique index, GL_PLCY_MST_PK, keyed on CO_CODE. From a Data Vault modeling perspective, the heuristic classification is hub-leaning: CO_CODE (the operating company/legal entity identifier) behaves as a business key hub, with the remaining descriptive fiscal attributes (currency, ledger, calendar, cost method, flags) functioning as satellite-type descriptive data. The table also carries multi-foreign-key dependencies into GL and CM masters, so it acts as an integration point between process manufacturing costing and Oracle General Ledger configuration.

Key Information Stored

The most operationally significant columns fall into four groups:

CO_CODE is the surrogate-to-natural key: while it is declared the primary key, it is simultaneously the join column into nearly every dependent GL policy configuration table, making it the true business key candidate.

Common Use Cases and Queries

Reporting and integration scenarios typically resolve the fiscal policy for a company or legal entity before posting or validating GL activity. A representative lookup:

  • Retrieve fiscal policy attributes for a company: SELECT co_code, base_currency_code, primary_ledger_code, sob_id, gl_cost_mthd, cost_basis, number_of_open_periods FROM gmf.gl_plcy_mst WHERE co_code = :p_co_code;
  • Identify the base currency and set of books for multi-org reporting: join GL_PLCY_MST to GL_LDGR_MST on primary_ledger_code, filtered by operating_unit or org_id.
  • Validate cost method and calendar assignments before running OPM cost rollups or period-close: join to CM_MTHD_MST and CM_CLDR_DTL on the revaluation method and calendar columns.
  • Legal-entity migration analysis: SELECT co_code, legal_entity_id, migrated_ind, new_le_flag, new_le_cost_mthd_code FROM gmf.gl_plcy_mst WHERE migrated_ind = 'N';
  • Cross-check all subledger configuration for a company by driving from GL_PLCY_MST.CO_CODE into GL_ACCT_MAP, GL_EVNT_PLC, and GL_LEDG_MAP.

Because CO_CODE is shared across a large family of configuration tables, any query that starts at the company level can fan out to every dependent fiscal-policy rule.

Related Objects

The following are the most significant related objects and their join columns:

  • SY_ORGN_MST / SY_ORGN_MST_B — operating company master; joined on GL_PLCY_MST.CO_CODE = SY_ORGN_MST.CO_CODE.
  • GL_LDGR_MST — ledger definition; joined on PRIMARY_LEDGER_CODE.
  • GL_CURR_MST — currency definition; joined on BASE_CURRENCY_CODE.
  • FV_LEGAL_ENTITIES — legal entity source; joined on LEGAL_ENTITY_ID (legal-entity releases).
  • GL_ACCT_MAP, GL_ACCT_MST, GL_ACCU_MAP — account mapping and accumulation rules; each references CO_CODE back to GL_PLCY_MST.
  • GL_PLCY_LGR, GL_PLCY_SEG, GL_PLCY_SYS — ledger, segment, and system policy detail tables that depend on CO_CODE.
  • GL_EVNT_PLC, GL_SUBR_LED, GL_SUBR_TST — event posting, subledger, and test configuration keyed by CO_CODE.
  • CM_MTHD_MST, CM_CLDR_DTL, CM_ALYS_MST, CM_CMPT_MST — process manufacturing cost method, calendar, analysis, and cost component masters referenced by the policy's costing columns.

These relationships confirm GL_PLCY_MST as the central configuration anchor connecting OPM costing setup with Oracle GL accounting structures.