Search Results po_document_types_b




Overview
Explore in AI Chat

Overview

APPS.PO_RFQQT_DOCUMENT_TYPES_ALL_V is a reporting view in the Oracle E-Business Suite Purchasing (PO) module that exposes the set of active, quotation-class document types available for RFQ and quotation processing. It consolidates descriptive, translatable type names with their base document type codes, subtype codes, quotation class classifications, and the originating operating unit (ORG_ID).

In Oracle EBS 12.1.1 and 12.2.2 the Purchasing module maintains RFQ document types through two linked entities: a base table (PO_DOCUMENT_TYPES_B) holding code-level attributes and a translation table (PO_DOCUMENT_TYPES_ALL_TL) holding language-specific display names. This view joins both alongside the QUOTATION CLASS lookup, presenting a single denormalized result set. It is commonly used in reporting, personalizations, custom concurrent programs, and integration layers that must enumerate valid RFQ/quotation document types without reproducing the underlying join logic.

Note that the view is scoped by language and by operating unit. It returns only enabled document types (DISABLED_FLAG = 'N') whose language matches the session language, so results differ by user environment and organization.

Underlying Base Objects

Per the documented view text, PO_RFQQT_DOCUMENT_TYPES_ALL_V is defined over three sources:

  • PO_DOCUMENT_TYPES_ALL_TL (synonym) — the translation (TL) table supplying the user-facing TYPE_NAME, filtered by LANGUAGE = USERENV('LANG') so only the current session language is returned.
  • PO_DOCUMENT_TYPES_B (synonym) — the base table providing DOCUMENT_TYPE_CODE, DOCUMENT_SUBTYPE, QUOTATION_CLASS_CODE, ORG_ID, and the DISABLED_FLAG used to exclude inactive records.
  • PO_LOOKUP_CODES (view) — a lookup view used to resolve the QUOTATION CLASS lookup code into its DISPLAYED_FIELD (display meaning) where LOOKUP_TYPE = 'QUOTATION CLASS'.
  • FND_GLOBAL (package) — referenced implicitly through the language resolution (USERENV('LANG')) tied to the application session context.

The join conditions require PODB.DOCUMENT_TYPE_CODE = PODT.DOCUMENT_TYPE_CODE and PODB.DOCUMENT_SUBTYPE = PODT.DOCUMENT_SUBTYPE, ensuring the translated name matches not only the type but also the subtype. PODT.ORG_ID = PODB.ORG_ID further ensures that translation and base rows belong to the same operating unit.

Key Columns

  • TYPE_NAME — the translated, language-specific display name of the document type (from the TL table). This is the value typically shown to end users.
  • DOCUMENT_TYPE_CODE — the internal code identifying the purchasing document type (for example, RFQ, QUOTATION).
  • DOCUMENT_SUBTYPE — the subtype within the document type, allowing finer classification of RFQ/quotation variants.
  • QUOTATION_CLASS_CODE — the lookup code classifying the quotation class for the document type.
  • DISPLAYED_FIELD — the display meaning returned from PO_LOOKUP_CODES for the QUOTATION CLASS lookup, providing a readable description of the quotation class.
  • ORG_ID — the operating unit identifier, enabling business-unit-restricted reporting.

Common Use Cases and Queries

Typical uses include LOV-style lookups of enabled RFQ document types for the current organization and language, validation of document type/subtype combinations in interfaces, and reporting on which quotation classes are enabled across operating units.

Retrieve active document types for the session's organization and language:

  • SELECT document_type_code, document_subtype, type_name, quotation_class_code, displayed_field, org_id FROM apps.po_rfqqt_document_types_all_v ORDER BY type_name;

Filter by operating unit and quotation class:

  • SELECT type_name, document_type_code, quotation_class_code FROM apps.po_rfqqt_document_types_all_v WHERE org_id = :p_org_id AND quotation_class_code = :p_class;

Resolve a readable quotation class meaning for validation or interface mapping:

  • SELECT document_type_code, document_subtype, type_name, displayed_field FROM apps.po_rfqqt_document_types_all_v WHERE document_type_code = 'RFQ';

Because results are filtered by DISABLED_FLAG and session language, callers should set the correct language and operating unit context before relying on this view for automation, and should never assume a fixed row count.