Results for “to_description”

21 results




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

Overview

GL_ALOC_EXP is a table owned by the GMF schema within Oracle E-Business Suite, belonging to the Process Manufacturing Financials (GMF) product family. It stores the expense-to-allocate information associated with an allocation code, and its data drives General Ledger expense allocation processing by determining the total expense amount to allocate. Each row represents a discrete expense allocation line tied to a parent allocation definition, allowing the allocation engine to resolve which accounts, descriptions, and balance types participate in a given expense allocation.

From a Data Vault modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification. The table carries a composite primary key and a single outbound foreign key to GL_ALOC_MST, which means it primarily holds descriptive and transactional attributes that depend on a parent allocation entity rather than acting as an independent hub or a many-to-many link. In practice, GL_ALOC_EXP functions as a detail/child table of the allocation master, and its rows are only meaningful in the context of the parent allocation record.

Key Information Stored

The table contains 18 documented columns. The most significant are summarized below, distinguishing the primary key from business-key candidates.

  • ALLOC_ID — Foreign key to GL_ALOC_MST and part of the composite primary key; identifies the parent allocation code.
  • LINE_NO — The second component of the composite primary key, sequencing the expense allocation lines within an allocation.
  • FROM_ACCOUNT / TO_ACCOUNT — The source and target accounts for the expense allocation mapping.
  • FROM_ACCOUNT_ID / TO_ACCOUNT_ID — Surrogate account identifiers corresponding to the FROM_ACCOUNT and TO_ACCOUNT values, supporting joins to account dimension structures.
  • FROM_DESCRIPTION / TO_DESCRIPTION — Descriptive text associated with the source and target accounts.
  • BALANCE_TYPE — Indicates the balance classification (for example, actual, budget, or encumbrance) applicable to the allocation line.
  • EXP_YTD_PTD — Specifies whether expense is measured on a year-to-date or period-to-date basis.
  • TRANS_CNT — A transaction count maintained for the allocation line.
  • TEXT_CODE — A reference or code value attached to the line.
  • DELETE_MARK — Standard soft-delete indicator used to logically retire a row.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Oracle audit columns.

The surrogate (composite) primary key is defined by the unique index GL_ALOC_EXP_PK on (ALLOC_ID, LINE_NO). No separate business-key unique index beyond the primary key is documented, so ALLOC_ID and LINE_NO together constitute the effective business-key candidate.

Common Use Cases and Queries

Typical uses center on tracing and validating expense allocations configured for Process Manufacturing Financials. Analysts query the table to review which accounts and balance types feed a given allocation, to reconcile year-to-date versus period-to-date expense logic, and to audit configuration before period close.

  • Retrieving all expense lines for a specific allocation: SELECT ALLOC_ID, LINE_NO, FROM_ACCOUNT, TO_ACCOUNT, BALANCE_TYPE, EXP_YTD_PTD FROM GMF.GL_ALOC_EXP WHERE ALLOC_ID = :p_alloc_id ORDER BY LINE_NO;
  • Excluding soft-deleted rows in reports: add WHERE DELETE_MARK = 0.
  • Joining to the allocation master to display descriptive allocation context: SELECT m.ALLOC_ID, e.LINE_NO, e.FROM_ACCOUNT, e.TO_ACCOUNT FROM GMF.GL_ALOC_EXP e, GMF.GL_ALOC_MST m WHERE e.ALLOC_ID = m.ALLOC_ID;
  • Auditing recently modified configuration: filter on LAST_UPDATE_DATE within a date range.
  • Reconciliation reporting of expense-to-allocate amounts by balance type and YTD/PTD basis.

Related Objects

The following objects are most significant in relation to GL_ALOC_EXP:

  • GL_ALOC_MST — The allocation master; joined via GL_ALOC_EXP.ALLOC_ID = GL_ALOC_MST.ALLOC_ID. This is the sole documented foreign-key relationship and the primary parent of the table.
  • Account dimension structures — Referenced through FROM_ACCOUNT_ID and TO_ACCOUNT_ID for account validation and reporting.
  • GL expense allocation processing programs — Consume GL_ALOC_EXP rows to compute the total expense to allocate.
  • GL journal and balance tables — Source the actual expense amounts that allocation logic distributes to target accounts.

Because the documented FK graph is limited to GL_ALOC_MST, GL_ALOC_EXP should be treated as a dependent detail table whose population and lifecycle are governed by its parent allocation definition.