Results for “operating_unit”

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

Overview

POA_CM_SITE_LOV_V is a read-only database view in the Oracle E-Business Suite Purchasing (PO) module. It exposes a denormalized, list-of-values style result set of supplier site records, joining supplier site information to supplier master data and to the operating unit organization definition. The view is intended to support list-of-values (LOV) presentation and lightweight reporting where a consumer needs to resolve a vendor site identifier to its site code, its owning supplier, and the operating unit under which the site is defined.

The view text includes the WITH READ ONLY clause, confirming that it is defined purely for query access and cannot be used as the target of DML. Because it is a Purchasing-owned view, it is typically referenced by concurrent programs, form-based LOV definitions, and custom reports that need a compact supplier site lookup without navigating the full PO_VENDOR_SITES_ALL structure.

Underlying Base Objects

The view is defined over three documented base objects:

• PO_VENDORS VE — the supplier (vendor) master table, supplying the vendor name.
• PO_VENDOR_SITES_ALL VS — the supplier site table containing all sites across operating units, supplying the site identifier, site code, vendor identifier, and organization identifier.
• HR_ALL_ORGANIZATION_UNITS OP — the organization units table, used to resolve the operating unit name.

The join conditions are: VS.ORG_ID = OP.ORGANIZATION_ID and VS.VENDOR_ID = VE.VENDOR_ID. These links associate each supplier site to exactly one supplier and to the organization unit identified by its ORG_ID. The ETRM metadata notes that no referenced base objects are separately documented beyond the view text itself, and that the object is not implemented in the reference database.

Key Columns

• VENDOR_SITE_ID — Primary identifier of the supplier site row in PO_VENDOR_SITES_ALL; the unique key surfaced by this view.
• ORG_ID — Operating unit organization identifier under which the site is defined.
• VENDOR_SITE_CODE — The user-visible supplier site name/code.
• OPERATING_UNIT — Aliased from OP.NAME; the descriptive name of the operating unit corresponding to ORG_ID.
• VENDOR_ID — Identifier of the parent supplier in PO_VENDORS.
• VENDOR_NAME — The supplier name from PO_VENDORS.

Common Use Cases and Queries

Typical scenarios include populating an LOV for supplier site selection, generating supplier site listings by operating unit, and joining to purchasing documents where only VENDOR_SITE_ID is stored but the operating unit or supplier name is required for presentation.

List all sites for a given supplier:

SELECT vendor_site_id, vendor_site_code, operating_unit
FROM   poa_cm_site_lov_v
WHERE  vendor_id = :p_vendor_id
ORDER BY vendor_site_code;

Filter sites by operating unit name:

SELECT vendor_name, vendor_site_code
FROM   poa_cm_site_lov_v
WHERE  operating_unit = :p_operating_unit;

Join to purchase orders to display the operating unit and supplier name:

SELECT poh.segment1, s.vendor_name, s.vendor_site_code, s.operating_unit
FROM   po_headers_all poh,
       poa_cm_site_lov_v s
WHERE  poh.vendor_site_id = s.vendor_site_id
AND    poh.org_id = s.org_id;

Because the view is read-only and resolves through HR_ALL_ORGANIZATION_UNITS, results reflect only sites whose ORG_ID has a matching organization unit record. Queries should therefore account for any data where the operating unit definition is absent.