Results for “begin_date”

2 results




Overview
Explore in AI Chat

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

Overview

ASO_PVT_PARTY_SITE_USES_V is a security-constrained view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the ASO product family — Order Capture — and exposes party site use records sourced from Oracle Trading Community Architecture (TCA). The view acts as a filtered access layer over HZ_PARTY_SITE_USES, returning only those site use rows whose STATUS column resolves to 'A' (active) under the predicate NVL(STATUS, 'A') = 'A'. The NVL expression means that rows with a NULL STATUS are also treated as active, which preserves backward compatibility with legacy data where status was never populated.

Within Oracle EBS reporting and integration, this view is typically consumed by order capture and order management logic that needs a stable list of active party site uses for a given party site. Because the definition is short and deterministic, the view is inexpensive to query and is commonly joined to HZ_PARTY_SITES, HZ_LOCATIONS, and HZ_PARTIES to build customer-site lookups used in order entry, shipping, and billing validation. The BEGIN_DATE and END_DATE columns are of particular interest to reporting users, because they provide the effective dating window that governs when a site use is considered valid.

Underlying Base Objects

The view is defined over a single documented base object: HZ_PARTY_SITE_USES, referenced through the APPS.HZ_PARTY_SITE_USES synonym. The view text is:

HZ_PARTY_SITE_USES is the TCA table that records the role a particular party site plays — for example, bill-to, ship-to, or statement-to. Because the view references the synonym, it inherits the standard APPS-level access grants and can be queried without the caller needing direct privileges on the TCA table. No joins or aggregations are applied, so the view is a straightforward projection with a status predicate.

Key Columns

  • PARTY_SITE_USE_ID — Primary identifier of the site use record; unique per party site use.
  • PARTY_SITE_ID — Foreign key to the parent party site, used to join to HZ_PARTY_SITES.
  • SITE_USE_TYPE — Classifies the purpose of the site use, such as bill-to or ship-to.
  • PRIMARY_PER_TYPE — Flag indicating whether this use is the primary use for its SITE_USE_TYPE for the party.
  • BEGIN_DATE — Effective start date of the site use; the lower bound of the validity window.
  • END_DATE — Effective end date of the site use; the upper bound of the validity window.

The BEGIN_DATE column is the field most frequently used to determine whether a site use should be considered current at a given point in time. A record is typically valid when the reporting date falls between BEGIN_DATE and END_DATE.

Common Use Cases and Queries

Typical use cases include listing active ship-to or bill-to sites for a customer, validating a site use as of a specific date, and driving order entry defaults. The following query returns all active site uses for a party site:

  • SELECT party_site_use_id, party_site_id, site_use_type, primary_per_type, begin_date, end_date FROM aso_pvt_party_site_uses_v WHERE party_site_id = :p_party_site_id;
  • SELECT party_site_use_id, site_use_type, begin_date, end_date FROM aso_pvt_party_site_uses_v WHERE site_use_type = 'SHIP_TO' AND TRUNC(SYSDATE) BETWEEN begin_date AND NVL(end_date, TRUNC(SYSDATE) + 1);

Because the view filters on status, callers do not need to add their own STATUS predicate, but they should still apply date filtering using BEGIN_DATE and END_DATE where effective dating matters. All access is read-only; no DML is supported against this view definition.