Search Results gl_aloc_bas_v




Overview
Explore in AI Chat

Overview

GL_ALOC_BAS_V is an APPS-owned, VALID Oracle E-Business Suite view that belongs to the GMF (Process Manufacturing Financials) product family. Its documented purpose is to enable a master-detail relationship on the Allocation Basis form. In Oracle EBS 12.1.1 and 12.2.2, Oracle Forms-based master-detail blocks require a join that links a master record to its detail records; this view supplies exactly that joined dataset so the Allocation Basis form can present allocation bases in the context of the allocation to which they belong. Although it is a low-level technical object rather than a delivered concurrent program or report source, it plays an important integration role: any custom inquiry, form personalization, or downstream extract that needs allocation method information resolved against legal entity and allocation code can query this view instead of reconstructing the three-way join manually. Because the view already performs the DISTINCT and the entity-name lookup, consumers obtain a clean, denormalized result set suitable for LOVs, validation, and reporting. The view is not itself an allocation engine; it exposes configuration data only.

Underlying Base Objects

The documented ETRM metadata for 12.2.2 lists three referenced objects, all owned by APPS: GL_ALOC_BAS (SYNONYM), GL_ALOC_MST (SYNONYM), and GMF_LEGAL_ENTITIES_VW2 (VIEW). The view text joins them as follows:

  • GL_ALOC_BAS BAS is the allocation basis (detail) table, joined to the master on BAS.ALLOC_ID = MST.ALLOC_ID.
  • GL_ALOC_MST MST is the allocation master table, supplying LEGAL_ENTITY_ID and ALLOC_CODE and providing the join key to the legal entity view.
  • GMF_LEGAL_ENTITIES_VW2 GLE is joined on GLE.LEGAL_ENTITY_ID = MST.LEGAL_ENTITY_ID to resolve the legal entity name.

The two GL_ALOC_* objects are exposed to APPS as synonyms, which in a standard EBS installation point to the underlying GMF/GMA base tables. The SELECT DISTINCT clause prevents duplicate rows when an allocation master maps to multiple bases or when the legal entity view returns more than one matching row.

Key Columns

  • LEGAL_ENTITY_ID — Identifier of the legal entity that owns the allocation; sourced from GL_ALOC_MST and used as the join key to the legal entity view.
  • ALLOC_ID — The allocation identifier linking master and basis records; the primary correlation key between the two GL_ALOC tables.
  • ALLOC_CODE — The user-defined code (name) of the allocation, taken from the master table and typically used for display and lookup.
  • ALLOC_METHOD — The allocation method associated with the basis record. This is the column most directly relevant to searches for "alloc_method," since it carries the method indicator used by GMF allocation processing.
  • LEGAL_ENTITY_NAME — The descriptive legal entity name resolved from GMF_LEGAL_ENTITIES_VW2, enabling readable output without an additional lookup.

Common Use Cases and Queries

Typical uses include validating allocation method values, populating form LOVs, and building custom extracts of allocation configuration by legal entity.

List all allocations and their basis methods for a given legal entity:

  • SELECT alloc_code, alloc_method, legal_entity_name FROM apps.gl_aloc_bas_v WHERE legal_entity_id = :p_legal_entity_id ORDER BY alloc_code;

Retrieve the method for a specific allocation:

  • SELECT alloc_id, alloc_code, alloc_method FROM apps.gl_aloc_bas_v WHERE alloc_id = :p_alloc_id;

Distinct methods in use across the installation:

  • SELECT DISTINCT alloc_method FROM apps.gl_aloc_bas_v ORDER BY alloc_method;

Because the view is APPS-owned, queries should be prefixed with APPS or executed under a responsibility whose MO: Operating Unit and security context permit access to the underlying GMF allocation data.