Search Results contract_rate_type




Overview

ICX_POR_REQ_TEMPLATES is an APPS-owned view in the Oracle iProcurement (ICX) module. It consolidates requisition template content from the Oracle Purchasing "ReqExpress" framework — the underlying mechanism that populates iProcurement's stored requisition templates and personal lists. The view presents template headers and their associated template lines as a single, uniformly shaped result set, sourced from PO_REQEXPRESS_HEADERS_ALL and PO_REQEXPRESS_LINES_ALL, and enriched with supplier, unit of measure, and currency attributes.

The view exists primarily to expose requisition template data to the iProcurement storefront in a format that mirrors the structure of a sourcing or contract line, which allows the storefront to render templates, punchout content, and contract-style shopping lines through a single read interface. Its status is VALID in Oracle EBS 12.1.1 and 12.2.2, and it is queried at runtime by iProcurement pages as well as by custom reporting and integration routines that need template line detail.

Underlying Base Objects

The view is defined over a join of several documented objects:

The first SELECT branch handles pure template lines (PO_HEADER_ID IS NULL); the UNION branch supplies contract-linked lines with real CONTRACT_NUM and CONTRACT_LINE values.

Key Columns

Common Use Cases and Queries

Typical uses include auditing template content, confirming which templates carry contract-linked lines, and joining template lines to supplier or item masters for reporting. Sample query:

SELECT template_id, template_line_id, contract_num, contract_line,
       item_description, unit_of_measure, contract_price,
       supplier, supplier_site_code, operating_unit_id
FROM   apps.icx_por_req_templates
WHERE  contract_line IS NOT NULL
AND    operating_unit_id = :org_id
ORDER BY template_id, template_line_id;

To list all lines within a given template:

SELECT template_line_id, item_description, contract_price, supplier
FROM   apps.icx_por_req_templates
WHERE  template_id = :template_name
AND    source_type_code = 'TEMPLATE';

Because the view enforces org and language filters internally, queries should always constrain by OPERATING_UNIT_ID where results are displayed per operating unit, and should treat CONTRACT_LINE as NULL for non-contract template entries. Given the outer joins to supplier and site tables, consumers should expect NULL supplier attributes for template lines without a suggested vendor.