Search Results header_fob_lookup_code




Overview
Explore in AI Chat

Overview

APPS.PO_AUTOSOURCE_DOCUMENTS_V is a reporting and integration view in Oracle E-Business Suite (EBS) Advanced Supply Chain Planning / Purchasing, available in both 12.1.1 and 12.2.2. It consolidates sourcing information across approved supplier lists (ASL) and their associated purchasing documents — quotations, blanket purchase agreements, and contracts — into a single denormalized result set. The view's principal purpose is to expose, for a given ASL entry, the candidate source documents that may be auto-sourced when a requisition or purchase order is created. It joins the ASL header, the ASL document mapping, and the underlying purchasing document header, line, and shipment (line location) records, together with vendor, vendor site, buyer, currency, and terms attributes.

Because it presents sourcing candidates in a flattened, query-friendly form, it is frequently consumed by purchasing workflows, sourcing automation, and custom integrations (for example, outbound extract programs or BI Publisher report definitions) that need to enumerate valid source agreements without navigating the base ASL and PO tables separately.

Underlying Base Objects

The view is defined over a broad set of documented base objects. ASL-related sources include PO_ASL_ATTRIBUTES, PO_ASL_DOCUMENTS, and PO_APPROVED_SUPPLIER_LIS_VAL_V. Purchasing document sources include PO_AUTOSOURCE_DOCUMENTS_ALL, PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, and PO_LINE_TYPES. Supplier sources include AP_SUPPLIER_CONTACTS, PO_VENDORS, and PO_VENDOR_SITES_ALL. Organizational and setup sources include PO_GA_ORG_ASSIGNMENTS, GL_SETS_OF_BOOKS, HR_ALL_ORGANIZATION_UNITS_TL, MTL_PARAMETERS, FINANCIALS_SYSTEM_PARAMETERS, and PER_ALL_PEOPLE_F, with FND_GLOBAL used for session context resolution (such as the operating unit). These objects provide the keys, descriptive attributes, and organizational context necessary to reconstruct a complete sourcing row.

Key Columns

Common Use Cases and Queries

Typical scenarios include sourcing-eligibility reporting, ASL document validation, and extracts feeding external procurement or reconciliation processes. A canonical query selects active candidate documents for a supplier and organization:

SELECT asl_id, vendor_id, vendor_name, document_type_code,
       segment1, line_num, unit_price, currency_code
  FROM apps.po_autosource_documents_v
 WHERE vendor_id = :p_vendor_id
   AND org_id = :p_org_id;

Analysts also filter on DOCUMENT_TYPE_CODE to isolate blanket agreements from quotations, or join the result to PO_HEADERS_ALL to reconcile authorization status. Because the view is built on multi-org tables, queries should always constrain ORG_ID to the intended operating unit to avoid cross-organization leakage.