Search Results po_reqexpress_headers_u1

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.ICX_PO_REQUISITION_TEMPLATES_V view belongs to the Oracle iProcurement (ICX) product family and is classified in the ETRM metadata as Obsolete. It exposes the data model supporting Oracle iProcurement requisition templates, also referred to as "requisition express" definitions. These templates allow organizations to predefine frequently ordered items, suggested suppliers, pricing, and default purchasing attributes so that requesters can create requisitions quickly without re-entering sourcing information.

The view consolidates the header and line level records from the requisition express tables together with denormalized descriptive information drawn from purchasing, inventory, human resources, and general ledger objects. Because the view is flagged obsolete, it is retained primarily for backward compatibility. Customers upgrading to EBS 12.1.1 or 12.2.2 should not build new customizations or reports against it; Oracle recommends using the supported iProcurement and purchasing APIs or replacement views instead. Existing reports that still reference the view will continue to function while the underlying tables are present, but they carry upgrade risk.

Underlying Base Objects

The view is defined over the following documented base objects:

• PO_REQEXPRESS_HEADERS and PO_REQEXPRESS_LINES — the primary header and line tables that store requisition template definitions.
• PO_HEADERS, PO_LINES, PO_LINE_TYPES, and PO_DOCUMENT_TYPES — supply document number, type, currency, price, and line type context.
• PO_VENDORS, PO_VENDOR_SITES, and PO_VENDOR_CONTACTS — resolve suggested supplier name, site code, and contact name.
• PER_PEOPLE_F — resolves the suggested buyer's full name.
• MTL_SYSTEM_ITEMS_KFV — supplies concatenated item segments and organization identifiers.
• GL_SETS_OF_BOOKS, GL_DAILY_CONVERSION_TYPES, and FINANCIALS_SYSTEM_PARAMETERS — provide currency and set-of-books context.
• PO_LOOKUP_CODES — resolves displayed field values.

The joins are predominantly outer joins (for example, PRL.SUGGESTED_VENDOR_ID = PV.VENDOR_ID(+)), ensuring template lines without a suggested supplier still appear. The header-to-line relationship is driven by the shared EXPRESS_NAME column. Because the definition references FND_GLOBAL, HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY packages, it is also subject to Oracle Applications row-level security and effective-dating logic when accessed at runtime.

Key Columns

• EXPRESS_NAME — identifies the requisition template.
• PO_HEADER_ID, PO_LINE_ID, SEGMENT1, LINE_NUM — link template content to purchase order context.
• SUGGESTED_VENDOR_ID, VENDOR_NAME — the recommended supplier for the line.
• SUGGESTED_VENDOR_SITE_ID, VENDOR_SITE_CODE — the suggested supplier site.
• SUGGESTED_VENDOR_CONTACT_ID — the suggested supplier contact. This is the column most directly relevant to the user's search. It is resolved through an outer join to PO_VENDOR_CONTACTS, and a derived DECODE expression returns the contact full name as LAST_NAME || ', ' || FIRST_NAME. A NULL value indicates no contact is suggested for that template line.
• SUGGESTED_VENDOR_PRODUCT_CODE, SUGGESTED_BUYER_ID, FULL_NAME — product code and suggested buyer with resolved name.
• UNIT_PRICE, RATE, CURRENCY_CODE — pricing and currency. A computed column returns ROUND(NVL(UNIT_PRICE,0) * NVL(RATE,1), 5).
• ITEM_ID, ITEM_DESCRIPTION, CATEGORY_ID, UNIT_MEAS_LOOKUP_CODE — item and unit-of-measure details.
• RFQ_REQUIRED_FLAG, SOURCE_TYPE_CODE, CONCATENATED_SEGMENTS — sourcing and item segment attributes.

Common Use Cases and Queries

The view is typically queried for reporting on template contents, auditing suggested sourcing defaults, or migrating template definitions during an upgrade. A common example retrieves template lines with their suggested vendor contact:

• SELECT express_name, sequence_num, item_description, vendor_name, vendor_site_code, suggested_vendor_contact_id FROM icx_po_requisition_templates_v WHERE suggested_vendor_contact_id IS NOT NULL;
• SELECT express_name, item_description, vendor_name, unit_price, rate, currency_code FROM icx_po_requisition_templates_v WHERE express_name = :p_template_name ORDER BY sequence_num;
• SELECT express_name, suggested_buyer_id, full_name, rfq_required_flag FROM icx_po_requisition_templates_v WHERE source_type_code = 'VENDOR';

Given the obsolete status, these queries are best used for one-time data extraction. New development should target supported purchasing and iProcurement APIs, and existing reports should be scheduled for remediation before the view is desupported.