Search Results reply_date

Overview

APPS.PJM_PROJECT_RFQ_V is a Project Manufacturing (PJM) reporting view that consolidates project-related Request for Quotation (RFQ) information for consumption by a Web Inquiry interface. It joins purchasing RFQ headers, lines, supplier (vendor) records, supplier sites, and supplier contacts, and projects each row against a specific project and task combination. The object is owned by the APPS schema and is documented as VALID in ETRM for release levels 12.1.1 and 12.2.2.

The view is read-only by design; it does not own data. Its purpose is to present a denormalized, inquiry-friendly projection of RFQ data so downstream web inquiry pages or custom self-service reporting can display which suppliers were solicited, at which site and contact, for a given project and task, together with status, buyer, and key dates.

Underlying Base Objects

The documented 12.2.2 metadata lists the following referenced base objects: AP_SUPPLIER_CONTACTS (synonym), FND_GLOBAL (package), HZ_PARTIES (synonym), PO_HEADERS_ALL (synonym), PO_INQ_SV (package), PO_LINES_ALL (synonym), PO_LOOKUP_CODES (view), PO_RFQ_VENDORS (synonym), PO_VENDORS (view), and PO_VENDOR_SITES_ALL (view).

The view text in the ETRM excerpt shows the core join path: PO_HEADERS is restricted to TYPE_LOOKUP_CODE = 'RFQ'; PO_LINES supplies PROJECT_ID and TASK_ID; PO_RFQ_VENDORS links solicited suppliers; PO_VENDORS and PO_VENDOR_SITES supply supplier name and site code; and PO_VENDOR_CONTACTS supplies contact name. PO_LOOKUP_CODES is outer-joined to translate the RFQ status lookup code for the 'RFQ/QUOTE STATUS' lookup type, defaulting to 'I' when no status is present. Supplier-related joins are outer joins, so RFQs without a supplier, site, or contact still return a row.

Key Columns

• PROJECT_ID, TASK_ID — Project and task identifiers derived from the RFQ line, anchoring the row to a project manufacturing context.
• PO_HEADER_ID — Primary key of the RFQ header; useful for drill-down joins back to purchasing.
• RFQ_NUMBER — The RFQ document number (mapped from PO_HEADERS.SEGMENT1).
• STATUS — Decoded RFQ/quote status derived from PO_LOOKUP_CODES.DISPLAYED_FIELD.
• BUYER_ID, BUYER_NAME — The purchasing agent; the name is returned via PO_INQ_SV.GET_PERSON_NAME(POH.AGENT_ID).
• SUPPLIER_ID, SUPPLIER_NAME, SUPPLIER_SITE_ID, SUPPLIER_SITE_CODE — Solicited supplier, its site, and site code.
• SUPPLIER_CONTACT_ID, SUPPLIER_CONTACT, SUPPLIER_CONTACT_NAME — Contact at the supplier, formatted as last name and first name.
• REPLY_DATE, CLOSE_DATE — RFQ reply deadline (POH.REPLY_DATE) and RFQ close date.

Common Use Cases and Queries

Typical usage is to power project-level supplier solicitation inquiries, or to extract RFQ activity for a project for audit and status tracking.

Retrieve all suppliers solicited on a given project:

SELECT rfq_number, status, supplier_name, supplier_site_code,
       supplier_contact_name, reply_date, close_date
FROM   apps.pjm_project_rfq_v
WHERE  project_id = :p_project_id
ORDER  BY rfq_number;

List open RFQs approaching their reply date:

SELECT rfq_number, buyer_name, supplier_name, supplier_site_code, reply_date
FROM   apps.pjm_project_rfq_v
WHERE  close_date >= SYSDATE
ORDER  BY reply_date;

Count responses solicited per supplier site for a task:

SELECT supplier_site_code, COUNT(*) AS rfq_count
FROM   apps.pjm_project_rfq_v
WHERE  project_id = :p_project_id AND task_id = :p_task_id
GROUP  BY supplier_site_code;