Search Results pa_alloc_run_gl_det




Overview
Explore in AI Chat

Overview

PA_ALLOC_RUN_GL_DET is a Projects (PA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2, owned by the APPS-facing PA schema. It stores the source lines that map allocation run activity to specific General Ledger accounts, capturing the detailed breakdown of eligible amounts, applied percentages, and subtract indicators that drive how a given allocation rule posts to the GL. Each row ties an allocation run and rule combination to a single GL code combination, forming the granular detail behind summarized allocation output.

From a Data Vault modeling perspective, the FK structure suggests classifying this object heuristically as a link. It resolves the many-to-many relationship between allocation rules (PA_ALLOC_GL_LINES) and GL accounts (GL_CODE_COMBINATIONS), while carrying descriptive and quantitative satellite-style attributes such as amounts and percentages. In the EBS 12.2.2 documented schema the table contains 13 columns under the PA owner.

Key Information Stored

The most significant columns of PA_ALLOC_RUN_GL_DET are:

  • RUN_ID — Identifier of the parent allocation run; a principal grouping key for retrieving all detail lines of a run.
  • RULE_ID — Foreign key to PA_ALLOC_GL_LINES identifying the allocation rule line that generated the source record.
  • LINE_NUM — Line sequence within the rule; combines with RULE_ID to complete the foreign key to PA_ALLOC_GL_LINES.
  • SOURCE_CCID — Foreign key to GL_CODE_COMBINATIONS, the GL account represented by the source line.
  • SUBTRACT_FLAG — Indicator controlling whether the source amount is added or subtracted during allocation computation.
  • SOURCE_PERCENT — The percentage of the source balance designated for allocation under the rule.
  • AMOUNT — The source amount associated with the GL account for the run.
  • ELIGIBLE_AMOUNT — The portion of the amount qualifying for allocation after applying rule criteria.
  • CREATION_DATE, CREATED_BY — Standard audit columns recording when and by whom the row was inserted.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns tracking the most recent modification and session.

The documented foreign keys reference PA_ALLOC_GL_LINES via (RULE_ID, LINE_NUM) and GL_CODE_COMBINATIONS via SOURCE_CCID. No surrogate single-column primary key is documented in the provided metadata; RUN_ID together with RULE_ID and LINE_NUM functions as the effective business-key candidate for uniquely locating a detail line.

Common Use Cases and Queries

Typical use cases include reconciliation of allocation runs to the GL, audit of eligible versus applied amounts, and reporting of how rule definitions map to accounts. A common pattern joins the detail to the rule and GL account definitions:

  • Retrieving all source GL accounts and amounts for a run: select RUN_ID, RULE_ID, LINE_NUM, SOURCE_CCID, AMOUNT, ELIGIBLE_AMOUNT, SOURCE_PERCENT from PA_ALLOC_RUN_GL_DET where RUN_ID = :run_id.
  • Joining to GL_CODE_COMBINATIONS on SOURCE_CCID to display concatenated account segments for reporting.
  • Joining to PA_ALLOC_GL_LINES on (RULE_ID, LINE_NUM) to compare configured rule targets against actual source detail.
  • Aggregating ELIGIBLE_AMOUNT by run or rule to validate allocation totals before GL posting.

Related Objects

  • PA_ALLOC_GL_LINES — Referenced via RULE_ID and LINE_NUM; holds the allocation rule line definition.
  • GL_CODE_COMBINATIONS — Referenced via SOURCE_CCID; supplies the GL account definition for each source line.
  • PA_ALLOC_RUNS_ALL — Parent allocation run master that owns RUN_ID.
  • PA_ALLOC_RUN_GL — Summarized output of allocation runs against the GL.
  • PA_ALLOC_RULES / PA_ALLOC_RULES_ALL — Rule headers governing the run.
  • GL_JE_LINES / GL_JE_HEADERS — Journal entries that ultimately receive posted allocation amounts.

These relationships make PA_ALLOC_RUN_GL_DET the detailed bridge between allocation rule configuration and the General Ledger accounts affected by each run.