Results for “pay_site_flag”

50+ results




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

Overview

OKL_VENDOR_SITES_UV is a user interface (UI) view owned by the APPS schema within the OKL – Leasing and Finance Management product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It is documented as a "user interface view for vendor sites" and exposes vendor site records in a shape tailored for Oracle Forms-based and HTML-based leasing screens rather than for general-purpose reporting. The view keys each row on VENDOR_SITE_ID (aliased to ID1) and carries a literal '#' placeholder in ID2, following the EBS convention of exposing dummy or composite primary-key segments required by the framework's ID1/ID2 pattern.

Because the view is built directly over PO_VENDOR_SITES, it surfaces the same supplier-site population used by Procurement, but adds derived attributes oriented toward leasing activity: an active/inactive STATUS flag, computed START_DATE_ACTIVE and END_DATE_ACTIVE values, a formatted address DESCRIPTION, and party-related identifiers. In 12.2.2 the same definition is retained, and the referenced base objects remain PO_VENDOR_SITES, the ARP_ADDR_LABEL_PKG address-formatting package, and FND_GLOBAL for session context.

Underlying Base Objects

  • PO_VENDOR_SITES (VIEW) — the sole data source, providing vendor_site_id, vendor_id, vendor_site_code, org_id, address lines, inactive_date, and pay_site_flag.
  • ARP_ADDR_LABEL_PKG (PACKAGE) — invoked via ARP_ADDR_LABEL_PKG.FORMAT_ADDRESS(...) to render a single-line address string, truncated to 80 characters with SUBSTR, for the DESCRIPTION column.
  • FND_GLOBAL (PACKAGE) — referenced by the view definition for runtime session values such as SYSDATE-based derivations and organizational context. In practice the date logic relies on SYSDATE and NVL against INACTIVE_DATE.

No OKL-specific base table or synonym is documented in the extracted view text; the relationship is therefore a thin projection and transformation layer over the shared supplier-site definition, reframing Procurement columns for leasing UI requirements.

Key Columns

  • ID1 / ID2 — ID1 is VENDOR_SITE_ID; ID2 is the literal '#' placeholder used by the EBS ID1/ID2 UI key convention.
  • VENDOR_ID — identifying supplier; also exposed again as PARTY_ID.
  • NAME — derived from VENDOR_SITE_CODE.
  • ORG_ID — the operating unit that owns the site, exposed for multi-org filtering.
  • STATUS — DECODE over SIGN(NVL(INACTIVE_DATE, SYSDATE) - SYSDATE): 'I' when inactive, otherwise 'A'.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — END_DATE_ACTIVE is INACTIVE_DATE minus one day; START_DATE_ACTIVE uses nested DECODE logic to normalize the effective start of the active window.
  • DESCRIPTION — the formatted, 80-character address produced by ARP_ADDR_LABEL_PKG.
  • PAY_SITE_FLAG — indicates whether the site is a payment site.
  • PARTY_ID / PARTY_ID2 — PARTY_ID maps to VENDOR_ID, while the user's searched term, PARTY_ID2, is defined in the view as the literal '#' placeholder. It is a framework-required convention for the second key segment, not a true TCA party identifier.

Common Use Cases and Queries

Leasing agents select this view when a vendor site is required as a lease counterparty, payment site, or asset-return location. Standard usage filters by operating unit and active status.

SELECT id1, vendor_id, name, org_id, description, pay_site_flag
FROM   apps.okl_vendor_sites_uv
WHERE  status = 'A'
AND    org_id = :org_id
ORDER BY name;

When a screen supplies the ID1/ID2 composite key, callers retrieve a specific site:

SELECT id1, id2, name, status, party_id, party_id2
FROM   apps.okl_vendor_sites_uv
WHERE  id1 = :vendor_site_id
AND    id2 = '#';

Because PARTY_ID2 resolves to '#', queries that treat it as a real party join key will fail; the correct linkage is party_id = vendor_id. Integration use of this view is therefore limited: it is intended for UI population, address display, and status checking, while true TCA party relationships should be resolved through the underlying supplier and party model rather than this projection.