Search Results quotation_type




Overview
Explore in AI Chat

Overview

APPS.PJM_PROJECT_QUOT_V is a valid Oracle E-Business Suite database view owned by the APPS schema and registered under FND Design Data as PJM.PJM_PROJECT_QUOT_V. It is classified as a Web view, a construct designed to simplify access from Oracle Self-Service Web Applications. Its purpose is to expose project-related quotation information, and it corresponds directly to the Quotations web inquiry region within Oracle Projects. In EBS 12.1.1 and 12.2.2, the view serves as a reporting and integration surface that joins project and task context to procurement quotation data maintained in Oracle Purchasing.

The view is read-only by nature and is not referenced by any other database object, confirming its role as a terminal presentation layer rather than a component of a dependency chain. The metadata records its status as VALID, indicating a successfully compiled definition with resolvable dependencies at the time of extraction.

Underlying Base Objects

PJM_PROJECT_QUOT_V is defined over a combination of Purchasing tables, lookup and vendor views, and a global context package. The documented dependencies are:

  • PO_HEADERS_ALL (synonym) — the quotation and purchase order header records that supply quotation number, type, class, status, dates, and buyer information.
  • PO_LINES_ALL (synonym) — line-level procurement detail associated with the header, used to link quotations to project and task references.
  • PO_VENDORS (view) — resolves supplier identifiers to supplier names.
  • PO_LOOKUP_CODES (view) — translates stored lookup codes into the descriptive values presented for quotation type, class, and status.
  • PO_INQ_SV (package) — a Purchasing inquiry server-side package supplying quotation inquiry logic.
  • FND_GLOBAL (package) — provides session context such as the current operating unit, applied through ORG_ID for multi-org security filtering.

The view therefore bridges Oracle Projects project/task identifiers with Oracle Purchasing sourcing data, applying lookup decoding and organizational access controls.

Key Columns

The view exposes sixteen columns. PROJECT_ID and TASK_ID are the system-generated identifiers for the project or seiban and its task, providing the Projects context. PO_HEADER_ID is the purchase order header unique identifier. QUOTATION_NUMBER (VARCHAR2(20)) is the human-readable quotation reference, while QUOTATION_TYPE, QUOTATION_CLASS, and QUOTATION_STATUS (each VARCHAR2(80)) are decoded descriptive values sourced through PO_LOOKUP_CODES.

QUOTATION_STATUS is the column most commonly targeted by users searching for quotation_status; it reports the current lifecycle state of the quotation in descriptive form. RFQ_ID and RFQ_NUMBER identify the originating Request For Quotation. EFFECTIVE_DATE and EXPIRATION_DATE bound the validity period of the quotation. SUPPLIER_ID and SUPPLIER_NAME identify the responding supplier, and BUYER_ID and BUYER_NAME identify the responsible buyer. ORG_ID carries the operating unit identifier used for multi-org filtering via FND_GLOBAL.

Common Use Cases and Queries

Typical uses include project procurement inquiry screens, supplier quotation status reporting, and integration extracts that require quotations linked to specific projects or tasks. A baseline query follows the documented query text:

  • SELECT PROJECT_ID, TASK_ID, QUOTATION_NUMBER, QUOTATION_STATUS, SUPPLIER_NAME, EFFECTIVE_DATE, EXPIRATION_DATE FROM APPS.PJM_PROJECT_QUOT_V;
  • Filtering by status: add WHERE QUOTATION_STATUS = :status to isolate quotations in a given state.
  • Project-scoped reporting: add WHERE PROJECT_ID = :project_id to return all quotations for a project, optionally narrowing with TASK_ID.
  • Validity analysis: compare EFFECTIVE_DATE and EXPIRATION_DATE against SYSDATE to identify active or lapsed quotations.

Because ORG_ID is exposed, queries should respect operating unit security, either by relying on FND_GLOBAL session context or by constraining ORG_ID explicitly in reporting extracts.