Results for “so_ship_to_contacts_v”

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

Overview

The view SO_SHIP_TO_CONTACTS_V is a reporting and integration object within the Oracle E-Business Suite Order Entry (OE) module. It exposes ship-to contact information for customers, drawing together contact identity, job title, and telephone data into a single denormalized row per active contact. Its principal purpose is to provide a ready-made source of "ship-to" contact records that can be consumed by order entry screens, concurrent programs, interfaces, and custom reports without requiring the caller to reconstruct the multi-table join between contacts, roles, and phone numbers.

The view is particularly relevant to the search term "area_code", since AREA_CODE is one of its exposed columns and is also embedded within the formatted telephone output. This makes the view a convenient source when address book telephone details must be displayed or transmitted alongside contact names for ship-to locations.

Underlying Base Objects

The view is defined over three Oracle Receivables base tables, related through outer joins to ensure that contacts survive even when phone or role data is absent:

• RA_CONTACTS (RC) — the driving table, supplying LAST_NAME, FIRST_NAME, JOB_TITLE, CONTACT_ID, and CUSTOMER_ID. Only rows where STATUS = 'A' (active) are returned.
• RA_PHONES (RPH) — joined via CONTACT_ID(+), supplying AREA_CODE, PHONE_NUMBER, and EXTENSION. The join is filtered so that only the primary, active phone is used via NVL(RPH.PRIMARY_FLAG(+), 'N') = 'Y' and NVL(RPH.STATUS(+), 'A') = 'A'.
• RA_CONTACT_ROLES (RCR) — joined via CONTACT_ID(+), filtering the result set to contacts whose role resolves to SHIP_TO through NVL(RCR.USAGE_CODE, 'SHIP_TO') = 'SHIP_TO'.

The (+) notation indicates Oracle outer-join syntax, meaning a contact is still returned when no matching phone or role record exists; in such cases PHONE_NUMBER_LONG resolves to an empty string.

Key Columns

• LAST_NAME / FIRST_NAME — the contact's individual name components from RA_CONTACTS.
• FULL_NAME — a computed concatenation (LAST_NAME || ', ' || FIRST_NAME) useful for display and sorting.
• JOB_TITLE — the contact's job title, commonly used on order acknowledgements and shipping documents.
• AREA_CODE — the telephone area code from the primary phone record; central to telephone formatting and dialing logic.
• PHONE_NUMBER / EXTENSION — the raw phone number and extension.
• PHONE_NUMBER_LONG — a DECODE-based formatted string producing a value such as (415) 555-1234 EXT 22, or blank when no phone exists.
• CONTACT_ID / CUSTOMER_ID — the primary key identifiers linking back to the contact and customer master records, enabling downstream joins.

Common Use Cases and Queries

Typical uses include populating ship-to contact lists on order entry forms, generating shipping manifests and acknowledgements that require telephone details, and validating contact data during order import interfaces. A basic query filtering by customer and formatting the phone follows:

• SELECT full_name, job_title, area_code, phone_number_long FROM so_ship_to_contacts_v WHERE customer_id = :p_customer_id ORDER BY last_name, first_name;
• Reports searching on the area code, e.g. WHERE area_code = '415', leverage the dedicated column rather than parsing the formatted phone string.
• Integration extracts commonly select contact_id, customer_id, full_name, area_code to feed downstream address book synchronization jobs.

Because the view is documented as "not implemented in this database" in some environments, developers should confirm its availability before depending on it in production code.