Results for “source_organization”

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

Overview

PO_REQUISITION_LINES_INQ_V is an APPS-owned database view in the Oracle E-Business Suite Purchasing (PO) module, documented as retrofitted for both release 12.1.1 and 12.2.2. As its name implies, it is an inquiry-oriented view whose purpose is to present purchase requisition line information in a denormalized, read-friendly form that joins the requisition header, requisition line, line type, unit of measure, hazard class, UN number, and destination/source organization and location details. In Oracle EBS reporting and integration contexts, this view serves as a stable read interface for requisition line data, allowing reports, concurrent programs, and external integrations to retrieve requisition particulars without navigating the full normalized table structure directly. Because it is a view rather than a table, it exposes no independent storage and inherits the security, indexing, and referential characteristics of its underlying base objects. The view’s status is VALID, indicating that its defining query parses successfully against the referenced objects in the documented environment.

Underlying Base Objects

The documented base objects behind PO_REQUISITION_LINES_INQ_V span purchasing, inventory, human resources, work in process, general ledger, and bills of material schemas, all resolved as APPS synonyms or views. Principal among them are PO_REQUISITION_HEADERS_ALL and PO_REQUISITION_LINES, which supply the header and line facts. Supporting lookups include PO_LINE_TYPES_B and PO_LINE_TYPES_TL for line type code and translated description, PO_DOCUMENT_TYPES_ALL_B and PO_DOCUMENT_TYPES_ALL_TL for document type attributes, MTL_UNITS_OF_MEASURE for unit of measure, PO_HAZARD_CLASSES_TL and PO_UN_NUMBERS_TL for hazardous material classification, and PO_LOCATION_ASSOCIATIONS_ALL for location relationships. Organization and location names are drawn from HR_ALL_ORGANIZATION_UNITS_TL and HR_LOCATIONS_ALL_TL. Item context comes from MTL_SYSTEM_ITEMS, WIP_ENTITIES and WIP_LINES provide work-in-process associations, BOM_RESOURCES supplies resource references, and FINANCIALS_SYSTEM_PARAMS_ALL, GL_SETS_OF_BOOKS and GL_DAILY_CONVERSION_TYPES support currency and set-of-books defaults. The view also references PO_LINE_LOCATIONS_ALL for line location data. This breadth means the view can only return rows where the underlying joins succeed.

Key Columns

The view exposes identifiers such as REQUISITION_HEADER_ID, REQUISITION_LINE_ID, LINE_NUM, ITEM_ID, CATEGORY_ID and DELIVER_TO_LOCATION_ID that anchor each line to its header, item, category and destination. Descriptive fields include ITEM_DESCRIPTION, LINE_TYPE and LINE_TYPE_ID, REFERENCE_NUM, JUSTIFICATION, NOTE_TO_AGENT and NOTE_TO_RECEIVER. Quantity and pricing columns cover QUANTITY, UNIT_PRICE, UNIT_MEAS_LOOKUP_CODE, and receipt-progress measures QUANTITY_RECEIVED, QUANTITY_DELIVERED and QUANTITY_CANCELLED, each wrapped in a DECODE that returns NULL for RATE and FIXED PRICE order types. Currency columns include CURRENCY_CODE (defaulting through NVL from the set of books), RATE, RATE_TYPE and RATE_DATE. Status and control flags include CANCEL_FLAG, URGENT_FLAG, ENCUMBERED_FLAG, RFQ_REQUIRED_FLAG, ON_RFQ_FLAG, MODIFIED_BY_AGENT_FLAG and the outside operation flag defaulted to 'N'. Destination and source context are provided through DESTINATION_TYPE_CODE, SOURCE_TYPE_CODE, DESTINATION_SUBINVENTORY, SOURCE_SUBINVENTORY and related organization and location names. Suggested vendor details include SUGGESTED_VENDOR_NAME, LOCATION, CONTACT and PHONE. Fifteen ATTRIBUTE columns plus ATTRIBUTE_CATEGORY expose descriptive flexfield data, and LAST_UPDATE_DATE, CREATED_BY and companion audit columns support change tracking.

Common Use Cases and Queries

Typical scenarios include requisition status reporting, buyer workload analysis, encumbrance review, and interfaces that export requisition lines to external procurement systems. The view is also useful for validating suggested vendor data and item sourcing information before requisition approval.

• Listing open requisition lines for a buyer: SELECT requisition_header_id, line_num, item_description, quantity, unit_price FROM po_requisition_lines_inq_v WHERE cancel_flag = 'N' ORDER BY requisition_header_id, line_num;
• Auditing encumbered lines: SELECT requisition_line_id, reference_num, encumbered_flag, currency_code FROM po_requisition_lines_inq_v WHERE encumbered_flag = 'Y';
• Reviewing lines with suggested vendors: SELECT line_num, suggested_vendor_name, suggested_vendor_location FROM po_requisition_lines_inq_v WHERE suggested_vendor_name IS NOT NULL;

Because the view joins many base objects, queries should filter selectively and apply the appropriate operating unit and security predicates expected in the reported environment.