Results for “pa_expend_items_adjust2_mrc_v”

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

Overview

PA_EXPEND_ITEMS_ADJUST2_MRC_V is a Projects (PA) module multi-reporting-currency (MRC) view in Oracle EBS 12.1.1 and 12.2.2. It exposes expenditure item adjustment data alongside the associated project, task, expenditure type, employee, organization, and non-labor resource attributes. The "_MRC_" suffix indicates that the view is intended to surface data across reporting currency contexts, which is consistent with the multi-org/multi-currency reporting requirement for project expenditures. The view is documented as "Not implemented in this database," meaning it may not exist in every environment; availability depends on whether the relevant MRC schema objects have been deployed.

For users searching on "wip_resource," it is relevant because the view includes non-labor resource columns such as NON_LABOR_RESOURCE and NLR_ORGANIZATION_ID/NAME, which are used to identify resources that may originate from Oracle Work in Process (WIP) resource transactions. The view is therefore useful when reconciling project expenditures that trace back to manufacturing or WIP resource consumption.

Underlying Base Objects

The ETRM metadata records no documented base objects for this view, but the view text references several tables and PL/SQL utilities. The primary tables include PA_EXPENDITURE_ITEMS (aliased EI), PA_EXPENDITURES (X), PA_PROJECTS (P), PA_PROJECT_TYPES (PT), PA_TASKS (T), PA_EXPENDITURE_TYPES, PA_EXPENDITURE_COMMENTS, PER_ALL_PEOPLE_F (P), and PA_JOBS (J). Additional lookups are performed through ORGANIZATIONS (O1) and utility functions such as PA_EXPENDITURES_UTILS.GETORGTLNAME and PA_UTILS4.GET_UNIT_OF_MEASURE. The view joins these objects on expenditure item identifiers, project/task keys, person identifiers, and organization identifiers to produce a consolidated adjustment-oriented record set.

Key Columns

• EXPENDITURE_ITEM_ID / EXPENDITURE_ID — Primary and parent identifiers linking the adjustment to the expenditure item and expenditure header.
• PROJECT_ID, PROJECT_NUMBER, PROJECT_NAME — Project identification and descriptive attributes.
• PROJECT_TYPE, PROJECT_TYPE_CLASS_CODE — Classification of the project.
• TASK_ID, TASK_NUMBER, TASK_NAME — Task-level context for the expenditure item.
• EXPENDITURE_ITEM_DATE, EXPENDITURE_TYPE, EXPENDITURE_CATEGORY — Date and categorization of the transaction.
• INCURRED_BY_PERSON_ID, EMPLOYEE_NAME, EMPLOYEE_NUMBER — Person who incurred the cost, with effective-dated lookups.
• JOB_ID, JOB_NAME — Job associated with the incurring person.
• EXPENDITURE_ORGANIZATION_ID/NAME — Organization to which the expenditure is assigned, derived from NVL(OVERRIDE_TO_ORGANIZATION_ID, INCURRED_BY_ORGANIZATION_ID).
• NON_LABOR_RESOURCE, NLR_ORGANIZATION_ID, NLR_ORGANIZATION_NAME — Non-labor resource details, directly relevant to WIP resource tracing.
• QUANTITY, BURDEN_COST, UNIT_OF_MEASURE — Measures and cost attributes for the adjustment.
• TRANSACTION_SOURCE, ORIG_TRANSACTION_REFERENCE, EXPENDITURE_STATUS_CODE — Source and status metadata for audit and reconciliation.

Common Use Cases and Queries

Typical use cases include reconciling expenditure adjustments, auditing non-labor resources originating from WIP, and reporting expenditure data with employee and organization detail.

Sample query:

SELECT EXPENDITURE_ITEM_ID, PROJECT_NUMBER, TASK_NUMBER, EXPENDITURE_TYPE, NON_LABOR_RESOURCE, NLR_ORGANIZATION_NAME, QUANTITY, BURDEN_COST FROM PA_EXPEND_ITEMS_ADJUST2_MRC_V WHERE NON_LABOR_RESOURCE IS NOT NULL;

Additional queries may filter by EXPENDITURE_ITEM_DATE or TRANSACTION_SOURCE to isolate adjustments tied to specific WIP resource transactions.