Search Results using_organization_code




Overview
Explore in AI Chat

Overview

POFV_ASL_DOCUMENTS is a read-only view owned by the APPS schema in Oracle E-Business Suite Purchasing (PO). It presents the association between an Approved Supplier List (ASL) entry and the purchasing documents — blanket purchase agreements, contracts, or standard purchase orders — that were approved to authorize that supplier entry. The view is implemented with a WITH READ ONLY clause, confirming that it is intended strictly for query and reporting purposes rather than for data maintenance. In release 12.2.2 the object is described as "Retrofitted," indicating that it was adapted to align with the multi-org and MOAC (Multi-Org Access Control) architecture introduced in Release 12.

The view is the principal reporting surface used by ASL-related inquiries and OAF-based pages that display document references on the Approved Supplier List form. By combining supplier list header information with header and line details from PO_HEADERS_ALL and PO_LINES_ALL, and resolving organization and operating unit names, it allows a consumer to answer the question: "for which ASL entry, and in which operating unit, is this purchasing document referenced?" The presence of the DOCUMENT_LINE_NUMBER column directly supports searches such as document_line_number, letting users trace the specific line of an agreement or order tied to a supplier list entry.

Underlying Base Objects

The view is defined over six documented base objects, all accessed through APPS synonyms: PO_ASL_DOCUMENTS (the driving table), PO_APPROVED_SUPPLIER_LIST, HR_ALL_ORGANIZATION_UNITS (used twice — once for the using organization, once for the operating unit), MTL_PARAMETERS, PO_HEADERS_ALL, and PO_LINES_ALL.

  • PO_ASL_DOCUMENTS (AD) — the central table linking an ASL attribute entry to a purchasing document header and line.
  • PO_APPROVED_SUPPLIER_LIST (AL) — joined on ASL_ID and USING_ORGANIZATION_ID to qualify the ASL entry.
  • MTL_PARAMETERS (UC) — outer-joined on USING_ORGANIZATION_ID to supply the inventory organization code.
  • HR_ALL_ORGANIZATION_UNITS (UO / OP) — outer-joined to resolve the using organization name and the operating unit name respectively.
  • PO_HEADERS_ALL (PH) — inner-joined on DOCUMENT_HEADER_ID, contributing the document number (SEGMENT1) and ORG_ID.
  • PO_LINES_ALL (PL) — inner-joined on DOCUMENT_LINE_ID, contributing the line number.

The inner joins to PO_HEADERS_ALL and PO_LINES_ALL mean that only ASL document references that resolve to a valid header and line appear in the result set.

Key Columns

Common Use Cases and Queries

Typical uses include auditing which agreements support a given supplier list entry, reconciling ASL documentation against open purchasing documents, and reporting document coverage by operating unit. The following sample retrieves document header and line detail for a specific ASL entry:

SELECT document_number, document_line_number, operating_unit_name
FROM apps.pofv_asl_documents
WHERE approved_supplier_list_id = :asl_id
ORDER BY sequence_number, document_line_number;

To locate every ASL reference for a particular purchasing document line, filter on the line number:

SELECT approved_supplier_list_id, using_organization_code, document_number
FROM apps.pofv_asl_documents
WHERE document_line_number = :line_num
AND document_number = :doc_num;

Because the view enforces '_SEC:AD.ORG_ID' IS NOT NULL, results are automatically filtered by the MOAC security profile of the querying responsibility, so users see only documents within their authorized operating units. All access should be performed through the APPS schema, and no DML should ever be issued against this read-only view.