Results for “pa_alloc_transactions_v”

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

Overview

PA_ALLOC_TRANSACTIONS_V is an Oracle E-Business Suite Projects (PA) view owned by the APPS schema. It exposes allocation transaction detail for burden and cost allocation runs, joining the transaction-level allocation table (PA_ALLOC_TXN_DETAILS) with project, task, lookup, basis, and organization information. It presents the allocation basis amount carried forward from prior runs, the basis amount accumulated in the current run, and the resulting allocated totals, along with rejection handling metadata. In ETRM 12.2.2 the view is documented as VALID, with the referenced base objects listed below. The view aggregates at the ALLOC_TXN_ID, RUN_ID, RULE_ID, transaction type, line, project, task, and expenditure-type grain, collapsing multiple PA_ALLOC_RUN_BASIS_DET rows per allocation line into basis percentages and computed allocation amounts.

For users searching previous_allocation, the view is the primary exposure point: the column PREVIOUS_ALLOCATION is surfaced via MAX(ATD.PREVIOUS_ALLOCATION) and is grouped alongside CURRENT_ALLOCATION and TOTAL_ALLOCATION, making the view suitable for reconciliation between successive allocation runs.

Underlying Base Objects

The documented base objects are PA_ALLOC_TXN_DETAILS, PA_ALLOC_RUN_BASIS_DET, PA_PROJECTS_ALL, PA_TASKS, PA_LOOKUPS, HR_ALL_ORGANIZATION_UNITS, and HR_ALL_ORGANIZATION_UNITS_TL.

• PA_ALLOC_TXN_DETAILS (ATD) — the driving table; supplies transaction type, line number, project/task, expenditure type, allocation amounts, and rejection code. It is the source of PREVIOUS_ALLOCATION.
• PA_ALLOC_RUN_BASIS_DET (ABD) — outer-joined on RUN_ID, LINE_NUM, PROJECT_ID, and TASK_ID; contributes BASIS_PERCENT and LINE_PERCENT used to derive the calculated allocation percentage.
• PA_PROJECTS_ALL (PP) — supplies SEGMENT1 (project number) and NAME.
• PA_TASKS (PT, PT2) — PT provides the transaction task number and name; PT2 provides the source task number and name via CINT_SOURCE_TASK_ID.
• PA_LOOKUPS (PL1, PL2) — PL1 decodes TRANSACTION_TYPE using lookup type ALLOC_TXN_TYPE; PL2 decodes REJECTION_CODE using the TRANSACTION REJECTION REASON and TRANSACTION USER REJ REASON lookup types.
• HR_ALL_ORGANIZATION_UNITS / _TL (HR1, HRTL1) — supply the expenditure organization name through CINT_EXP_ORG_ID, resolved against the session's language.

Key Columns

• ALLOC_TXN_ID, RUN_ID, RULE_ID, LINE_NUM — allocation transaction, run, rule, and line identifiers.
• TRANSACTION_TYPE / MEANING — allocation transaction type code and its decoded lookup meaning.
• PROJECT_ID, SEGMENT1, NAME, TASK_ID, TASK_NUMBER, TASK_NAME, EXPENDITURE_TYPE — project and task context for the allocation line.
• CINT_SOURCE_TASK_ID / PT2.TASK_NUMBER / PT2.TASK_NAME — source task for cross-charge (CINT) allocations.
• CINT_RATE_MULTIPLIER, CINT_PRIOR_BASIS_AMT, CINT_CURRENT_BASIS_AMT — cross-charge rate and basis amounts before and after the current run.
• Basis percent columns — SUM(ABD.BASIS_PERCENT), MAX(ABD.LINE_PERCENT), and the derived product over 100.
• TOTAL_ALLOCATION, PREVIOUS_ALLOCATION, CURRENT_ALLOCATION — the cumulative, prior-run, and current-run allocation amounts; PREVIOUS_ALLOCATION is the subject of the user's search.
• REJECTION_CODE and its meaning — populated only for rejected transactions (the view filters on REJECTION_CODE IS NOT NULL).

Common Use Cases and Queries

Typical scenarios include reconciling allocation run outputs, tracing where a prior allocation balance originated, and auditing rejected transactions. The view already restricts rows to rejected transactions, so it is most useful for rejection and prior-balance analysis rather than a general allocation ledger. A representative query:

SELECT run_id, rule_id, segment1, task_number,
       transaction_type, previous_allocation,
       current_allocation, total_allocation, rejection_code
FROM   apps.pa_alloc_transactions_v
WHERE  run_id = :p_run_id
ORDER  BY segment1, task_number, line_num;

To compare prior and current allocation by project and task:

SELECT segment1, task_number,
       SUM(previous_allocation) prev_alloc,
       SUM(current_allocation)  curr_alloc
FROM   apps.pa_alloc_transactions_v
GROUP  BY segment1, task_number;