Search Results sec_supplier_id

Overview

APPS.POS_ASN_SITE_LOV_V is a valid, internal Oracle E-Business Suite view owned by the APPS schema. It is registered in FND Design Data under the product short name ICX, indicating that its primary consumer is the iProcurement / Internet Procurement family of applications rather than the core Purchasing forms themselves. As the name implies, the object functions as a list-of-values (LOV) source, returning supplier and supplier site candidates that can be presented to a user during an Advance Shipment Notice (ASN) or related receiving workflow.

The view is flagged "Oracle Internal Use Only." Oracle Corporation does not support direct access to application data through this object except from standard Oracle Applications programs. Because it is a view rather than a table, it stores no data of its own; it is a read-only projection whose cost and behaviour are entirely determined by the underlying supplier and supplier site objects. Note also that the ETRM metadata records that POS_ASN_SITE_LOV_V is not referenced by any other database object, so its dependency footprint is one-directional.

Underlying Base Objects

Per the documented metadata, the view is defined over three referenced objects: the FND_GLOBAL package and the PO_VENDORS and PO_VENDOR_SITES views. PO_VENDORS supplies the supplier-level attributes (internal supplier identifier and supplier name), while PO_VENDOR_SITES supplies the site-level attributes (site identifier, site code, and the concatenated site address). FND_GLOBAL is almost certainly used to resolve session context — most commonly ORG_ID or a similar runtime identifier — so that the LOV is scoped to the operating unit or organization in which the calling form is executing.

The primary-key relationship is the expected one: PO_VENDOR_SITES rows are children of PO_VENDORS rows, joined on vendor_id. Consequently each row returned by POS_ASN_SITE_LOV_V represents a single supplier site belonging to a single supplier, with the supplier attributes denormalised onto every site row for LOV display purposes.

Key Columns

• SUPPLIER_ID (NUMBER) — The internal identifier of the supplier party, sourced from PO_VENDORS.
• SUPPLIER_NAME (VARCHAR2 240) — The display name of the supplier, used as the primary descriptive field in the LOV.
• SUPPLIER_SITE_ID (NUMBER) — The internal identifier of the supplier site, sourced from PO_VENDOR_SITES.
• SUPPLIER_SITE_CODE (VARCHAR2 15) — The short site code used operationally to distinguish sites of the same supplier.
• SUPPLIER_SITE_ADDRESS (VARCHAR2 947) — A concatenated, human-readable address string for the site.
• SEC_SUPPLIER_ID (NUMBER) — A secondary supplier identifier. This column is the one associated with the search term "sec_supplier_id" and typically carries the identifier of the supplier entity that holds the security or business relationship relevant to the current session, which can differ from SUPPLIER_ID in third-party or agent-style procurement relationships.
• SEC_SUPPLIER_SITE_ID (NUMBER) — The corresponding secondary site identifier, paired with SEC_SUPPLIER_ID to give the full secondary supplier/site context.

Common Use Cases and Queries

The view is normally invoked behind an LOV widget or via a form's record-group lookup; direct SQL is used for diagnostics, reconciliation, and reporting where the ASN supplier/site context must be reproduced. A basic projection follows the documented query text exactly:

• SELECT SUPPLIER_ID, SUPPLIER_NAME, SUPPLIER_SITE_ID, SUPPLIER_SITE_CODE, SUPPLIER_SITE_ADDRESS, SEC_SUPPLIER_ID, SEC_SUPPLIER_SITE_ID FROM APPS.POS_ASN_SITE_LOV_V;
• Filter by supplier name for LOV-style search: WHERE SUPPLIER_NAME LIKE 'ACME%'.
• Resolve a single site: WHERE SUPPLIER_SITE_ID = :site_id.
• Detect third-party or agent relationships where the primary and secondary identifiers diverge: WHERE SEC_SUPPLIER_ID IS NOT NULL AND SEC_SUPPLIER_ID <> SUPPLIER_ID.
• Join to receiving or ASN tables on SUPPLIER_SITE_ID to validate that a shipment header points at a site still present in the LOV.

Because the query text carries no explicit WHERE clause, row count and performance depend heavily on the row counts of PO_VENDORS and PO_VENDOR_SITES and on any predicates pushed into those views. Applications always query it with restricting predicates; unrestricted full scans should be avoided. As with all internal Oracle objects, use should be limited to supported programs or explicitly authorised diagnostics.