Results for “po_rfqqt_document_status_v”

16 results




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

Overview

PO_RFQQT_DOCUMENT_STATUS_V is an APPS-owned database view in the Oracle Purchasing (PO) module, documented in ETRM as a retrofitted object designated "10SC ONLY." It presents the set of RFQ and quotation status codes available in Oracle E-Business Suite, excluding the code 'P'. Rather than storing transactional data, the view exposes reference lookup values that drive status selection and display on RFQ and quotation documents. In EBS 12.1.1 and 12.2.2, such views support inquiry-only presentation of valid statuses, enabling forms, reports, and integrations to render consistent status lists without directly querying the lookup table. The view's role is therefore that of a controlled reference source for RFQ/quote status values, suited for inquiry and display purposes rather than transactional processing.

Underlying Base Objects

The view is defined over two documented objects. Its primary source is PO_LOOKUP_CODES, itself a view in the APPS schema that surfaces Purchasing lookup code definitions. The view text filters PO_LOOKUP_CODES on LOOKUP_TYPE = 'RFQ/QUOTE STATUS' and excludes LOOKUP_CODE = 'P', returning only the active display values for RFQ and quotation status processing. The metadata also lists FND_GLOBAL (PACKAGE) among referenced objects; FND_GLOBAL supplies session context such as user and responsibility identifiers commonly used by EBS views for security and localization. Because the definition resolves against PO_LOOKUP_CODES, any change to the underlying lookup configuration is reflected automatically in the view, with no separate maintenance required.

Key Columns

The view exposes three columns, each carrying a specific meaning for RFQ/quote status display:

  • LOOKUP_CODE — The internal code identifying each RFQ/quote status value. This is the value stored on transactions and referenced in logic; the code 'P' is deliberately omitted from the result set.
  • DISPLAYED_FIELD — The user-facing label shown in forms, lists of values, and reports. It provides the readable status description presented to users.
  • DESCRIPTION — Additional descriptive text associated with the lookup code, offering extended meaning or context for the status.

Together these columns allow consumers to map an internal status code to its displayed and descriptive forms, a pattern consistent with Oracle's lookup-driven design.

Common Use Cases and Queries

The view is typically used to populate status lists of values, validate status codes entered on RFQ and quotation inquiries, and drive report parameters that filter by document status. A representative query retrieving all available RFQ/quote statuses is:

  • SELECT LOOKUP_CODE, DISPLAYED_FIELD, DESCRIPTION FROM APPS.PO_RFQQT_DOCUMENT_STATUS_V ORDER BY DISPLAYED_FIELD;
  • SELECT DISPLAYED_FIELD FROM APPS.PO_RFQQT_DOCUMENT_STATUS_V WHERE LOOKUP_CODE = :status_code; — to resolve a stored code to its display label.
  • SELECT LOOKUP_CODE FROM APPS.PO_RFQQT_DOCUMENT_STATUS_V WHERE DISPLAYED_FIELD = :label; — to derive the internal code from a user-entered label.

Because the view is inquiry-oriented and constrained to non-'P' statuses, it is best applied in reporting and integration extraction scenarios where an authoritative, filtered list of RFQ and quotation statuses is required. Note that the documented metadata describes this object as retrofitted and limited to 10SC scope, so its use should be confirmed against the specific EBS instance and patch level before relying on it in custom development.