Results for “pabv_expenditure_items”

Underlying Base Objects

The view is defined over two synonyms: PA_EXPENDITURE_ITEMS_ALL (aliased PEI) and PA_TASKS (aliased PT). The join is an inner join on PEI.TASK_ID = PT.TASK_ID, meaning only expenditure items linked to a valid task are returned. Because PA_EXPENDITURE_ITEMS_ALL is the _ALL variant, it is partitioned or secured by operating unit via ORG_ID, and this column is surfaced explicitly in the view as ORG_ID /* OPERATING UNIT */ and asserted by the security predicate. The task table contributes the owning PROJECT_ID, which is projected alongside the expenditure item identifier.

As a view, no data is stored in PABV_EXPENDITURE_ITEMS; all persistence remains in the base tables. The metadata records the status as VALID, confirming the view compiles cleanly against its base objects in the documented releases.

Key Columns

The projection covers several functional groupings:

• Identity and context: EXPENDITURE_ITEM_ID, EXPENDITURE_ID, TASK_ID, PROJECT_ID, EVENT_TASK_ID, EVENT_NUM, ORGANIZATION_ID, ORG_ID.
• Cost and quantity: QUANTITY, RAW_COST, BURDEN_COST, RAW_COST_RATE, BURDEN_COST_RATE, COST_DISTRIBUTED_FLAG.
• Revenue and billing: RAW_REVENUE, ACCRUED_REVENUE, ACCRUAL_RATE, FORECAST_REVENUE, BILL_AMOUNT, BILL_RATE, BILLABLE_FLAG, BILL_HOLD_FLAG, REVENUE_DISTRIBUTED_FLAG, REV_DIST_REJECTION_CODE, BILL_JOB_BILLING_TITLE, BILL_EMPLOYEE_BILLING_TITLE, NET_ZERO_ADJUSTMENT_FLAG.
• Currency and rate detail: DENOM_CURRENCY_CODE, DENOM_RAW_COST, DENOM_BURDENED_COST, ACCT_CURRENCY_CODE, ACCT_RAW_COST, ACCT_BURDENED_COST, ACCT_RATE_TYPE, ACCT_RATE_DATE, ACCT_EXCHANGE_RATE, PROJECT_CURRENCY_CODE, PROJECT_RATE_TYPE, PROJECT_RATE_DATE, PROJECT_EXCHANGE_RATE, RECEIPT_CURRENCY_CODE, RECEIPT_CURRENCY_AMOUNT, RECEIPT_EXCHANGE_RATE.
• Descriptive and audit: EXPENDITURE_TYPE, TRANSACTION_SOURCE, NON_LABOR_RESOURCE, CONVERTED_FLAG, EXPENDITURE_ITEM_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY.

Several columns appear as literal placeholder expressions, such as '_LA:PEI.BILLABLE_FLAG:FND_LOOKUPS:YES_NO:MEANING'. These are late-binding lookup substitutions resolved by the reporting layer to translate code values into user-facing meanings via FND_LOOKUPS or PA_LOOKUPS. The descriptive flexfield column is represented by '_DF:PA:PA_EXPENDITURE_ITEMS_DESC_FLEX:PEI'.

Common Use Cases and Queries

Typical uses include project cost reporting, unbilled and unbilled receivable analysis, revenue accrual reconciliation, and feed into OBI dashboards. The view is also convenient for ad hoc analysis where a join between expenditure items and tasks is always required.

SELECT expenditure_item_id,
       project_id,
       task_id,
       expenditure_item_date,
       expenditure_type,
       raw_cost,
       burden_cost,
       bill_amount,
       billable_flag,
       org_id
  FROM apps.pabv_expenditure_items
 WHERE expenditure_item_date BETWEEN :start_date AND :end_date;

To analyze billing status for a project, one may aggregate bill amounts by expenditure type while filtering on bill hold and billable flags. Because the view is read-only and secured by ORG_ID, queries return only operating units for which the user is authorized, making it suitable for shared reporting responsibilities without exposing restricted data.