Search Results po_document_types




Overview
Explore in AI Chat

Overview

APPS.ICX_PO_REQUISITION_TEMPLATES_V is a reporting view in Oracle E-Business Suite that exposes the contents of the Procurement Requisition Express (self-service requisition template) framework together with resolution of the referenced purchasing documents. It joins requisition express headers and lines (PO_REQEXPRESS_HEADERS and PO_REQEXPRESS_LINES) to purchase order headers and lines, item definitions, supplier data, and purchasing document type lookups. In this respect, it is the denormalized representation of a requisition template: the template header, its lines, and the defaulted purchasing attributes attached to each template line.

The view primarily supports the Oracle iProcurement / e-Procurement module, whose internal schema is ICX. It is widely used for diagnostics, reconciliation, and custom reporting on template definitions, and it is frequently scanned when developers search for po_document_types content because the view resolves document type lookup codes into their display names in two places. The view text contains the ORDERED hint and explicit index hints (INDEX(PRH PO_REQEXPRESS_HEADERS_U1), INDEX(HRE PER_PEOPLE_F_PK)), indicating it is designed for direct query rather than for modification.

Underlying Base Objects

The ETRM metadata documents the following referenced base objects: FINANCIALS_SYSTEM_PARAMETERS (synonym), FND_GLOBAL (package), GL_DAILY_CONVERSION_TYPES (synonym), GL_SETS_OF_BOOKS (view), HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY (packages), MTL_SYSTEM_ITEMS_KFV (synonym), PER_PEOPLE_F (view), PO_DOCUMENT_TYPES (synonym), PO_HEADERS (synonym), PO_LINES (synonym), PO_LINE_TYPES (synonym), PO_LOOKUP_CODES (view), PO_REQEXPRESS_HEADERS (synonym), PO_REQEXPRESS_LINES (synonym), PO_VENDORS (view), PO_VENDOR_CONTACTS (view), and PO_VENDOR_SITES (view).

Two instances of PO_DOCUMENT_TYPES appear in the FROM clause (aliased PDT and PDT1). The first resolves the document type of the template header (PRH.TYPE_LOOKUP_CODE), and the second resolves the document type of the referenced purchase order header (PH.TYPE_LOOKUP_CODE). This double reference is the reason a search on po_document_types surfaces this view. The HR_* packages are not used in the SQL but are required grants for the column-level security applied through PER_PEOPLE_F and the buyer name resolution.

Key Columns

Common Use Cases and Queries

Typical scenarios include auditing which document types are applied to requisition templates versus their referenced purchase orders, extracting template lines for supplier and buyer analysis, and validating item/category defaults before populating iProcurement.

  • List templates with their header and PO document type names:
SELECT express_name, type_lookup_code, type_name,
       ph_type_lookup_code, pdt1_type_name
FROM   apps.icx_po_requisition_templates_v;
  • Filter templates by a specific purchasing document type (the po_document_types search):
SELECT express_name, type_name, segment1, vendor_name
FROM   apps.icx_po_requisition_templates_v
WHERE  pdt1_type_name = 'Purchase Order'
   OR  type_name      = 'Purchase Order';
  • Extract supplier and line defaults for a template:
SELECT express_name, sequence_num, line_num, item_description,
       unit_price, vendor_name, vendor_site_code, full_name
FROM   apps.icx_po_requisition_templates_v
WHERE  express_name = :p_express_name
ORDER  BY sequence_num;

Because the view performs many outer joins and resolves HR columns, ad hoc queries should include a narrowing predicate on EXPRESS_NAME or on the document type columns where possible; this allows the ORDERED hint and the index hints on PO_REQEXPRESS_HEADERS to be exploited effectively.