Results for “org_code”

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

Overview

APPS.POR_LINES_V is a requisition line view owned by the APPS schema and shipped with the Oracle iProcurement (ICX) product family. It exposes purchase requisition line detail in a denormalized, display-ready form, resolving foreign keys into concatenated key flexfield segments, person names, lookup meanings, and organization codes. Its primary consumers are the iProcurement and Oracle Purchasing user interfaces and the concurrent reporting layer that renders requisition information, rather than a transactional destination. Because the view joins PO_REQUISITION_LINES to a substantial set of reference objects, it allows callers to retrieve a complete requisition line picture with a single query, avoiding repeated lookups against MTL_SYSTEM_ITEMS_KFV, HR_LOCATIONS, PER_PEOPLE_F, and the PO lookup views. The status in EBS 12.1.1 and 12.2.2 is VALID, and the view is referenced extensively by the requisition display and search pages delivered in the iProcurement module.

Underlying Base Objects

The view is defined over PO_REQUISITION_LINES (synonym PRL) as its driving table, joined to PO_REQUISITION_HEADERS and to a series of supporting objects. Documented base objects include: PO_LINE_TYPES, PO_HEADERS, PO_HAZARD_CLASSES, PO_VENDOR_SITES (view), PO_LOOKUP_CODES (view), FND_LOOKUPS (view), MTL_SYSTEM_ITEMS_KFV and MTL_CATEGORIES_KFV (synonyms), ORG_ORGANIZATION_DEFINITIONS, PER_PEOPLE_F, HR_LOCATIONS, OE_ORDER_HEADERS, and the packages FND_GLOBAL, HR_GENERAL, HR_PERSON_NAME, HR_SECURITY, and POR_VIEW_REQS_PKG. The package POR_VIEW_REQS_PKG supplies derived values such as the shipment number via GET_SHIPMENT_NUMBER. The Key Flexfield views supply CONCATENATED_SEGMENTS for item numbers and categories, while PO_LOOKUP_CODES resolves destination and source type codes into displayed field values.

Key Columns

The view exposes identifying keys such as REQUISITION_HEADER_ID, REQUISITION_LINE_ID, LINE_NUM, and ORG_ID. Descriptive columns include ITEM_DESCRIPTION, ITEM_NUMBER (from MTL_SYSTEM_ITEMS_KFV.CONCATENATED_SEGMENTS), CATEGORY, MANUFACTURER_NAME, and MANUFACTURER_PART_NUMBER. Quantities and amounts appear as QUANTITY, QUANTITY_DELIVERED, QUANTITY_RECEIVED, QUANTITY_CANCELLED, CURRENCY_CODE, and CURRENCY_UNIT_PRICE. Of particular interest to the searched term, the column MUST_USE_SUGG_VENDOR_FLAG is projected directly from PO_REQUISITION_LINES and indicates whether the requester is obligated to use the suggested vendor carried on the line. Delivery attributes include DELIVER_TO_LOCATION, DELIVER_TO_ORG_CODE, DESTINATION_SUBINVENTORY, and DESTINATION_TYPE. Requisition ownership and routing are represented by DELIVER_TO_REQUESTER, REQUESTER_EMAIL, SUGGESTED_BUYER, NOTE_TO_VENDOR, NOTE_TO_RECEIVER, and NEED_BY_DATE.

Common Use Cases and Queries

The view is commonly queried for requisition line reporting, iProcurement search, and integration extracts that require a denormalized line record. A representative query retrieving lines with their suggested-vendor constraint might read:

• SELECT REQUISITION_HEADER_ID, REQUISITION_LINE_ID, LINE_NUM, ITEM_DESCRIPTION, ITEM_NUMBER, QUANTITY, CURRENCY_UNIT_PRICE, MUST_USE_SUGG_VENDOR_FLAG, SUGGESTED_BUYER, DELIVER_TO_LOCATION, NEED_BY_DATE FROM APPS.POR_LINES_V WHERE ORG_ID = :p_org_id AND REQUISITION_HEADER_ID = :p_header_id ORDER BY LINE_NUM;
• Filtering open requirements: adding WHERE QUANTITY > (QUANTITY_RECEIVED + QUANTITY_CANCELLED) to isolate lines still awaiting receipt or cancellation.
• Vendor-constraint auditing: selecting MUST_USE_SUGG_VENDOR_FLAG alongside MANUFACTURER_NAME, MANUFACTURER_PART_NUMBER, and DOCUMENT_NUM to review which blanket or negotiated sources were enforced.
• Buyer workload reporting: aggregating on SUGGESTED_BUYER and ORG_CODE to measure requisition volumes per purchasing group.

Because the view resolves security through HR_SECURITY and organization context through FND_GLOBAL, queries executed outside a properly initialized session should set the organization context explicitly. The view text continues beyond the excerpt shown, projecting additional lookup and document type columns, so consumers should treat the column list as representative rather than exhaustive.