Search Results pa_alloc_gl_lines_pk

Overview

PA_ALLOC_GL_LINES is a Projects (PA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the allocation source lines associated with General Ledger accounts. It defines, at the rule level, which GL code combinations participate in a project allocation and the proportion each contributes. The table sits beneath PA_ALLOC_RULES_ALL, the parent definition table for allocation rules, and supplies the source-side detail that drives how costs are distributed across target projects and tasks.

In Data Vault modeling terms, the mined foreign-key structure classifies PA_ALLOC_GL_LINES as satellite-leaning. This is a modeling suggestion: the table carries descriptive attributes (source account, subtraction flag, source percentage) that qualify a parent allocation rule rather than acting as an independent hub of business entities. The parent rule key is inherited as part of the primary key, which is characteristic of a satellite attached to the allocation rule.

Key Information Stored

The table is documented with ten columns in ETRM 12.2.2. The most significant are:

• RULE_ID – Identifier of the parent allocation rule; foreign key to PA_ALLOC_RULES_ALL and part of the composite primary key.
• LINE_NUM – Sequence number of the source line within the rule; the second component of the composite primary key.
• SOURCE_CCID – The GL code combination acting as the allocation source; foreign key to GL_CODE_COMBINATIONS.
• SOURCE_PERCENT – The percentage of the source balance to allocate for this line.
• SUBTRACT_FLAG – Indicates whether the line amount is added to or subtracted from the allocation basis.
• CREATED_BY, CREATION_DATE – Standard WHO audit columns recording row creation.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – Standard WHO audit columns recording the most recent modification.

The surrogate identifier is the composite primary key PA_ALLOC_GL_LINES_PK, made up of RULE_ID and LINE_NUM. A unique index, PA_ALLOC_GL_LINES_U1, is defined on the same two columns (RULE_ID, LINE_NUM), making them the business-key candidates: no two source lines may share the same rule and line number.

Common Use Cases and Queries

Typical scenarios include auditing allocation rule definitions, reconciling allocation source accounts to GL, and reporting on the percentage mix applied to each rule. A representative query retrieves all source lines for a given rule:

• SELECT LINE_NUM, SOURCE_CCID, SOURCE_PERCENT, SUBTRACT_FLAG FROM PA_ALLOC_GL_LINES WHERE RULE_ID = :rule_id ORDER BY LINE_NUM;

Joining to GL_CODE_COMBINATIONS resolves the account string for reporting:

• SELECT l.LINE_NUM, g.concatenated_segments, l.SOURCE_PERCENT, l.SUBTRACT_FLAG FROM PA_ALLOC_GL_LINES l, GL_CODE_COMBINATIONS_KFV g WHERE l.SOURCE_CCID = g.code_combination_id AND l.RULE_ID = :rule_id;

Because PA_ALLOC_RUN_GL_DET references this table on RULE_ID and LINE_NUM, run-time allocation results can be compared against the rule definition to validate that executed percentages match the intended source percentages.

Related Objects

PA_ALLOC_GL_LINES participates in a small, tightly coupled set of allocation objects:

• PA_ALLOC_RULES_ALL – Parent allocation rule header; joined on RULE_ID.
• GL_CODE_COMBINATIONS – Resolves SOURCE_CCID to a full accounting flexfield.
• PA_ALLOC_RUN_GL_DET – Allocation run-time GL detail; references PA_ALLOC_GL_LINES on RULE_ID and LINE_NUM, providing the actual-versus-defined comparison path.

These relationships establish PA_ALLOC_GL_LINES as the source-definition satellite within the project allocation subsystem, bridging rule headers to GL account combinations and to executed allocation detail.