Results for “alloc_txn_type”

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

Overview

APPS.PA_ALLOC_TRANSACTIONS_V is a reporting view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that consolidates allocation transaction detail generated by the Oracle Projects allocation engine. It exposes the results of allocation runs — the transactions produced when allocation rules distribute or offset costs, revenue, or quantities across projects, tasks, and expenditure types. The view is owned by APPS and is defined as a UNION of at least two SELECT blocks over the allocation detail and run basis detail tables, joined to descriptive lookups, project/task master data, and organization name translations.

The view plays a central role in reconciliation and audit reporting. It answers the question "what did an allocation run produce, and why?" by combining computed allocation amounts with the rejection reasons and basis percentages that explain each line. The search term "alloc_txn_type" corresponds directly to the PA_LOOKUPS lookup type ALLOC_TXN_TYPE, which the view joins to translate the stored transaction_type code into a user-readable meaning. This makes the view a convenient source for reports that need to display allocation transaction types without performing a separate lookup join.

Underlying Base Objects

The documented ETRM metadata lists seven referenced objects: 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. All are accessed through APPS synonyms except PA_LOOKUPS, which is itself a view.

The core driver is PA_ALLOC_TXN_DETAILS (aliased atd), which holds the allocation transaction rows. It is outer-joined to PA_ALLOC_RUN_BASIS_DET (abd) on run_id, line_num, project_id, and task_id, allowing basis percent and line percent to be aggregated per transaction. Inner joins to PA_PROJECTS_ALL and PA_TASKS supply project segment1/name and task number/name. A second, outer-joined instance of PA_TASKS (pt2) resolves the carried-interest source task, while HR_ALL_ORGANIZATION_UNITS and its translation table supply the carrying-interest expenditure organization name. Two lookup joins on PA_LOOKUPS resolve transaction_type via lookup type ALLOC_TXN_TYPE and rejection_code via transaction rejection reason lookup types. The union combines a rejected-transaction branch (where rejection_code is not null) with a second branch drawn from the same base structures.

Key Columns

• alloc_txn_id, run_id, rule_id, line_num — Identifiers linking each row to its allocation transaction, allocation run, rule, and line.
• transaction_type / meaning (pl1) — The allocation transaction type code and its ALLOC_TXN_TYPE lookup meaning; this is the column group surfaced by the "alloc_txn_type" search.
• project_id, segment1, name — Project identifier, number, and name from PA_PROJECTS_ALL.
• task_id, task_number, task_name — Target task attributes; parallel columns expose the carried-interest source task (cint_source_task_id) and its number/name.
• cint_exp_org_id, hrtl1.name — Carrying-interest expenditure organization and its translated name.
• cint_rate_multiplier, cint_prior_basis_amt, cint_current_basis_amt, and their sum — Carrying-interest rate multiplier and prior/current basis amounts aggregated via MAX.
• basis_percent (SUM), line_percent (MAX), and derived product — Allocation basis and line percentages, with the computed effective percent (basis_percent × line_percent ÷ 100).
• total_allocation, previous_allocation, current_allocation — Allocation amounts for the transaction.
• rejection_code / pl2.meaning — Rejection code and its descriptive meaning from the transaction rejection reason lookups.

Common Use Cases and Queries

Typical uses include auditing allocation run output, investigating rejected allocation lines, reconciling carrying-interest calculations, and feeding downstream reporting or extracts. A simple query filtering by transaction type meaning and run is:

SELECT run_id, line_num, segment1, task_number, meaning, total_allocation FROM apps.pa_alloc_transactions_v WHERE run_id = :run_id AND meaning = 'ALLOCATED' ORDER BY line_num;

To review rejections, filter on the rejection reason columns:

SELECT run_id, line_num, segment1, task_number, rejection_code FROM apps.pa_alloc_transactions_v WHERE run_id = :run_id AND rejection_code IS NOT NULL;

Because the view aggregates basis percentages with SUM and MAX over grouped columns, results may show one row per alloc_txn_id/line combination rather than per basis detail row. Joins back to PA_ALLOC_RUN_BASIS_DET should therefore be avoided when line-level basis granularity is required; query the base table directly in that case.