Results for “supplier_contact”

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

Overview

POR_VIEW_LINES_V is a reporting view owned by the APPS schema within the Oracle iProcurement (ICX) module. It presents the line-level detail of requisitions created and maintained through Oracle iProcurement and Oracle Purchasing, exposing a flattened, display-ready projection of requisition line data for the Oracle E-Business Suite 12.1.1 and 12.2.2 releases. The view is documented with the description "View Requisition Lines" in the ETRM metadata and carries a VALID status, indicating that it is a supported, compiled object within the APPS schema.

The view exists primarily to serve iProcurement and associated reporting requirements, where requisition lines must be presented alongside descriptive attributes that do not reside on the base transaction table itself. It resolves codes into meaningful values, formats dates according to user profile settings, and computes derived amounts and account strings through calls to the POR_VIEW_REQS_PKG package. Because it joins more than twenty base objects, it functions as a consolidated requisition-line reporting surface rather than a normalized transactional entity.

Underlying Base Objects

The view is defined over a broad set of synonyms, views, and packages. The central driving table is PO_REQUISITION_LINES (aliased PRL), with the header-level parent PO_REQUISITION_HEADERS also referenced. Supporting purchasing data is drawn from PO_LINE_LOCATIONS, PO_HEADERS, PO_RELEASES, PO_VENDORS, PO_VENDOR_SITES, and PO_LOOKUP_CODES. Order information for inventory-sourced lines is obtained through OE_ORDER_HEADERS, with the OE_ORDER_IMPORT_INTEROP_PUB package listed among referenced objects.

Inventory and item context is supplied by MTL_SYSTEM_ITEMS_KFV, MTL_CATEGORIES, and MTL_UNITS_OF_MEASURE_VL. Human resources and organizational data come from PER_ALL_PEOPLE_F, HR_LOCATIONS, and the HR_GENERAL package. Financial context is provided by GL_SETS_OF_BOOKS, FINANCIALS_SYSTEM_PARAMETERS, and PO_SYSTEM_PARAMETERS. Runtime formatting and derivation logic is delegated to the FND_PROFILE, FND_GLOBAL, and POR_VIEW_REQS_PKG packages, the latter being referenced repeatedly within the view text to resolve account numbers, line totals, project numbers, task names, and expenditure types.

Key Columns

• REQUISITION_LINE_ID and REQUISITION_HEADER_ID — the primary and foreign keys linking lines to their requisition headers.
• PARENT_REQ_LINE_ID — identifies the parent requisition line, enabling hierarchical and line-reference relationships; this is the column most commonly sought when tracing sourced or referenced lines.
• SEGMENT1 columns (MC and MSI) — expose the category and inventory item identifiers or numbers.
• ITEM_DESCRIPTION and LINE_NUM — describe the requested item and its sequence on the requisition.
• NEED_BY_DATE — formatted using the ICX_DATE_FORMAT_MASK profile value.
• SOURCE_TYPE_CODE — indicates whether the line originates from inventory or from an external/purchasing source; the view also derives a destination indicator from DESTINATION_TYPE_CODE.
• Order/Release reference — resolves to the order number for inventory lines or to the concatenated PO segment and release number for purchasing lines.
• QUANTITY, UNIT_PRICE, and derived line total — the line total is computed via POR_VIEW_REQS_PKG.GET_LINE_TOTAL against the set of books currency.
• Account, project, task, and expenditure type — resolved through POR_VIEW_REQS_PKG functions for display purposes.
• Vendor attributes — VENDOR_NAME, VENDOR_SITE_CODE, SUGGESTED_VENDOR_PRODUCT_CODE, and SUGGESTED_VENDOR_CONTACT.
• Delivery attributes — DESTINATION_SUBINVENTORY, deliver-to location code, and the requester full name resolved from PER_ALL_PEOPLE_F.

Common Use Cases and Queries

The view is typically queried to produce requisition line listings for iProcurement display, purchasing analysis, and downstream reporting. A common pattern is to retrieve all lines for a given requisition header, including parent line references:

• SELECT requisition_line_id, requisition_header_id, parent_req_line_id, line_num, item_description, quantity FROM por_view_lines_v WHERE requisition_header_id = :p_header_id ORDER BY line_num;

Analysts frequently isolate hierarchical relationships by filtering on the parent line reference:

• SELECT requisition_line_id, parent_req_line_id, line_num, source_type_code FROM por_view_lines_v WHERE parent_req_line_id IS NOT NULL;

Because the view pre-resolves account strings, project data, and formatted totals, it is also used as a source for requisition detail extracts and for reconciliation between requisition and order lines, particularly where the source type distinguishes inventory from purchasing activity.