Search Results source_organization_name




Overview
Explore in AI Chat

Overview

The APPS.PO_REQEXPRESS_LINES_V view is a Purchasing (PO) module reporting object in Oracle E-Business Suite 12.1.1 and 12.2.2. It denormalizes the PO_REQEXPRESS_LINES base table by joining it to line type, lookup, organization, vendor, vendor site, and vendor contact information, producing a single row per requisition express line enriched with descriptive attributes. The view is marked VALID and is maintained by Oracle as a "retrofitted" object, meaning it was carried into the current release while retaining its original column interface for backward compatibility with existing forms, reports, and integrations.

Because the view exposes both the raw foreign-key columns and their resolved descriptive values, it is well suited to reporting and integration scenarios where a self-service or iProcurement-style requisition express template must be rendered without additional lookups at the application tier.

Underlying Base Objects

The FROM clause lists seven objects: PO_REQEXPRESS_LINES (synonym to the base table), PO_LINE_TYPES (synonym), PO_LOOKUP_CODES (view), ORG_ORGANIZATION_DEFINITIONS (view), PO_VENDORS (view), PO_VENDOR_SITES_ALL (view), and PO_VENDOR_CONTACTS (view). It also calls PO_INQ_SV.GET_PERSON_NAME and is documented as referencing FND_GLOBAL, HR_GENERAL, and HR_SECURITY packages, which support security and person-name resolution. The joins to PO_VENDORS, PO_VENDOR_SITES_ALL, and PO_VENDOR_CONTACTS are outer joins (identified by the (+) operator), so a requisition express line is returned even when no suggested vendor, site, or contact is recorded. PO_LINE_TYPES and PO_LOOKUP_CODES are inner-joined on LINE_TYPE_ID and on the 'REQUISITION SOURCE TYPE' lookup, and ORG_ORGANIZATION_DEFINITIONS is outer-joined on SOURCE_ORGANIZATION_ID.

Key Columns

Common Use Cases and Queries

Typical usage includes validating express-line vendor/contact assignments, exporting template lines for interface processing, and building report queries that need the contact name without a secondary join.

SELECT EXPRESS_NAME, SEQUENCE_NUM, ITEM_DESCRIPTION,
       VENDOR_NAME, VENDOR_SITE_CODE,
       SUGGESTED_VENDOR_CONTACT_ID
FROM   APPS.PO_REQEXPRESS_LINES_V
WHERE  EXPRESS_NAME = :p_express_name
ORDER  BY SEQUENCE_NUM;

SELECT EXPRESS_NAME, SUGGESTED_VENDOR_CONTACT_ID,
       VENDOR_NAME, VENDOR_SITE_CODE
FROM   APPS.PO_REQEXPRESS_LINES_V
WHERE  SUGGESTED_VENDOR_ID = :p_vendor_id
AND    ORG_ID = :p_org_id;

The second query illustrates filtering on the resolved vendor while still surfacing the contact ID, a pattern commonly used when auditing which express templates reference a given supplier contact.