Results for “project_bill_amount”

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

Overview

The PJM_PROJECT_EXPEND_V view is an APPS-owned, VALID database object within the Oracle E-Business Suite Project Manufacturing (PJM) product family. Its documented purpose is to expose project expenditures for the Web Inquiry, meaning it functions as a flattened, ready-to-query reporting layer rather than as a transactional base table. Users searching for the term expenditure_org arrive at this view because it exposes EXPENDITURE_ORG as one of its projected columns, derived from the incurred-by or override organization logic embedded in the view definition.

Because the view already joins expenditure items, expenditure types, tasks, organizations, employees, jobs, and vendors, it removes the burden of reconstructing those relationships at query time. This makes it a convenient access point for inquiry screens, custom reports, and lightweight integrations that need a denormalized view of project cost and revenue data without touching the PA and HR base tables directly.

Underlying Base Objects

The view is defined over a documented set of base objects, several of which are synonyms and views rather than physical tables. The metadata lists:

• PA_EXPENDITURE_ITEMS_ALL and PA_EXPENDITURES_ALL — the core expenditure records (item-level and header-level).
• PA_EXPENDITURE_TYPES and PA_IMPLEMENTATIONS_ALL — expenditure categorization and implementation/org calibration.
• PA_TASKS — task context for each expenditure item.
• HR_ALL_ORGANIZATION_UNITS_TL — the organization name translations used for both the expenditure organization and the non-labor resource organization (aliased EO and NLO).
• PER_ALL_PEOPLE_F and PER_JOBS — the incurring person and job information.
• PO_VENDORS — supplier details for non-labor expenditure.
• PA_LOOKUPS — the unit-of-measure meaning lookup, restricted to LOOKUP_TYPE = 'UNIT'.
• PA_EXPENDITURE_INQUIRY and FND_CURRENCY_CACHE — packaged PL/SQL functions used for mode control and currency formatting.

The joins are largely outer joins (notably against organizations, jobs, people, and vendors), so expenditures without a fully populated master record still appear, which is important for completeness in reporting.

Key Columns

The view projects a broad set of identifiers, descriptive attributes, and formatted amounts. Notable columns include:

• PROJECT_ID, TASK_ID, TASK_NUMBER — the project and task context of the expenditure item.
• EXPENDITURE_ITEM_ID, EXPENDITURE_TYPE — the item identifier and its expenditure type.
• EXPENDITURE_CATEGORY, REVENUE_CATEGORY_CODE — categorization carried from the expenditure type.
• EXPENDITURE_ORG — the organization name, resolved via NVL(EI.OVERRIDE_TO_ORGANIZATION_ID, X.INCURRED_BY_ORGANIZATION_ID), which is why users searching for "expenditure_org" reach this object.
• EXPENDITURE_ITEM_DATE, QUANTITY, UOM — timing and units of measure.
• Burden cost, accrued revenue, and bill amount — each formatted through FND_CURRENCY_CACHE.GET_FORMAT_MASK using the accounting currency.
• NON_LABOR_RESOURCE and related name column — non-labor resource identification.
• INCURRED_BY_PERSON_ID, employee name and number, JOB_ID and job name — labor attribution.
• VENDOR_ID and vendor name — supplier attribution for non-labor items.

Common Use Cases and Queries

The view supports inquiry-style reporting on project expenditures. A typical query returns expenditure detail filtered by project or task:

• Listing all expenditures for a project with organization, person, and amounts.
• Aggregating burden cost or bill amount by EXPENDITURE_ORG to analyze spend by incurring organization.
• Filtering by EXPENDITURE_CATEGORY or REVENUE_CATEGORY_CODE for cost-versus-revenue review.
• Joining to dimension tables on PROJECT_ID or TASK_ID for cross-project reporting.

A representative statement is:

SELECT project_id, task_number, expenditure_org, expenditure_type, quantity, uom, burden_cost, bill_amount FROM apps.pjm_project_expend_v WHERE project_id = :p_project_id ORDER BY expenditure_item_date;

Because amounts are pre-formatted as character strings, arithmetic aggregation should be performed against the underlying PA tables if numeric totals are required. The view is best treated as a presentation and inquiry layer consistent with its documented purpose.