Results for “ac_status”

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

Overview

GL_ALOC_DTL is a table owned by the GMF schema (Process Manufacturing Financials) that stores the results of allocation processing within Oracle E-Business Suite. In the context of Oracle EBS 12.1.1 and 12.2.2, this table serves as the persistent record of how expenses are distributed across items, cost types, and accounting periods. The Actual Costing Process consumes the rows in this table to determine the expense allocation applicable to manufactured items. It therefore acts as the bridge between the allocation rules defined upstream and the cost roll-up performed by the costing engine.

From a dimensional modeling perspective, the metadata's heuristic Data Vault classification identifies this table as satellite-leaning. This suggests that GL_ALOC_DTL is best understood as a descriptive detail table hanging off a parent allocation entity rather than as an independent hub or as a pure link table. The dependency of GL_ALOC_DTL on GL_ALOC_MST through the ALLOC_ID foreign key reinforces this reading, since the parent supplies the allocation definition and the detail rows supply the computed results.

Key Information Stored

The table contains 25 documented columns. The most operationally significant are the following:

• ALLOCDTL_ID — the surrogate primary key, enforced by the unique index GL_ALOC_DTLI1. This is the only documented unique index and therefore the sole business-key candidate, though it functions primarily as a system-generated identifier.
• ALLOC_ID — the foreign key to GL_ALOC_MST, linking each detail row to its allocation definition.
• CALENDAR_CODE and PERIOD — identify the accounting calendar and period to which the allocation applies.
• PERIOD_ID — the internal period identifier that maps to the open accounting period.
• LINE_NO — the sequence of the allocation line within the parent allocation.
• PERCENT_ALLOCATION — the proportion of expense assigned to this line.
• ALLOCATED_EXPENSE_AMT — the resulting allocated expense amount, which is the central financial figure produced by the process.
• COST_TYPE_ID — a foreign key to CST_COST_TYPES, distinguishing the costing category (for example, material, resource, or overhead) to which the allocation applies.
• PERIOD_QTY and TOTAL_QTY — quantities used as allocation bases or resulting totals for the period.
• AC_STATUS — the status flag indicating the progress of the allocation through the Actual Costing process.
• GL_POSTED_IND — indicates whether the allocation has been transferred to the General Ledger.
• TRANS_CNT and TEXT_CODE — supplementary control and descriptive attributes.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program tracking columns that identify which request generated the rows.

Common Use Cases and Queries

The most frequent use case is reconciling allocated expenses for a given period against the originating allocation definition. A typical query joins GL_ALOC_DTL to GL_ALOC_MST on ALLOC_ID:

• Reporting allocated expense by cost type: SELECT d.COST_TYPE_ID, SUM(d.ALLOCATED_EXPENSE_AMT) FROM GMF.GL_ALOC_DTL d WHERE d.CALENDAR_CODE = :cal AND d.PERIOD = :per GROUP BY d.COST_TYPE_ID;
• Identifying allocations not yet posted to GL: SELECT * FROM GMF.GL_ALOC_DTL WHERE GL_POSTED_IND = 'N' AND AC_STATUS = 'PROCESSED';
• Tracing a specific allocation run via the concurrent request: SELECT * FROM GMF.GL_ALOC_DTL WHERE REQUEST_ID = :req_id;
• Auditing allocation percentages and verifying they sum to 100 percent per ALLOC_ID, LINE_NO grouping.
• Analyzing quantity-based allocation drivers using PERIOD_QTY and TOTAL_QTY.

Because the table is populated by the Actual Costing Process, most reporting queries filter on CALENDAR_CODE and PERIOD to constrain the result set to a single accounting period.

Related Objects

• GL_ALOC_MST — the parent allocation master table. Joined via GL_ALOC_DTL.ALLOC_ID = GL_ALOC_MST.ALLOC_ID. This is the principal FK relationship.
• CST_COST_TYPES — the cost type reference table. Joined via GL_ALOC_DTL.COST_TYPE_ID = CST_COST_TYPES.COST_TYPE_ID.
• GL_ALOC_DTLI1 — the unique index on ALLOCDTL_ID that enforces the primary key.
• GL_ALOC_DTL_PK — the composite primary key constraint defined on CALENDAR_CODE, PERIOD, ALLOC_ID, and LINE_NO, which establishes the natural uniqueness of an allocation line within a period.
• Actual Costing Process — the concurrent program that reads this table to determine item expense allocation; it is the primary consumer of the data.
• GL (General Ledger) interface tables — downstream objects that receive allocation amounts once GL_POSTED_IND is set.