Search Results displayed_field




Overview
Explore in AI Chat

Overview

APPS.PO_DOCUMENT_TYPES_V is a Purchasing (PO) module view that presents the configured document types used throughout Oracle E-Business Suite procurement and sourcing. It joins the base configuration table PO_DOCUMENT_TYPES with lookup-code view PO_LOOKUP_CODES to translate stored lookup codes into human-readable descriptions. Rather than exposing raw codes such as SECURITY_LEVEL_CODE or DOCUMENT_SUBTYPE, the view exposes the corresponding DISPLAYED_FIELD values (aliased as shown in the view text), making it suitable for reports, LOVs, and integrations that require meaningful labels rather than internal codes.

Because it is a reporting-friendly view, PO_DOCUMENT_TYPES_V is commonly referenced where purchasing document behavior must be understood — for example determining whether a preparer may approve, whether an approver may modify a document, and which workflow item types and processes drive the approval flow. The view also surfaces AME transaction type and template codes, supporting approval-management and contract-sourcing configuration across 12.1.1 and 12.2.2.

Underlying Base Objects

The documented base objects underlying this view are:

  • PO_DOCUMENT_TYPES (SYNONYM) — the primary configuration table supplying document type, subtype, security level, approval flags, attribute columns, workflow configuration, ORG_ID, and AME/template settings.
  • PO_LOOKUP_CODES (VIEW) — referenced seven times (aliases LC1 through LC7) to resolve codes into DISPLAYED_FIELD descriptions for document type, subtype, security level, quotation class, archive external revision, access level, and forwarding mode.
  • PER_POSITION_STRUCTURES (SYNONYM) — joined via DEFAULT_APPROVAL_PATH_ID to PPS.NAME to supply the default approval path name.
  • FND_GLOBAL (PACKAGE) — used within the view definition to enforce organizational/security context (e.g., ORG_ID handling).

All joins are performed with outer joins (+) to the lookup view for optional code categories, ensuring rows are retained even when a given lookup code has no matching description.

Key Columns

Common Use Cases and Queries

Typical uses include populating document-type LOVs, validating approval configuration, and reporting on source-to-pay behavior by operating unit. A representative query retrieves active document types with their displayed descriptions and approval flags for an organization:

  • SELECT DOCUMENT_TYPE_CODE, DISPLAYED_FIELD, TYPE_NAME, CAN_PREPARER_APPROVE_FLAG, AME_TRANSACTION_TYPE FROM APPS.PO_DOCUMENT_TYPES_V WHERE DISABLED_FLAG = 'N' AND ORG_ID = :p_org_id;

A second scenario resolves the default approval path and workflow configuration for a specific document type:

  • SELECT DOCUMENT_TYPE_CODE, DOCUMENT_SUBTYPE, NAME, WF_APPROVAL_ITEMTYPE, WF_APPROVAL_PROCESS FROM APPS.PO_DOCUMENT_TYPES_V WHERE DOCUMENT_TYPE_CODE = 'PURCHASE ORDER';

Because the view resolves lookup codes to displayed values, it is preferable to direct table access when building reports, interfaces, and integrations requiring readable procurement document-type configuration.