Results for “pjm_req_commitments_cmprj_v”

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

Overview

PJM_REQ_COMMITMENTS_CMPRJ_V is an APPS-owned, VALID database view within the Oracle E-Business Suite Project Manufacturing (PJM) module. It presents project-related purchase requisition distributions, consolidating requisition header, line, and distribution data into a single denormalized reporting structure. Its primary role is to expose the commitment detail required by Project Manufacturing and Project Costing processes, where requisition distributions that carry a project and task must be identified as commitments against project budgets.

The view is designed for reporting and integration rather than for direct transactional maintenance. It projects currency conversion information, unit of measure conversion factors, project and task identifiers, expenditure classification, and organization context in a form suitable for commitment reporting, project cost collection, and downstream integration with external systems or custom reports. Because it joins many base objects—including purchasing, projects, human resources, and general ledger entities—it is a convenient single source for a comprehensive requisition commitment extract.

Underlying Base Objects

The documented metadata lists the following referenced base objects: GL_SETS_OF_BOOKS (view), HR_ALL_ORGANIZATION_UNITS_TL (synonym), PA_EXPENDITURE_TYPES (synonym), PA_PROJECTS_ALL (synonym), PA_TASKS (synonym), PJM_COMMITMENT_UTILS (package), PO_REQUISITION_HEADERS_ALL (synonym), PO_REQUISITION_LINES_ALL (synonym), and PO_REQ_DISTRIBUTIONS_ALL (synonym).

The view text additionally references PO_DOCUMENT_TYPES_ALL_TL, PO_LINE_TYPES_B, PER_ALL_PEOPLE_F, and BOM_RESOURCES to supply document type, line type, requester, and resource information. GL_SETS_OF_BOOKS provides the functional currency context used in the currency DECODE logic. The project hierarchy is resolved through PA_PROJECTS_ALL and PA_TASKS, and expenditure classification through PA_EXPENDITURE_TYPES. HR_ALL_ORGANIZATION_UNITS_TL supplies the inventory organization name. PJM_COMMITMENT_UTILS is referenced in an inline subquery that resolves the effective project when the distribution does not carry a project directly, defaulting to POP.COMMON_PROJECT_ID.

Key Columns

The view exposes requisition identifiers (REQUISITION_HEADER_ID, REQUISITION_LINE_ID, DISTRIBUTION_ID) that link back to the purchasing tables. Project and task context is provided through PROJECT_ID, SEGMENT1, NAME, TASK_ID, TASK_NUMBER, and TASK_NAME.

Currency handling is significant. The view returns the effective currency code, the extended amount (NVL of currency and standard unit price multiplied by distribution quantity), the functional currency code from GL_SETS_OF_BOOKS, and DECODE-driven RATE_DATE, RATE_TYPE, and RATE columns that are nulled when the transaction currency equals the functional currency.

Unit of measure conversion is central to the columns the user searched for. The view returns UNIT_OF_MEASURE and UOM_CODE, and computes the transaction price as RL.UNIT_PRICE divided by NVL(R.UOM_CONVERSION_RATE, 1), the committed quantity as RD.REQ_LINE_QUANTITY multiplied by NVL(R.UOM_CONVERSION_RATE, 1), and the committed amount as quantity multiplied by unit price. Requester details (PERSON_ID, FULL_NAME), vendor information, need-by dates, item identifiers, and expenditure type/category columns complete the payload.

Common Use Cases and Queries

Typical use cases include project commitment reporting, reconciliation of requisition distributions to project budgets, and feeds into external cost or procurement analytics. A representative query filtered on project and effective UOM follows:

• SELECT project_id, task_number, requisition_header_id, requisition_line_id, distribution_id, unit_of_measure, uom_conversion_rate, requisition_line_quantity, unit_price FROM pjm_req_commitments_cmprj_v WHERE project_id = :p_project_id;
• SELECT requisition_header_id, project_id, task_name, expenditure_type, extended_amount FROM pjm_req_commitments_cmprj_v WHERE requisition_header_id = :p_header_id;
• SELECT project_id, SUM(requisition_line_quantity * NVL(uom_conversion_rate,1)) committed_qty FROM pjm_req_commitments_cmprj_v GROUP BY project_id;

Note that the view does not expose a literal UOM_CONVERSION_RATE column by name; conversion is applied inline. Reports requiring the raw factor must resolve it from BOM_RESOURCES or derive it from the committed and base quantity expressions.