Results for “gl_aloc_mst”

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

Overview

GL_ALOC_MST is the allocation code master table within the Oracle EBS Process Manufacturing Financials (GMF) module. It stores the definition of allocation codes used to distribute costs, quantities, or amounts across accounts and cost objects in process manufacturing environments. Each row represents a single allocation definition that downstream allocation processing engines reference when calculating and posting allocation results to the general ledger.

The table resides in the GMF schema and is documented as VALID in ETRM 12.2.2, where it exposes 44 columns. Two primary key constraints are documented: GL_ALOC_MSTI1, a unique index on ALLOC_ID, and GL_ALOC_MST_PK, a composite key on CO_CODE and ALLOC_CODE. The unique index on the surrogate ALLOC_ID is the canonical business-key candidate and is the column all child tables use for referential integrity.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is hub-leaning. GL_ALOC_MST behaves as a hub: it carries a stable surrogate key (ALLOC_ID) and a natural business key (CO_CODE plus ALLOC_CODE), and it is referenced by multiple dependent tables. In a Data Vault design this would be modeled as a hub entity with satellites capturing descriptive and audit attributes, and links to related allocation detail, basis, and exception structures.

Key Information Stored

• ALLOC_ID — Surrogate primary key (unique index GL_ALOC_MSTI1); the identifier propagated to all dependent allocation tables.
• CO_CODE — Company or cost organization code; part of the composite business key GL_ALOC_MST_PK.
• ALLOC_CODE — The user-facing allocation code; the second component of GL_ALOC_MST_PK.
• ALLOC_DESC — Descriptive text for the allocation definition.
• LEGAL_ENTITY_ID — Foreign key to FV_LEGAL_ENTITIES, scoping the allocation to a legal entity.
• TEXT_CODE — Short textual reference associated with the allocation.
• TRANS_CNT — Transaction counter, typically used for concurrency control during updates.
• DELETE_MARK — Soft-delete flag indicating logical removal without physical deletion.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE30 — The standard Oracle EBS descriptive flexfield (DFF) columns, providing extensible, customer-defined attributes.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns tracking row creation and modification.

The distinction between the surrogate and business keys is significant: ALLOC_ID provides stable, join-safe identity across the allocation subsystem, while CO_CODE and ALLOC_CODE form the human-recognizable unique combination enforced by GL_ALOC_MST_PK.

Common Use Cases and Queries

Typical usage centers on retrieving allocation definitions, joining master attributes to detail, basis, and exception tables, and reporting allocation setup across legal entities. A representative query resolving a business key to its surrogate follows:

• SELECT ALLOC_ID, ALLOC_CODE, ALLOC_DESC FROM GMF.GL_ALOC_MST WHERE CO_CODE = :co_code AND ALLOC_CODE = :alloc_code AND DELETE_MARK = 0;
• Reporting allocations by legal entity: join LEGAL_ENTITY_ID to FV_LEGAL_ENTITIES to present entity names alongside allocation codes.
• Extracting full allocation definitions for migration or audit: SELECT * FROM GMF.GL_ALOC_MST WHERE LAST_UPDATE_DATE >= :since;
• Reconciling child detail to master: join GL_ALOC_DTL and GL_ALOC_BAS on ALLOC_ID to validate that every detail row has a live master definition.
• Flexfield-based reporting: query ATTRIBUTE_CATEGORY and the relevant ATTRIBUTEn columns for customer-specific allocation groupings.

Queries should generally filter on DELETE_MARK = 0 to exclude logically deleted records.

Related Objects

• GL_ALOC_BAS — References GL_ALOC_MST via GL_ALOC_BAS.ALLOC_ID; holds allocation basis information.
• GL_ALOC_DTL — References via GL_ALOC_DTL.ALLOC_ID; stores allocation detail lines.
• GL_ALOC_EXP — References via GL_ALOC_EXP.ALLOC_ID; stores allocation exceptions or exclusions.
• GL_ALOC_INP — References via GL_ALOC_INP.ALLOC_ID; captures allocation input parameters.
• GL_ALOC_DTL_EFC — References via ALLOC_ID; a related allocation detail extension structure.
• IGI_STP_NET_TYPE_ALLOC_ALL — References via ALLOC_ID; links allocation codes to net type allocation setup.
• FV_LEGAL_ENTITIES — Referenced by GL_ALOC_MST.LEGAL_ENTITY_ID, providing legal entity context.

These relationships confirm GL_ALOC_MST as the hub of the GMF allocation schema, with dependent detail, basis, input, and exception tables all keyed through ALLOC_ID.