Results for “current_npw_flag”

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

Overview

PA_EXPENDITURES_V is a Projects (PA) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. The ETRM metadata describes it tersely as a "10SC Only" object, indicating that the view exists primarily to support the Oracle Projects self-service expenditure reporting flows and certain seeded concurrent programs and OAF pages rather than being a general-purpose public interface. It presents a denormalized, human-readable projection of expenditure batch headers stored in PA_EXPENDITURES, enriched with employee name and number attributes resolved from PER_ALL_PEOPLE_F. The view is not an interface table and carries no writable semantics; it is intended purely for query access within Oracle Projects reporting, workflow, and self-service logic. The underlying PA_EXPENDITURES table is the parent of expenditure batch and item records used in pre-approved, timecard, and expense report processing.

Underlying Base Objects

The view is defined over the following documented objects:

• PA_EXPENDITURES (synonym) — the primary base table supplying all expenditure batch header columns (rowid aliased as ROW_ID, expenditure identifiers, status codes, class codes, currency, control totals, and DFF attributes).
• PER_ALL_PEOPLE_F (synonym) — the HR people table, outer-joined on INCURRED_BY_PERSON_ID = PERSON_ID to resolve the incurred-by person's full name and employee/non-worker number.
• PA_EXPENDITURES_UTILS (package) — a PL/SQL package invoked within the view's SELECT list via PA_EXPENDITURES_UTILS.GETORGTLNAME to translate the incurred-by organization ID into a descriptive organization name.

The join to PER_ALL_PEOPLE_F is date-effective aware. The ROWID predicate restricts the result to the single people record effective on the expenditure ending date (with a six-day buffer) whose CURRENT_EMPLOYEE_FLAG or CURRENT_NPW_FLAG matches the E.PERSON_TYPE value ('CWK' selects non-worker data). The outer join allows expenditure rows with no matching person record to survive.

Key Columns

• ROW_ID, EXPENDITURE_ID — surrogate row and primary key of the expenditure batch header.
• EXPENDITURE_STATUS_CODE — workflow/approval status of the batch (e.g., Working, Submitted, Approved, Released).
• EXPENDITURE_ENDING_DATE — the batch period end date, also used to determine the effective people record.
• EXPENDITURE_CLASS_CODE — classification of the batch (e.g., expenditure batch, miscellaneous transaction, usages).
• INCURRED_BY_PERSON_ID / INCURRED_BY_EMPLOYEE_NAME / INCURRED_BY_EMPLOYEE_NUMBER — the person incurring the expenditure and the resolved display name and employee or non-worker number.
• INCURRED_BY_ORGANIZATION_ID / ORGANIZATION_NAME — incurring organization and its translated name.
• EXPENDITURE_GROUP, CONTROL_TOTAL_AMOUNT — batch grouping and the expected total amount used for control reconciliation.
• DENOM_CURRENCY_CODE, ACCT_CURRENCY_CODE, ACCT_RATE_DATE, ACCT_RATE_TYPE, ACCT_EXCHANGE_RATE — currency and accounting rate context for the batch.
• WF_STATUS_CODE, TRANSFER_STATUS_CODE — workflow and cost transfer status, relevant for cost distribution and interface processing.
• PERSON_TYPE — distinguishes employees from contingent workers and drives the people-table predicate.

Common Use Cases and Queries

Typical uses include operational reporting on pending expenditure batches, self-service screens that display a user's submitted expenditures, and diagnostics of currency or workflow status. Because the view is documented as self-service oriented, external interfaces should generally prefer base tables and the standard Projects public APIs. A representative query:

• SELECT expenditure_id, expenditure_ending_date, expenditure_status_code, incurred_by_employee_name, incurred_by_employee_number, organization_name, control_total_amount, acct_currency_code FROM pa_expenditures_v WHERE expenditure_ending_date BETWEEN :start_date AND :end_date AND expenditure_status_code = 'WORKING';
• Filter by incurred_by_person_id to retrieve a single user's expenditure history on a self-service page.
• Join expenditure_id to PA_EXPENDITURE_ITEMS_ALL for batch-to-line drill-down reporting.

Note that ORGANIZATION_NAME resolution depends on PA_EXPENDITURES_UTILS, so the view inherits that package's behavior and security context. Only select from this view; all modifications must flow through the supported Projects batch processing programs.