Results for “clli_code”

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

Overview

The view APPS.CSC_HZ_PARTY_SITES_V is a Customer Care (CSC) module database object that presents a consolidated, denormalized representation of party site information. It joins records from the Oracle Trading Community Architecture (TCA) foundation tables HZ_PARTY_SITES, HZ_LOCATIONS, and HZ_PARTIES to associate a party with its physical address locations. Within the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, this view serves as a reporting and integration convenience layer, sparing developers and analysts from repeatedly writing the multi-table joins required to resolve a party site to its constituent location attributes.

Because it aggregates party identity, site role, and address detail into a single queryable object, the view is commonly referenced in customer-facing inquiries, data extracts, and interface programs where a flat rendering of site and address information is required. It is owned by the APPS schema and carries a VALID status, indicating that it compiles successfully against the underlying TCA objects.

Underlying Base Objects

Per the documented ETRM metadata for release 12.2.2, the view is defined over the following referenced base objects:

• HZ_PARTIES (SYNONYM) — supplies party identity columns such as PARTY_ID, PARTY_NUMBER, PARTY_NAME, and PARTY_TYPE.
• HZ_PARTY_SITES (SYNONYM) — provides the party-to-location linkage and site-level attributes including PARTY_SITE_ID, STATUS, PARTY_SITE_NAME, ADDRESSEE, and IDENTIFYING_ADDRESS_FLAG.
• HZ_LOCATIONS (SYNONYM) — contributes the full set of address and location attributes, including the CLLI_CODE column referenced by the user.
• FND_TERRITORIES (SYNONYM) — referenced in the view definition, typically for territory or country resolution associated with location records.

The view text selects SITE.ROWID and joins site, party, and location records, projecting a wide set of columns from each source. It is a read-only composite and inherits the security and partitioning characteristics of its base tables.

Key Columns

The view exposes a broad column set. Notable groups include:

• Party identifiers: PARTY_ID, PARTY_NUMBER, PARTY_NAME, and PARTY_TYPE, supporting party classification and lookup.
• Site identifiers: PARTY_SITE_ID, PARTY_SITE_NAME, STATUS, ADDRESSEE, and IDENTIFYING_ADDRESS_FLAG describe the specific party site record.
• Location identifiers: LOCATION_ID and ADDRESS_KEY link the site to its geographic record.
• Address components: ADDRESS1 through ADDRESS4, STREET, HOUSE_NUMBER, BUILDING, CITY, STATE, PROVINCE, POSTAL_CODE, COUNTY, and COUNTRY, plus the derived ADDRESS and FULL_ADDRESS concatenations.
• Telecom and routing codes: CLLI_CODE (Common Language Location Identifier), DODAAC, TRAILING_DIRECTORY_CODE, DELIVERY_POINT_CODE, and POSTAL_PLUS4_CODE.
• Descriptive and extensible attributes: SHORT_DESCRIPTION, DESCRIPTION, LIFE_CYCLE_STATUS, TIME_ZONE, and ATTRIBUTE_CATEGORY with ATTRIBUTE1 through ATTRIBUTE20.

The CLLI_CODE column originates from HZ_LOCATIONS and is frequently queried to retrieve or validate the standardized location identifier assigned to a party site address.

Common Use Cases and Queries

Typical scenarios include retrieving a party's primary or identifying address, extracting sites for interface processing, and locating records by CLLI or other routing codes.

• Retrieve all sites for a party with their identifying address flag set.
• Extract address detail for outbound interface files by party number.
• Search for locations carrying a specific CLLI_CODE.

A representative query is:

SELECT party_id, party_number, party_name, party_site_id, party_site_name, address1, address2, city, state, postal_code, country, clli_code
FROM apps.csc_hz_party_sites_v
WHERE clli_code = :p_clli_code;

Filtering by PARTY_NUMBER or PARTY_SITE_ID is equally common. Because the view is a composite over TCA tables, query performance depends on indexes on the underlying HZ_* base tables, and it should be used for read-only reporting rather than transactional updates.