Search Results alloc_method




Overview
Explore in AI Chat

Overview

GMF.GL_ALOC_BAS is the allocation basis detail table within the Oracle EBS Process Manufacturing (OPM) financials schema. It stores the line-level definitions that determine how a given allocation code distributes expenses. In the context of EBS 12.1.1 and 12.2.2, this table works together with the GL_ALOC_MST master table to define allocation logic that assigns cost from source expense accounts to target items, warehouses, and cost component classes. Each row represents one allocation line, keyed by ALLOC_ID and LINE_NO, and captures both the criteria (basis) used to compute the allocation percentage and the destination of the resulting cost.

The header-level table GL_ALOC_MST holds the allocation code itself; GL_ALOC_BAS supplies the per-line mechanics. The alloc_method column is the pivot that governs how a basis is derived: value 0 directs the system to compute the allocation percentage dynamically from a basis account amount, while value 1 directs the system to use a fixed percent entered on the line. Per the documented metadata, alloc_method must carry the same value across all lines of a given ALLOC_ID, meaning an allocation code is homogeneous with respect to its method.

Under a heuristic Data Vault classification derived from the foreign key structure, this object is best modeled as a link (or, depending on the modeling stance, a link with satellite attributes). The classification is a modeling suggestion reflecting the presence of multiple foreign key relationships and the presence of a composite natural/business key. In this context, the Data Vault classification is a modeling suggestion rather than a documented EBS artifact.

Key Information Stored

The composite primary key GL_ALOC_BAS_PK (ALLOC_ID, LINE_NO) is the surrogate/business key that uniquely identifies each allocation basis line. The most operationally significant columns include:

  • ALLOC_METHOD – Indicator of the allocation method; 0 = allocation percent depends on basis amount, 1 = fixed percent used for allocation. This value is consistent across all lines of one alloc_id.
  • FIXED_PERCENT – The fixed allocation percentage when alloc_method = 1.
  • BASIS_ACCOUNT_KEY and BASIS_ACCOUNT_DESC – The basis account used to compute the allocation percentage (only populated for alloc_method = 0) and its description.
  • BALANCE_TYPE – Type of the basis account (0 = Statistical, 1 = Budget, 2 = Actual), applicable only for alloc_method = 0.
  • BAS_YTD_PTD – Determines whether period-to-date (0) or year-to-date (1) basis amounts are used to compute the allocation percentage.
  • ITEM_ID – The item to which the allocation is directed.
  • CMPNTCLS_ID – The cost component class bucket into which the allocated cost will flow.
  • WHSE_CODE – The warehouse to which the cost will be allocated.
  • The standard who columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) provide the audit trail.

Additional documented columns such as TEXT_CODE, DELETE_MARK, BASIS_ACCOUNT_ID, BASIS_TYPE, INVENTORY_ITEM_ID, ORGANIZATION_ID, and ANALYSIS_CODE#1 appear in the 12.2.2 physical schema (24 total columns) and support supplementary classification and multi-organization context.

Common Use Cases and Queries

Typical usage centers on allocation configuration review, cost distribution analysis, and reconciliation of allocated cost back to source items and warehouses. Common patterns include retrieving all lines for a given allocation code, filtering by method, or resolving the destination item and cost component class:

  • Listing lines for an allocation code: SELECT ALLOC_ID, LINE_NO, ALLOC_METHOD, ITEM_ID, CMPNTCLS_ID, WHSE_CODE FROM GMF.GL_ALOC_BAS WHERE ALLOC_ID = :alloc_id ORDER BY LINE_NO;
  • Isolating fixed-percent allocations: SELECT * FROM GMF.GL_ALOC_BAS WHERE ALLOC_METHOD = 1;
  • Isolating basis-amount allocations with their basis account and balance type: SELECT * FROM GMF.GL_ALOC_BAS WHERE ALLOC_METHOD = 0 AND BASIS_ACCOUNT_KEY IS NOT NULL;
  • Reporting destination cost component classes by allocation: joining CMPNTCLS_ID to the component master to describe where expense will land.

These queries support finance and cost accounting teams validating that allocation rules route expense to the correct item, warehouse, and cost component class.

Related Objects

GL_ALOC_BAS is tightly coupled to several master tables through documented foreign keys:

  • GMF.GL_ALOC_MST – Joined on ALLOC_ID; the parent allocation code master.
  • GMF.IC_ITEM_MST and GMF.IC_ITEM_MST_B – Joined on ITEM_ID; resolve the destination item.
  • GMF.IC_WHSE_MST – Joined on WHSE_CODE; resolves the destination warehouse.
  • GMF.CM_CMPT_MST and GMF.CM_CMPT_MST_B – Joined on CMPNTCLS_ID; resolve the cost component class bucket.
  • GMF.CM_ALYS_MST – Joined on ANALYSIS_CODE; links analysis classification where applicable.
  • GMF.CM_TEXT_HDR – Joined on TEXT_CODE; provides supporting text reference.

Together these relationships make GL_ALOC_BAS the connective structure between allocation codes and the OPM cost, item, and warehouse masters.