Search Results gmf_organization_definitions




Overview
Explore in AI Chat

Overview

GMF_ORGANIZATION_DEFINITIONS is an APPS-owned reporting view within the Oracle E-Business Suite Process Manufacturing Financials (GMF) product family. Its documented purpose is to present "Process Organization Definition Details," consolidating the organizational, accounting, and inventory attributes that identify which inventory organizations are enabled for process manufacturing. The view is classified as VALID and is available in both the 12.1.1 and 12.2.2 releases, sharing identical column semantics across the two, since it abstracts ledger identity behind GL_LEDGERS rather than exposing the older GL_SETS_OF_BOOKS construct directly.

Functionally, the view answers a recurring question in process manufacturing implementations: which organizations are enabled for process execution, and what ledger, legal entity, and operating unit are they associated with? Because these attributes are distributed across Human Resources organization tables, inventory parameters, and General Ledger, the view provides a single denormalized read surface suitable for reports, concurrent programs, integrations, and ad hoc SQL without requiring the developer to reconstruct the join logic.

Underlying Base Objects

The view is defined over five referenced base objects, all exposed in the APPS schema as synonyms:

The join chain therefore runs from the organization unit through its translated name, its accounting flexfield information, its inventory parameters, and finally to the ledger. The ACCOUNTING INFORMATION context predicate is mandatory, as it isolates the specific descriptive flexfield context that stores accounting organization assignments.

Key Columns

  • ORGANIZATION_ID — primary identifier of the inventory organization; the principal join key to MTL_PARAMETERS, MTL_SYSTEM_ITEMS, and other inventory objects.
  • ORGANIZATION_CODE — the short inventory organization code from MTL_PARAMETERS.
  • ORGANIZATION_NAME — the translated organization name from HR_ALL_ORGANIZATION_UNITS_TL.
  • LEDGER_ID — numeric ledger identifier derived from ORG_INFORMATION1.
  • LEGAL_ENTITY_ID — numeric legal entity identifier derived from ORG_INFORMATION2.
  • OPERATING_UNIT_ID — numeric operating unit identifier derived from ORG_INFORMATION3.
  • CHART_OF_ACCOUNTS_ID — chart of accounts associated with the ledger.
  • CURRENCY_CODE — the ledger's functional currency.

Because the numeric columns are produced by TO_NUMBER conversions of descriptive flexfield segments, they are safe to join directly to LEDGER_ID, LEGAL_ENTITY_ID, and OPERATING_UNIT_ID columns elsewhere.

Common Use Cases and Queries

Typical scenarios include validating process-enabled organizations before data conversion, driving multi-org reports that must display the ledger and legal entity context, and feeding downstream integrations that require organization-to-ledger mappings.

A basic listing of process organizations and their accounting context:

  • SELECT organization_id, organization_code, organization_name, ledger_id, legal_entity_id, operating_unit_id, currency_code FROM gmf_organization_definitions ORDER BY organization_code;

Restricting to a specific ledger or operating unit:

  • SELECT organization_id, organization_code FROM gmf_organization_definitions WHERE ledger_id = :p_ledger_id;
  • SELECT organization_id, organization_code, currency_code FROM gmf_organization_definitions WHERE operating_unit_id = :p_org_id;

Joining to inventory parameters to confirm process enablement and cost organization attributes, or joining ORGANIZATION_ID to MTL_SYSTEM_ITEMS to enumerate process items by organization, are equally common. As with all APPS views, queries should be executed against the APPS schema or through a synonym, and responsibility-level security (MOAC) should be applied where organization-restricted access is required.