Search Results acct_site

Overview

ZX_LOC_ASSIGNMENTS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, registered under the FND – Application Object Library product grouping. The view presents a consolidated list of customer location assignments that are eligible for tax geography determination. It functions as a staging or reconciliation source that links HZ_LOCATIONS records to the operating unit (ORG_ID) under which the corresponding customer account site is defined, so that tax configuration and location-based tax assignment processes can resolve which locations require geography mapping.

The view is defined as a UNION of two distinct query branches. The first branch returns locations that already carry a successful geography structure mapping, requiring a matching record in HZ_GEO_STRUCT_MAP and a successful usage entry in HZ_GEO_NAME_REFERENCE_LOG with USAGE_CODE = 'TAX' and MAP_STATUS = 'S'. The second branch returns locations whose country has no HZ_GEO_STRUCT_MAP entry at all, drawing the country from HZ_GEOGRAPHIES where GEOGRAPHY_TYPE = 'COUNTRY' and applying a NOT EXISTS filter. Together the branches give a complete population of taxable customer locations — those already mapped and those still awaiting a structure-map definition.

Underlying Base Objects

The documented base objects, all referenced through APPS synonyms, are:

• HZ_LOCATIONS — primary source of the LOCATION_ID and audit/WHO columns exposed by the view.
• HZ_CUST_ACCT_SITES_ALL — supplies ORG_ID, tying each location to an operating unit through the account site.
• HZ_PARTY_SITES — joins the account site to the location via PARTY_SITE_ID and LOCATION_ID.
• HZ_GEO_STRUCT_MAP — geography structure mapping table; drives the first UNION branch and the NOT EXISTS exclusion in the second.
• HZ_GEO_NAME_REFERENCE_LOG — validation log confirming a successful TAX usage geography assignment for the location.
• HZ_GEOGRAPHIES — provides COUNTRY_CODE for countries lacking a structure map entry.

The join chain is consistent across both branches: account site to party site, party site to location, and location to the geography-definition source. DISTINCT is applied to each branch, so duplicate account-site-to-location combinations are collapsed.

Key Columns

• LOCATION_ID — the HZ_LOCATIONS primary key identifying the physical location.
• ORG_ID — operating unit of the customer account site; central to multi-org tax reporting.
• LOC_ID — always NULL in this view, cast via TO_NUMBER(NULL). It is a placeholder column retained for interface or downstream compatibility.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns carried from HZ_LOCATIONS.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context columns from HZ_LOCATIONS.
• WH_UPDATE_DATE — warehouse update timestamp from HZ_LOCATIONS.
• OBJECT_VERSION_NUMBER — optimistic locking version for the location row.
• CREATED_BY_MODULE, APPLICATION_ID — origin metadata identifying the module and application that created the location record.

Common Use Cases and Queries

Typical scenarios include reconciling taxable customer locations against geography structure maps, identifying locations in countries that still require a structure-map definition, and reporting location counts by operating unit for tax setup verification.

List locations already mapped and confirmed for tax usage:

• SELECT location_id, org_id FROM zx_loc_assignments_v WHERE org_id = :p_org_id;

Identify locations whose country has no structure-map entry (the second UNION branch):

• SELECT a.location_id, a.org_id FROM zx_loc_assignments_v a WHERE NOT EXISTS (SELECT 1 FROM hz_geo_struct_map m WHERE m.country_code = (SELECT country FROM hz_locations l WHERE l.location_id = a.location_id) AND m.loc_tbl_name = 'HZ_LOCATIONS');

Count assigned taxable locations per operating unit:

• SELECT org_id, COUNT(DISTINCT location_id) FROM zx_loc_assignments_v GROUP BY org_id;

Because the second UNION branch pulls countries absent from HZ_GEO_STRUCT_MAP, result sets can include locations not yet configured for geography validation; consumers should filter or reconcile accordingly before treating results as finalized tax assignments.