Search Results ra_addresses_morg

Overview

RA_ADDRESSES_MORG is a Receivables (AR) reporting view that consolidates customer address information across the party, location, and account site model used in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It presents a flattened, denormalized picture of address data drawn from the Trading Community Architecture (TCA) layer, exposing bill-to, ship-to, market, and territory attributes alongside the descriptive address lines (ADDRESS1 through ADDRESS4, CITY, STATE, PROVINCE, COUNTY, POSTAL_CODE, and COUNTRY). The view is intended primarily for query and reporting convenience, allowing address details to be retrieved without manually joining the underlying TCA and Receivables account site tables. The suffix "MORG" denotes the multi-organization variant, and the view carries ORG_ID, meaning results are partitioned by operating unit. This makes it suitable for operating-unit-scoped reporting, integration extracts, and inquiries such as locating a specific customer address record — for example a search for a particular bank branch or remit-to address.

Underlying Base Objects

The view is defined as a join of three TCA/Receivables entities. HZ_CUST_ACCT_SITES_ALL supplies the account site context (aliased ACCT_SITE), carrying the account site identifier, flags, territory and specialist columns, and the customer account reference. HZ_PARTY_SITES (aliased PARTY_SITE) supplies the party site linkage, contributing PARTY_SITE_ID and PARTY_ID, which connect the address to a party record. HZ_LOCATIONS (aliased LOC) supplies the physical address attributes, including ADDRESS1–ADDRESS4, CITY, STATE, PROVINCE, POSTAL_CODE, COUNTY, COUNTRY, ADDRESS_KEY, ADDRESS_STYLE, and LANGUAGE. The LOCATION_ID is derived from a further assignment entity (LOC_ASSIGN.LOC_ID), reflecting the association between a location and its assignment level. The ETRM metadata records no documented referenced base objects and notes the view is not implemented in the supplied database, but the underlying view text confirms these TCA structures. Because the view exposes CUST_ACCT_SITE_ID as ADDRESS_ID and CUST_ACCOUNT_ID as CUSTOMER_ID, it maps legacy Receivables column names onto the TCA model.

Key Columns

• PARTY_SITE_ID and PARTY_ID — identify the party and its site, enabling joins back to HZ_PARTIES and related TCA views.
• LOCATION_ID and ADDRESS_KEY — the location identifier and key for the physical address record.
• ADDRESS1, ADDRESS2, ADDRESS3, ADDRESS4, CITY, STATE, PROVINCE, COUNTY, POSTAL_CODE, COUNTRY — the address text.
• BILL_TO_FLAG, SHIP_TO_FLAG, MARKET_FLAG — usages that classify how the site is applied.
• CUST_ACCT_SITE_ID (ADDRESS_ID) and CUST_ACCOUNT_ID (CUSTOMER_ID) — the account site and customer account identifiers.
• ORG_ID — the operating unit that owns the record.
• STATUS, ATTRIBUTE1–ATTRIBUTE15, ATTRIBUTE_CATEGORY — descriptive, extensibility, and status information.
• TERRITORY_ID, SERVICE_TERRITORY_ID, PRIMARY_SPECIALIST_ID, SECONDARY_SPECIALIST_ID, CUSTOMER_CATEGORY_CODE — territory and categorization data.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID — audit and concurrent program context.

Common Use Cases and Queries

The view supports locating and validating customer addresses for a given operating unit, populating billing or shipping extracts, and performing data-quality checks on address completeness. A typical query retrieves all addresses for a named customer account:

• SELECT address_id, customer_id, party_site_id, address1, address2, city, state, postal_code, country, bill_to_flag, ship_to_flag, org_id FROM ra_addresses_morg WHERE customer_id = :p_customer_id AND org_id = :p_org_id;
• SELECT address1, city, postal_code FROM ra_addresses_morg WHERE UPPER(address1) LIKE '%BANK%' AND org_id = :p_org_id;
• SELECT a.customer_id, a.address1, a.city, a.country FROM ra_addresses_morg a WHERE a.bill_to_flag = 'Y' AND a.status = 'A';

Because ORG_ID is present, queries should always be constrained by operating unit in multi-org environments. When joining to party or account master data, use PARTY_SITE_ID, PARTY_ID, and CUST_ACCOUNT_ID.