Results for “pjm_project_req_v”

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

Overview

PJM_PROJECT_REQ_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Project Manufacturing (PJM) module. It exposes project-related purchase requisition information for consumption by the Web Inquiry interface, consolidating requisition header, distribution, action history, and item data into a single denormalized result set suitable for online enquiry screens. The view is documented as VALID and is present across both 12.1.1 and 12.2.2 releases.

The view performs a multi-table join across purchasing, human resources, general ledger, and inventory schemas, with Oracle-style outer joins applied to status lookup codes, preparer records, and action history. This design allows incomplete or unprocessed requisitions (for example, those lacking an authorization status) to remain visible in the inquiry without being filtered out. Notably, the view exposes the PLC_STA.DISPLAYED_FIELD column, which resolves the requisition authorization status code into a user-readable description by joining PO_LOOKUP_CODES under the lookup type 'AUTHORIZATION STATUS'.

Underlying Base Objects

The view is defined over the following documented base objects:

• PO_REQUISITION_HEADERS_ALL and PO_REQUISITION_LINES_ALL — requisition header and line records.
• PO_REQ_DISTRIBUTIONS_ALL — distribution-level project and task references.
• PO_LOOKUP_CODES (view) — supplies authorization status descriptions; aliased PLC_STA for the header status.
• PO_DOCUMENT_TYPES_ALL — restricts results to requisition document types.
• PO_ACTION_HISTORY — provides the most recent action and the responsible employee, correlated through a MAX(SEQUENCE_NUM) subquery.
• PER_ALL_PEOPLE_F — resolves preparer and action employee names from PERSON_ID with effective-dated joins.
• GL_SETS_OF_BOOKS and FINANCIALS_SYSTEM_PARAMS_ALL — supply the ledger currency code used for formatting.
• MTL_SYSTEM_ITEMS_KFV — item concatenated segments and descriptions.
• PJM_INQUIRY and FND_CURRENCY_CACHE (packages) — encapsulate the YES_NO flag translation and currency format mask.
• FND_GLOBAL — session context used by the enquiry layer.

Key Columns

• PROJECT_ID, TASK_ID — project and task identifiers from the requisition distribution.
• REQUISITION_HEADER_ID, SEGMENT1 — unique key and requisition number.
• DESCRIPTION, TYPE_LOOKUP_CODE, CREATION_DATE — header descriptive attributes.
• DISPLAYED_FIELD — the authorization status description derived from PO_LOOKUP_CODES (the PLC_STA alias).
• PREPARER_ID and associated FULL_NAME columns — requisition preparer and action-taking employee.
• CURRENCY_CODE and the formatted requisition total returned via PO_REQUISITION_HEADERS_PKG.GET_REQ_TOTAL.
• CONCATENATED_SEGMENTS, ITEM_DESCRIPTION, END_ITEM_UNIT_NUMBER — item and end-item context for project manufacturing.
• Translated closed and cancelled flags rendered through PJM_INQUIRY.YES_NO.

Common Use Cases and Queries

The view is typically queried to support project procurement enquiry screens and ad-hoc reporting on requisitions tied to a project or task.

Listing requisitions by project with status:

SELECT SEGMENT1, DISPLAYED_FIELD, DESCRIPTION, CREATION_DATE
FROM   APPS.PJM_PROJECT_REQ_V
WHERE  PROJECT_ID = :p_project_id;

Filtering by authorization status (the plc_sta alias resolves to DISPLAYED_FIELD):

SELECT REQUISITION_HEADER_ID, SEGMENT1, DISPLAYED_FIELD
FROM   APPS.PJM_PROJECT_REQ_V
WHERE  DISPLAYED_FIELD = 'Approved';

Retrieving item detail for a specific requisition:

SELECT SEGMENT1, ITEM_DESCRIPTION, CONCATENATED_SEGMENTS, END_ITEM_UNIT_NUMBER
FROM   APPS.PJM_PROJECT_REQ_V
WHERE  SEGMENT1 = :req_number;

Because the view already applies DISTINCT and joins the latest action history row, it is well suited to direct enquiry without additional aggregation.