Search Results po_document_types_all_vl




Overview
Explore in AI Chat

Overview

PO_DOCUMENT_TYPES_ALL_VL is a multilingual (VL) view in the APPS schema that consolidates purchasing document type definitions for Oracle E-Business Suite releases 12.1.1 and 12.2.2. It presents the translatable name of each document type alongside the full set of configuration attributes that govern approval routing, security, sourcing, and contract behavior. Because it is a VL view, it joins the language-independent base table to its translation table and filters rows using USERENV('LANG'), so each query returns document type names in the session's current language.

In reporting and integration scenarios, the view serves as the authoritative reference for resolving a DOCUMENT_TYPE_CODE / DOCUMENT_SUBTYPE combination into a user-facing type name and its behavioral flags. Users searching for the column CONTRACT_TEMPLATE_CODE are typically attempting to identify which purchasing document types are associated with contract templates, or to trace how a template is linked to a specific type configuration. That column is exposed directly by this view, as are related contract and sourcing attributes such as DOCUMENT_TEMPLATE_CODE and USE_CONTRACT_FOR_SOURCING_FLAG.

Underlying Base Objects

The view is defined over two documented base objects, both accessed through APPS synonyms:

  • PO_DOCUMENT_TYPES_ALL_B — the language-independent base table holding the operational columns (organization, document type code, subtype, approval workflow settings, security levels, descriptive flexfield attributes, and the contract/template columns including CONTRACT_TEMPLATE_CODE).
  • PO_DOCUMENT_TYPES_ALL_TL — the translation table supplying TYPE_NAME in the session language.

The join condition matches DOCUMENT_TYPE_CODE, DOCUMENT_SUBTYPE, and ORG_ID across both tables, and restricts T.LANGUAGE to USERENV('LANG'). The view also derives ROW_ID from B.ROWID. Note that although the base table name contains "ALL," the view is not automatically filtered by org; consumers must apply their own ORG_ID predicate where multi-org isolation is required.

Key Columns

Common Use Cases and Queries

Typical scenarios include populating LOVs with valid document types, auditing which types are enabled for a given operating unit, and joining to transaction tables to translate codes into names. A common query returns active document types with their contract and sourcing configuration:

  • Resolve names for a reporting join: SELECT pdt.DOCUMENT_TYPE_CODE, pdt.DOCUMENT_SUBTYPE, pdt.TYPE_NAME FROM PO_DOCUMENT_TYPES_ALL_VL pdt WHERE pdt.ORG_ID = :org_id AND pdt.DISABLED_FLAG = 'N';
  • Find types tied to contract templates (relevant to the user's search): SELECT pdt.ORG_ID, pdt.DOCUMENT_TYPE_CODE, pdt.DOCUMENT_SUBTYPE, pdt.TYPE_NAME, pdt.CONTRACT_TEMPLATE_CODE FROM PO_DOCUMENT_TYPES_ALL_VL pdt WHERE pdt.CONTRACT_TEMPLATE_CODE IS NOT NULL;
  • Audit approval configuration: SELECT pdt.DOCUMENT_TYPE_CODE, pdt.TYPE_NAME, pdt.WF_APPROVAL_PROCESS, pdt.CAN_PREPARER_APPROVE_FLAG FROM PO_DOCUMENT_TYPES_ALL_VL pdt WHERE pdt.ORG_ID = :org_id;

Because the view filters on the session language, integrated applications and concurrent programs should confirm that the querying session's language is initialized; otherwise TYPE_NAME may return no rows for types lacking a translation in that language.