Search Results hz_cust

Overview

APPS.JAI_CMN_CUST_ADDRESS_V is a custom Oracle E-Business Suite view owned by the APPS schema and delivered as part of the India Localization (JAI) module. It presents a unified, consolidated listing of addresses drawn from two distinct sources within the EBS data model: customer addresses held in the Oracle Trading Community Architecture (TCA) tables, and inventory organization addresses held in the HR locations tables. The view therefore serves as a single reporting and integration access point for address data that would otherwise require separate queries against unrelated schema objects.

Its primary consumers are localization reports, tax and excise document generation, and interfaces that require a uniform address representation regardless of whether the party is a customer or an internal organization. The view carries the "JAI_CMN" prefix, indicating it belongs to the common (shared) layer of the India localization rather than to a specific functional sub-module. It is relevant to both Oracle EBS 12.1.1 and 12.2.2, though the ETRM metadata supplied here is documented against 12.2.2. The presence of embedded EBIZ-00190 and EBIZ-00191 change references in the view text confirms it has been patched and extended in the field.

Underlying Base Objects

The documented base objects referenced by the view are HR_GENERAL (package), HR_LOCATIONS (view), HZ_CUST_ACCT_SITES_ALL (synonym), HZ_LOCATIONS (synonym), HZ_PARTY_SITES (synonym), JAI_CMN_CUS_ADDRESSES (synonym), and JAI_CMN_INVENTORY_ORGS (synonym).

• HZ_LOCATIONS, HZ_PARTY_SITES, HZ_CUST_ACCT_SITES_ALL — the TCA customer address chain, joined on location_id, party_site_id, and cust_acct_site_id respectively.
• JAI_CMN_CUS_ADDRESSES — the India localization customer address table, linked on address_id = cust_acct_site_id and customer_id = party_id.
• HR_LOCATIONS — supplies organization address lines for the second branch of the union.
• JAI_CMN_INVENTORY_ORGS — supplies the organization_id for inventory organizations.
• HR_GENERAL — referenced as a package dependency, typically for location or address formatting utilities invoked by dependent logic.

The view is a UNION ALL of two SELECT statements. The first returns customer rows with Attribute1 hard-coded to 'Customer'; the second returns organization rows with Attribute1 set to 'Organization'. The union was changed to UNION ALL only after EBIZ-00190; the original UNION was commented out.

Key Columns

• ID — for customer rows, cust_acct_site_id; for organization rows, location_id. This is the polymorphic key and must be interpreted together with Attribute1.
• ADDRESS1, ADDRESS2, ADDRESS3 — address lines. Added for EBIZ-00191; earlier versions concatenated lines into a single address column.
• CUSTOMER_ID — customer party identifier; populated only for customer rows (NULL from the organization branch).
• ATTRIBUTE1 — discriminator, either 'Customer' or 'Organization'.
• ORGANIZATION_ID — inventory organization identifier; populated only for organization rows.
• OPERATING_UNIT — org_id from hz_cust_acct_sites_all; populated only for customer rows.

Common Use Cases and Queries

Typical scenarios include printing customer addresses on India localization invoices, resolving ship-to and bill-to information for excise reporting, and populating address blocks in custom EBiz-facing pages such as the "/ebiz/faces" style applications referenced in the user search. A standard retrieval query follows:

SELECT id, attribute1, address1, address2, address3,
       customer_id, organization_id, operating_unit
  FROM apps.jai_cmn_cust_address_v
 WHERE attribute1 = 'Customer';

To isolate organization addresses:

SELECT id, organization_id, address1, address2, address3
  FROM apps.jai_cmn_cust_address_v
 WHERE attribute1 = 'Organization';

Because the union branches populate disjoint columns, any query should filter on attribute1 explicitly rather than relying on non-null checks. Joins back to HZ_CUST_ACCT_SITES_ALL should use id for customer rows, while joins to inventory organizations use organization_id. Note that Attribute1 is a required filtering key: without it, results contain a mixture of customer and organization rows that most downstream processes cannot consume uniformly.