Results for “pa_expenditure_groups_v”

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

Overview

The PA_EXPENDITURE_GROUPS_V view is an APPS-owned database object within the Projects (PA) module of Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description is "10SC Only," indicating it is a restricted or specialized object originally introduced in a single-source or limited-release context, and it is classified as VALID within the ETRM metadata. The view presents expenditure group records together with descriptive lookup values and system linkage information, providing a denormalized read layer over the base expenditure group tables.

The view is primarily relevant for the "system_linkage" search context because it joins expenditure groups to the PA_SYSTEM_LINKAGES table through the SYSTEM_LINKAGE_FUNCTION column. This exposes the human-readable SYSTEM_LINKAGE meaning alongside the linking function used to associate an expenditure group with an external or source system (such as a subledger or feeder system). The view therefore supports integration, reconciliation, and reporting use cases where expenditure group definitions must be traced to their originating system linkage.

Underlying Base Objects

The documented base objects referenced by the view are: FND_USER (synonym), HR_GENERAL (package), HR_PERSON_NAME (package), HR_SECURITY (package), PA_EXPENDITURE_GROUPS (synonym), PA_LOOKUPS (view), PA_SYSTEM_LINKAGES (synonym), PA_TRANSACTION_SOURCES (synonym), and PER_PEOPLE_F (view). The core driving table is PA_EXPENDITURE_GROUPS, aliased as E, from which all primary expenditure attributes are selected.

• PA_SYSTEM_LINKAGES (aliased SL) joins on SL.FUNCTION = E.SYSTEM_LINKAGE_FUNCTION and provides the SYSTEM_LINKAGE meaning.
• PA_LOOKUPS (L1) joins with LOOKUP_TYPE = 'EXPENDITURE GROUP STATUS' to decode the expenditure group status code.
• PA_TRANSACTION_SOURCES (TR) is outer-joined on transaction source to return source-level flags such as adjustment and reversal permissions.
• FND_USER and PER_PEOPLE_F are outer-joined to resolve the creating user to an employee name and number, using the HR packages for name and security handling.

Key Columns

• SYSTEM_LINKAGE_FUNCTION and SYSTEM_LINKAGE: the linking function code and its decoded meaning, central to the "system_linkage" search.
• EXPENDITURE_GROUP and EXPENDITURE_ENDING_DATE: the identifier and ending date of each expenditure group.
• EXPENDITURE_GROUP_STATUS_CODE and EXPENDITURE_GROUP_STATUS_M: the status code and its lookup meaning.
• CONTROL_COUNT and CONTROL_TOTAL_AMOUNT: control totals used to validate group contents.
• TRANSACTION_SOURCE, USER_TRANSACTION_SOURCE, ALLOW_ADJUSTMENTS_FLAG, ALLOW_REVERSAL_FLAG: transaction source identification and permitted actions.
• CREATED_BY_EMPLOYEE_NAME, CREATED_BY_EMPLOYEE_NUMBER: resolved creator identity from HR.
• PERIOD_ACCRUAL_FLAG, ORG_ID, ROW_ID: accrual indicator, multi-org identifier, and row identifier.

Common Use Cases and Queries

Typical scenarios include auditing expenditure groups by system linkage, verifying control totals, and joining group data into integration extracts. The following query lists active expenditure groups with their decoded status and system linkage:

SELECT expenditure_group,
       expenditure_ending_date,
       expenditure_group_status_m,
       system_linkage,
       control_count,
       control_total_amount
FROM   apps.pa_expenditure_groups_v
WHERE  org_id = :org_id
  AND  system_linkage_function = :linkage_function;

A second scenario isolates creator and transaction-source permissions for reconciliation:

SELECT expenditure_group,
       created_by_employee_name,
       created_by_employee_number,
       user_transaction_source,
       allow_adjustments_flag,
       allow_reversal_flag
FROM   apps.pa_expenditure_groups_v
WHERE  transaction_source = :transaction_source;

Because the view decodes lookups and resolves personnel via HR packages, queries should avoid unnecessary full scans; filtering on ORGANIZATION_ID or system linkage function improves performance in multi-org reporting environments.