Search Results po_document_types_vl




Overview
Explore in AI Chat

Overview

PO_DOCUMENT_TYPES_VL is a seeded, read-only view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is registered in the ETRM repository as a VIEW with VALID status, and it belongs to the Purchasing (PO) product family. The view presents document type and document subtype definitions used by Oracle Purchasing, including the sourcing, approval, forwarding, and security attributes that govern how each purchasing document behaves during entry and approval.

Because it exposes translated document type names alongside their configuration flags, PO_DOCUMENT_TYPES_VL serves as the primary reporting and integration surface for purchasing document definitions. It joins the base configuration table to its translation table and filters to the session language, so consumers see a human-readable TYPE_NAME rather than a raw code alone. The view is derived from PO_DOCUMENT_TYPES_B and PO_DOCUMENT_TYPES_ALL_TL, and in the documented 12.2.2 metadata both base objects are referenced as synonyms. The "_VL" suffix follows the standard EBS convention for a view that combines a base detail table with a corresponding "_TL" translation table.

Underlying Base Objects

The view is defined over two documented base objects: PO_DOCUMENT_TYPES_B (SYNONYM) and PO_DOCUMENT_TYPES_ALL_TL (SYNONYM). The view text performs an inner join between the translation table (aliased T) and the base table (aliased B) on three keys: DOCUMENT_TYPE_CODE, DOCUMENT_SUBTYPE, and ORG_ID. The join is further restricted by the clause T.LANGUAGE = USERENV('LANG'), which returns only the rows matching the current session language. The SELECT list projects all base-table columns from B in full and adds the translated TYPE_NAME from T. The presence of ORG_ID in both the join and the projected columns confirms that the view is multi-org aware; document type behavior can differ by operating unit.

Key Columns

Common Use Cases and Queries

Typical scenarios include validating which document subtypes are enabled in a given operating unit, tracing the workflow processes assigned to a document type, and building reports that display translated type names for purchasing transactions. The following query lists active, enabled document types with their translated names and assigned approval workflow:

SELECT dt.DOCUMENT_TYPE_CODE,
       dt.DOCUMENT_SUBTYPE,
       dt.TYPE_NAME,
       dt.DISABLED_FLAG,
       dt.WF_APPROVAL_ITEMTYPE,
       dt.WF_APPROVAL_PROCESS
FROM   PO_DOCUMENT_TYPES_VL dt
WHERE  dt.DISABLED_FLAG = 'N'
ORDER BY dt.DOCUMENT_TYPE_CODE, dt.DOCUMENT_SUBTYPE;

To inspect the approval and forwarding controls for a single subtype within an operating unit:

SELECT dt.TYPE_NAME,
       dt.CAN_PREPARER_APPROVE_FLAG,
       dt.CAN_APPROVER_MODIFY_DOC_FLAG,
       dt.DEFAULT_APPROVAL_PATH_ID,
       dt.AME_TRANSACTION_TYPE
FROM   PO_DOCUMENT_TYPES_VL dt
WHERE  dt.DOCUMENT_TYPE_CODE = '&type_code'
AND    dt.DOCUMENT_SUBTYPE   = '&subtype'
AND    dt.ORG_ID             = &org_id;

Because the view already resolves language and multi-org context, it is preferred over querying the underlying base tables directly. It can be joined to PO_HEADERS_ALL or PO_APPROVAL_LIST_HEADERS to drive document-type-aware reports.