Results for “as_dossier_addresses_v”

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

Overview

AS_DOSSIER_ADDRESSES_V is a Sales Foundation (AS) view that presents order history address information for both ship-to and bill-to locations associated with order headers. In Oracle EBS 12.1.1 and 12.2.2, order history and dossier-style reporting require a consolidated, denormalized picture of the addresses and contacts attached to historic orders. This view serves that purpose by joining order header records to their corresponding ship-to and invoice-to site uses, addresses, customers, and contacts.

Functionally, the view exposes two parallel sets of address data: one for the ship-to party and one for the bill-to (invoice-to) party. Each set includes the contact person (last and first name), the customer identity (ID, name, number), and the full postal address (multiple address lines, city, state, province, postal code, county, and country). This makes the view particularly useful for order history reporting, archival extracts, and integration interfaces where a single row per order header is required with resolved address detail.

The column SHIP_TO_CONTACT_LAST_NAME is directly relevant to the search that led to this object. It surfaces the last name of the contact recorded against the ship-to contact ID on the order header, allowing report authors and integration developers to reference a meaningful contact identifier without having to join RA_CONTACTS separately.

Underlying Base Objects

The view is defined over nine base tables. The driving table is SO_HEADERS (aliased HEAD), which supplies the header ID, audit columns, ship-to and invoice-to site use IDs, and the corresponding contact IDs. Address detail is sourced from RA_ADDRESSES, joined twice — once for the ship-to address and once for the invoice-to address. Customer identity is drawn from RA_CUSTOMERS, also joined twice. Contact names come from RA_CONTACTS, again joined twice. Site use records are resolved through RA_SITE_USES, joined twice to link each header's site use ID to its address.

All joins other than the one from the header to the driving header record itself are outer joins. This is significant: orders that lack a ship-to or bill-to contact, site use, address, or customer record will still be returned, with NULL values in the affected columns. The RA_ tables supply the customer, contact, and address master data, while SO_HEADERS anchors the result set to a specific order.

Key Columns

• ROW_ID, HEADER_ID — The row identifier and the order header identifier that anchors each record.
• SHIP_TO_CONTACT_ID, SHIP_TO_CONTACT_LAST_NAME, SHIP_TO_CONTACT_FIRST_NAME — The ship-to contact identifier and the resolved contact name fields from RA_CONTACTS.
• SHIP_TO_CUSTOMER_ID, SHIP_TO_CUSTOMER, SHIP_TO_CUSTOMER_NUMBER — Customer identity associated with the ship-to address.
• SHIP_TO_ADDRESS_ID and SHIP_TO_ADDRESS1–4, SHIP_TO_CITY, SHIP_TO_STATE, SHIP_TO_PROVINCE, SHIP_TO_POSTAL_CODE, SHIP_TO_COUNTY, SHIP_TO_COUNTRY — The fully resolved ship-to postal address.
• BILL_TO_SITE_USE_ID, BILL_TO_CONTACT_ID, BILL_TO_C… — The parallel invoice-to columns, including contact and address attributes.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard audit columns inherited from SO_HEADERS.

Common Use Cases and Queries

Typical scenarios include order history extracts, dossier reporting, and resolving contact and address detail for legacy orders. A common query to find order history by ship-to contact last name is:

SELECT header_id, ship_to_contact_last_name, ship_to_contact_first_name, ship_to_city, ship_to_country FROM as_dossier_addresses_v WHERE ship_to_contact_last_name = 'SMITH';

For interface extracts requiring a single consolidated record per order, all columns can be selected filtered by header_id or by creation date range. Because the joins are outer joins, report authors should test for NULL contact or address values before applying string operations or equality filters on the name and address columns.