Search Results bill_postal_code

Overview

AR_SHIP_ADDRESS_V is a seeded Oracle Receivables view owned by the APPS schema, whose documented purpose is to expose Active Ship to Addresses. It presents the ship-to addresses defined against customer accounts and their sites in a denormalized, report-ready form, resolving the underlying Oracle Trading Community Architecture (TCA) model of parties, accounts, account sites, site uses and locations. The view is used wherever Receivables and downstream modules need a printable or comparable ship-to address without re-joining the full TCA stack: order entry, shipping documentation, invoicing, statement generation, tax and territory lookups, and custom concurrent programs or Discoverer reports. Because it is a view and not a table, it carries no data of its own; its result set is recomputed at query time from the base tables and therefore always reflects current TCA data. The inclusion of both a raw ADDRESS3_DB column and a concatenated ADDRESS3, plus a formatted ADDRESS column composed of space-padded 25-character segments, indicates the view was designed to serve legacy fixed-format report definitions as well as contemporary SQL consumers.

Underlying Base Objects

The ETRM 12.2.2 metadata records the following referenced objects: FND_GLOBAL (PACKAGE), FND_TERRITORIES_VL (VIEW), and the synonyms HZ_CUST_ACCT_RELATE, HZ_CUST_ACCT_SITES, HZ_CUST_SITE_USES, HZ_LOCATIONS, HZ_PARTY_SITES, and DUAL. Functionally, HZ_CUST_ACCT_SITES supplies each customer account site, HZ_CUST_SITE_USES identifies the purpose of each site (ship-to, bill-to), HZ_PARTY_SITES and HZ_LOCATIONS supply the postal address attributes (ADDRESS1–ADDRESS4, CITY, STATE, PROVINCE, COUNTY, COUNTRY, POSTAL_CODE), and FND_TERRITORIES_VL resolves the territory short name appended to the concatenated address strings. FND_GLOBAL is invoked for LOCAL_CHR(44) and LOCAL_CHR(32), which emit the localized comma and space characters so the concatenated address respects the session's language settings. HZ_CUST_ACCT_RELATE — the term the user searched — is the customer account relationship table, providing the customer account and party relationships that anchor the account-to-site hierarchy the view traverses; its presence confirms the view resolves addresses through the account relationship chain rather than a single flat customer record. DUAL supports the arithmetic and NULL handling constructs in the select list.

Key Columns

• ADDRESS1, ADDRESS2, ADDRESS3_DB — discrete location address lines exactly as stored in HZ_LOCATIONS.
• ADDRESS3 — a concatenation of ADDRESS3, ADDRESS4, CITY, STATE/PROVINCE, POSTAL_CODE and territory short name, assembled with FND_GLOBAL.LOCAL_CHR separators.
• ADDRESS — a fixed-width concatenation of the first 25 characters of each address line plus city, state/province and territory, used for report layouts.
• LOCATION, PRIMARY_FLAG — the location identifier and primary flag from the site use record.
• CITY, COUNTY, STATE, PROVINCE, COUNTRY, POSTAL_CODE — parsed address components for filtering and display.
• TERRITORY_ID — the territory identifier associated with the site.
• SU_STATUS, A_STATUS — status of the site use and of the customer account respectively; these govern which records qualify as active.
• BILL_LOCATION, BILL_ADDRESS1, BILL_ADDRESS2 — bill-to information resolved through NVL/DECODE logic from the related bill-to site use, allowing ship-to and bill-to comparison in a single row.

Common Use Cases and Queries

Typical consumers list active ship-to addresses for a customer, validate that a ship-to exists before order import, or compare ship-to and bill-to addresses for consistency checks. A representative query is:

SELECT address1, address2, city, state, postal_code
FROM   apps.ar_ship_address_v
WHERE  su_status = 'A'
AND    a_status  = 'A';

Because the view resolves HZ_CUST_ACCT_RELATE, it can also be joined back to customer account relationship queries to identify addresses shared across related accounts. Filtering on SU_STATUS and A_STATUS is essential, since the view name promises active addresses but the underlying TCA rows retain inactive sites unless the caller restricts them.