Search Results source_doc_line_id

Overview

PO_REQUISITION_TEMPLATES_V is a Purchasing (PO) module view owned by the APPS schema and marked VALID in Oracle E-Business Suite 12.1.1 and 12.2.2. Its description is recorded as "Retrofitted," indicating it was carried forward to preserve backward compatibility for customizations, reports, or integrations that predate the current requisition template architecture. The view presents pre-defined requisition templates stored in the requisition express infrastructure — the header and line records that Procurement uses to generate requisition templates or "express" requisition setups. Each row joins an express header (template header) to one of its express lines, along with the corresponding documented purchasing header, line, item, vendor, currency, and organization attributes. It therefore serves as a denormalized, read-only reporting surface for template content rather than as a transactional interface.

Underlying Base Objects

The view text is built on two primary tables — PO_REQEXPRESS_HEADERS (aliased PRH) and PO_REQEXPRESS_LINES_ALL (aliased PRL) — combined with a broad set of supporting objects. The documented base objects for 12.2.2 include:

• Requisition express: PO_REQEXPRESS_HEADERS, PO_REQEXPRESS_LINES_ALL.
• Purchasing documents: PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_TYPES, PO_DOCUMENT_TYPES_ALL_B, PO_DOCUMENT_TYPES_ALL_TL, PO_LOOKUP_CODES.
• Supplier data: PO_VENDORS, PO_VENDOR_SITES_ALL, PO_VENDOR_CONTACTS.
• Currency and ledger: GL_DAILY_CONVERSION_TYPES, GL_SETS_OF_BOOKS, FINANCIALS_SYSTEM_PARAMS_ALL.
• Costing and inventory: CST_ITEM_COSTS, MTL_PARAMETERS.
• Human resources and security: HR_ORG_UNITS_NO_JOIN, HR_ALL_ORGANIZATION_UNITS_TL, PER_ALL_PEOPLE_F, plus the FND_GLOBAL, HR_GENERAL, and HR_SECURITY packages used for organization and security context.

The express line drives the join to PO_LINES_ALL via PO_LINE_ID and to PO_HEADERS_ALL via PO_HEADER_ID, while lookup and type tables resolve codes into descriptive names.

Key Columns

Because the user searched for source_doc_line_id, it is important to note that this identifier is not among the columns enumerated in the documented view text; source-related attributes are instead represented through SOURCE_TYPE_CODE, SOURCE_ORGANIZATION_ID, SOURCE_SUBINVENTORY, and the suggested-vendor fields.

• Template identity: EXPRESS_NAME, PRH.TYPE_LOOKUP_CODE, PDTL.TYPE_NAME, DESCRIPTION, SEQUENCE_NUM.
• Document links: PO_HEADER_ID, PO_LINE_ID, PH.SEGMENT1, PL.LINE_NUM.
• Pricing and currency: CURRENCY_CODE, RATE, RATE_TYPE, USER_CONVERSION_TYPE, RATE_DATE, UNIT_PRICE, the rounded unit price expression, AMOUNT.
• Sourcing: SOURCE_TYPE_CODE, ITEM_ID, ITEM_DESCRIPTION, CATEGORY_ID, UNIT_MEAS_LOOKUP_CODE, SUGGESTED_VENDOR_ID, VENDOR_NAME, VENDOR_SITE_CODE, SUGGESTED_VENDOR_CONTACT_ID, and the combined contact name.
• Buyer and organization: SUGGESTED_BUYER_ID, FULL_NAME, ORGANIZATION_CODE, ORG_ID.
• Controls: RFQ_REQUIRED_FLAG, NEGOTIATED_BY_PREPARER_FLAG, MATCHING_BASIS, PURCHASE_BASIS, DISPLAYED_FIELD.

Several columns use DECODE expressions to return inventory-derived or vendor-derived values depending on SOURCE_TYPE_CODE.

Common Use Cases and Queries

Typical uses include auditing template contents, validating defaulting logic, and feeding downstream requisition automation. To retrieve all lines for a named template:

• SELECT express_name, sequence_num, item_description, unit_price, source_type_code FROM po_requisition_templates_v WHERE express_name = :template ORDER BY sequence_num;
• SELECT express_name, segment1, vendor_name, organization_code, amount FROM po_requisition_templates_v WHERE org_id = :org_id;
• SELECT express_name, item_id, suggested_vendor_site_id, rfq_required_flag FROM po_requisition_templates_v WHERE negotiated_by_preparer_flag = 'Y';

Security context is applied through HR organization and FND_GLOBAL values, so results reflect the operating unit of the session. (Note: 12.1.1 and 12.2.2 may differ in some join specifics; the metadata above reflects the documented 12.2.2 definition.)