Search Results pay_element_name

Overview

PA_EXPENDITURE_ITEMS_ONLINE_V is an Oracle E-Business Suite view owned by the APPS schema within the Projects (PA) module. As its description states, the view "shows all expenditure items" and serves as a denormalized, reporting-oriented projection of transactional expenditure data drawn primarily from the underlying PA_EXPENDITURE_ITEMS_ALL and PA_EXPENDITURE_ITEMS tables. In Oracle EBS 12.1.1 and 12.2.2, the view is validated as VALID and is intended for online inquiry, ad hoc reporting, OBIEE/BI Publisher extracts, and integration interfaces where a single flattened row per expenditure item is required.

The view is significant because expenditure items represent the atomic unit of cost captured against Projects — labor, non-labor, usage, and miscellaneous transactions — and this view enriches those raw items with descriptive attributes from project, task, person, job, organization, and expenditure-type dimensions, removing the need for callers to reconstruct those joins independently.

Underlying Base Objects

The view is defined over a broad set of documented base objects. Its primary source is PA_EXPENDITURE_ITEMS_ALL (referenced in the text as EI), joined conceptually to PA_EXPENDITURES_ALL (X), which carries the expenditure group, status code, ending date, and incurred-by person/party. Dimensional lookups include PA_PROJECTS_ALL (P) for PROJECT_NUMBER and PROJECT_NAME, PA_PROJECT_TYPES_ALL (PT) for PROJECT_TYPE and PROJECT_TYPE_CLASS_CODE, PA_TASKS (T) for task attributes, and PA_EXPENDITURE_TYPES for expenditure and revenue categories. Person-level attributes rely on PER_ALL_PEOPLE_F, PER_JOBS, and HR_ALL_ORGANIZATION_UNITS_TL, with HR_SECURITY controlling access. Non-labor detail is supported by PO_HEADERS_ALL and PO_LINES_ALL for supplier and document context, while payroll-related columns draw on PAY_ELEMENT_TYPES_F_TL and PAY_PAYROLLS_F. Utility packages such as PA_EXPENDITURES_UTILS, PA_UTILS2, PA_UTILS4, PA_SECURITY, HR_GENERAL, and FND_GLOBAL supply derived values and security predicates. Lookup views PA_LOOKUPS, FND_LOOKUPS, and PA_CONVERSION_TYPES_V, together with PA_CAPITAL_EVENTS, PA_PAY_AUDIT_ALL, PA_PAY_EXTERNAL_PAYROLL, and PA_TRANSACTION_SOURCES, round out the supported object list.

Key Columns

The view's most referenced identity columns are EXPENDITURE_ITEM_ID and EXPENDITURE_ID, which link back to the base expenditure item and expenditure tables. ROW_ID is returned as a ROWID for updatable query frameworks. Project context is provided through PROJECT_ID, PROJECT_NUMBER, PROJECT_NAME, PROJECT_TYPE, and PROJECT_TYPE_CLASS_CODE. Task context comes from TASK_ID, TASK_NUMBER, and TASK_NAME, while EXPENDITURE_ITEM_DATE, EXPENDITURE_TYPE, EXPENDITURE_CATEGORY, and REVENUE_CATEGORY_CODE describe the transaction.

Person and organization columns include INCURRED_BY_PERSON_ID, EMPLOYEE_NAME, EMPLOYEE_NUMBER (resolved via CURRENT_EMPLOYEE_FLAG from PER_ALL_PEOPLE_F), JOB_ID/JOB_NAME, INCURRED_BY_ORGANIZATION_ID, OVERRIDE_TO_ORGANIZATION_ID, EXPENDITURE_ORGANIZATION_ID (NVL of override and incurred-by), EXPENDITURE_ORGANIZATION_NAME, and NLR_ORGANIZATION_ID/NLR_ORGANIZATION_NAME for non-labor resources. Financial and status attributes include QUANTITY, BURDEN_COST, EXPENDITURE_STATUS_CODE, EXPENDITURE_GROUP, EXPENDITURE_ENDING_DATE, TRANSACTION_SOURCE, ORIG_TRANSACTION_REFERENCE, SYSTEM_LINKAGE_FUNCTION, and the expenditure comment subquery. The PAY_ELEMENT_TYPES_F_TL and PAY_PAYROLLS_F dependencies indicate the view also surfaces payroll element and payroll name context relevant to the user's search term "pay_element_name".

Common Use Cases and Queries

Typical usage includes reconciling expenditure items to project cost, producing labor distribution reports, and extracting non-labor spend linked to purchasing documents. Analysts frequently filter by EXPENDITURE_STATUS_CODE or EXPENDITURE_ITEM_DATE to isolate released, unprocessed, or adjusted items.

• List recent labor items with employee and job detail.
• Aggregate burdened cost by project, task, and expenditure category.
• Identify non-labor expenditure by NLR organization and non-labor resource.
• Map expenditure items to payroll element names for payroll-funded projects.

Sample query:

SELECT PROJECT_NUMBER, PROJECT_NAME, TASK_NUMBER, EXPENDITURE_ITEM_DATE, EXPENDITURE_TYPE, EXPENDITURE_CATEGORY, EMPLOYEE_NAME, EMPLOYEE_NUMBER, JOB_NAME, QUANTITY, BURDEN_COST, EXPENDITURE_STATUS_CODE FROM APPS.PA_EXPENDITURE_ITEMS_ONLINE_V WHERE EXPENDITURE_ITEM_DATE BETWEEN :p_start AND :p_end AND EXPENDITURE_STATUS_CODE = 'RELEASED' AND PROJECT_ID = :p_project_id;

A second common pattern joins the view to PA_EXPENDITURE_ITEMS_ALL on EXPENDITURE_ITEM_ID when additional base columns beyond those exposed are required. Because the view embeds HR_SECURITY and PA_SECURITY logic, results are automatically restricted by the caller's security profile when accessed by non-privileged users.