Search Results gl_aloc_bas_pk




Overview
Explore in AI Chat

Overview

GL_ALOC_BAS is a table owned by the GMF schema (Process Manufacturing Financials) in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the basis definition lines for an allocation code: the items or item ranges to which expenses will be allocated, the criteria used to derive the allocation (a basis account or a fixed percent), and the cost component class bucket that receives the allocated amount. Each row is a single basis line belonging to a parent allocation defined in GL_ALOC_MST, and it is the table queried whenever Oracle Process Manufacturing Financials resolves how a cost allocation should be spread.

From the mined foreign-key structure, the table is heuristically classified as a link in a Data Vault model — it resolves many-to-many relationships between the allocation master, items, warehouses, analysis codes, cost component classes, and text headers rather than acting as a standalone hub or a descriptive satellite. This classification is a modeling suggestion derived from its FK profile, not a documented Oracle designation.

Key Information Stored

The table carries 24 documented columns. The most consequential are:

Common Use Cases and Queries

Typical usage includes reviewing how a specific allocation code spreads cost, verifying which items or warehouses participate, and auditing cost component class assignments for month-end close. A common pattern joins the basis lines to the allocation master:

  • Extract all basis lines for an allocation: SELECT * FROM GMF.GL_ALOC_BAS WHERE ALLOC_ID = :alloc_id ORDER BY LINE_NO;
  • Resolve item detail: join ITEM_ID to IC_ITEM_MST or IC_ITEM_MST_B and WHSE_CODE to IC_WHSE_MST to obtain item and warehouse descriptions.
  • Identify account-based versus fixed-percent lines by filtering on BASIS_TYPE and FIXED_PERCENT.
  • Cost component reporting: join CMPNTCLS_ID to CM_CMPT_MST_B to label the receiving cost bucket.

Reporting often filters on DELETE_MARK to exclude logically deleted lines and uses TRANS_CNT to detect concurrent modifications.

Related Objects

The following relationships are documented in the ETRM metadata and are the most significant for joining or validating GL_ALOC_BAS:

  • GL_ALOC_MST — parent allocation master, joined on ALLOC_ID (the allocation header that owns each basis line).
  • IC_ITEM_MST and IC_ITEM_MST_B — validated via ITEM_ID for item detail.
  • IC_WHSE_MST — validated via WHSE_CODE for warehouse detail.
  • CM_CMPT_MST and CM_CMPT_MST_B — validated via CMPNTCLS_ID for cost component class definitions.
  • CM_ALYS_MST — validated via ANALYSIS_CODE#1 for analysis code detail.
  • CM_TEXT_HDR — validated via TEXT_CODE for descriptive text associated with the basis line.

Because GL_ALOC_BAS is a link-style table, its value in reporting derives primarily from the descriptive dimensions it references rather than from attributes held natively on the row.