Search Results hr_org_units_no_join




Overview
Explore in AI Chat

Overview

PO_APPROVED_SUPPLIER_LIST_V is a purchasing-module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the Approved Supplier List (ASL) — the master record that authorizes a specific supplier, supplier site, or manufacturer to supply a given item or commodity to a given inventory organization. Where the base table PO_APPROVED_SUPPLIER_LIST stores the ASL header, this view flattens the header together with its sourcing attributes, status, item and category descriptors, supplier names, and organization names into a single denormalized row. That makes it the conventional access point for sourcing reports, supplier qualification inquiries, and inbound integration extracts that need a human-readable ASL rather than a set of foreign keys. The ETRM record lists the object status as VALID and notes it as "Retrofitted," indicating it was regenerated during the 12.2 upgrade cycle while retaining 11i semantics.

Underlying Base Objects

The view is defined over a large join graph. The driving objects are PO_APPROVED_SUPPLIER_LIST (synonym for the header) and PO_ASL_ATTRIBUTES, which carries sourcing behavior such as document sourcing method, release generation method, scheduling flags, bucket patterns, tolerances, and lead times. Supporting objects include PO_ASL_STATUSES for the status description, PO_LOOKUP_CODES (referenced five times) to resolve displayed values for sourcing and scheduling code columns, PO_VENDORS and PO_VENDOR_SITES, MTL_MANUFACTURERS for manufacturer rows, MTL_SYSTEM_ITEMS_KFV and MTL_CATEGORIES_KFV for item concatenated segments and category description, and CHV_BUCKET_PATTERNS for bucket pattern names. Organization names come from HR_ORG_UNITS_NO_JOIN and HR_ALL_ORGANIZATION_UNITS_TL, with MTL_PARAMETERS supplying the operating unit context. Person names are resolved through PER_PEOPLE_F, and HR_PERSON_NAME, HR_GENERAL, HR_SECURITY, FND_GLOBAL, PO_MOAC_UTILS_PVT, and WF_CORE provide the security and utility calls used in the WHERE clause. Notably, the view depends on HR_ORG_UNITS_NO_JOIN — the union of HR_ALL_ORGANIZATION_UNITS and HR_ALL_ORGANIZATION_UNITS_TL that avoids the name-translation join — which is why queries against this view can surface both organization codes and translated organization names.

Key Columns

Common Use Cases and Queries

Typical uses include validating sourcing setup before running MRP or auto-sourcing, auditing ASL records approaching their review date, and extracting approved supplier data for supplier-portal or third-party procurement systems.

  • List active suppliers for an item in a given organization.
  • Report ASLs due for review within the next thirty days.
  • Extract global (using_organization_id = -1) approved suppliers.
SELECT asl_id, vendor_name, item_id, concatenated_segments,
       organization_code, status
FROM   apps.po_approved_supplier_list_v
WHERE  item_id = :item_id
AND    using_organization_id IN (:org_id, -1)
AND    disable_flag = 'N';

SELECT asl_id, vendor_name, review_by_date
FROM   apps.po_approved_supplier_list_v
WHERE  review_by_date BETWEEN SYSDATE AND SYSDATE + 30
ORDER  BY review_by_date;

Because organization and person name resolution passes through HR security packages, results are filtered by the querying user's HR organization security profile; responsibility and MOAC operating unit context must be set correctly to avoid suppressed rows.