Search Results party_site_use_code

Overview

AST_LOCATION_SITE_USE_V is a reporting view owned by the APPS schema within the AST (TeleSales) product family of Oracle E-Business Suite. It exposes party site use records — the assignments of a specific purpose or business function to a party site — in a form that is convenient for TeleSales and related modules to query. In Oracle EBS 12.1.1 and 12.2.2, party site uses are stored in the trading community (HZ) model and are central to determining how a location is used, for example as a bill-to, ship-to, or other location role. The view presents these records alongside the lookup meaning that describes each site use type, giving consumers a human-readable label without requiring a separate join.

The view is a lightweight, read-oriented projection. It contains no business logic of its own beyond a status filter and an outer join to the lookup table, and it is not a table, so it carries no data of its own. Its role is to provide a stable, denormalized interface for reports, concurrent programs, and integration points that need to interpret a party site's role.

Underlying Base Objects

The view text is defined over two referenced objects:

• HZ_PARTY_SITE_USES (documented as a SYNONYM in the ETRM metadata, aliased USE in the view definition) — the primary source of party site use rows.
• AR_LOOKUPS (a VIEW, aliased LKUP) — joined via an outer join on USE.SITE_USE_TYPE = LKUP.LOOKUP_CODE, restricted to LKUP.LOOKUP_TYPE = 'PARTY_SITE_USE_CODE'.

The join to AR_LOOKUPS is an outer join ((+) syntax), so rows in HZ_PARTY_SITE_USES are retained even when no matching lookup meaning exists. The WHERE clause further restricts output to records whose STATUS is either 'A' (active) or 'I' (inactive), excluding other lifecycle states. This means the view surfaces both active and inactive site uses, and consumers must apply their own status filter when only active records are required.

Key Columns

• ROW_ID — the ROWID of the underlying HZ_PARTY_SITE_USES row.
• PARTY_SITE_USE_ID — the unique identifier of the party site use record.
• PARTY_SITE_ID — the party site to which the use applies.
• SITE_USE_TYPE — the coded type of the site use, matching a lookup code of lookup type PARTY_SITE_USE_CODE.
• SITE_USE_MEANING — the translated meaning of the site use type, sourced from AR_LOOKUPS.MEANING via the outer join.
• PRIMARY_PER_TYPE — indicates whether this use is the primary use for its type at the party site.
• STATUS — the record status, restricted to 'A' or 'I' by the view.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE, plus OBJECT_VERSION_NUMBER for optimistic locking and APPLICATION_ID and CREATED_BY_MODULE for ownership and module attribution.

Common Use Cases and Queries

Typical uses include resolving a party site's role for order entry and customer-facing processes, reporting on site use distributions by type, and integration extracts that need readable labels for site use codes. A common filter is on the lookup meaning, which is how many users search for a given site use code.

The following query returns active site uses for a given party site, showing both the coded type and its meaning:

• SELECT party_site_use_id, party_site_id, site_use_type, site_use_meaning, primary_per_type FROM apps.ast_location_site_use_v WHERE party_site_id = :p_party_site_id AND status = 'A';

To find sites using a particular site use code, query by type or by the resolved meaning:

• SELECT party_site_id, site_use_type, site_use_meaning FROM apps.ast_location_site_use_v WHERE site_use_type = 'BILL_TO' AND status = 'A';
• SELECT party_site_id, site_use_type, site_use_meaning FROM apps.ast_location_site_use_v WHERE site_use_meaning = 'Ship-To' AND status = 'A';

Because the view already joins to AR_LOOKUPS, queries that need the descriptive meaning of PARTY_SITE_USE_CODE values can avoid repeating that join, which simplifies reporting SQL and keeps the site use type consistent with the standard lookup definitions.