Results for “csd_customer_details_v”

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

Overview

CSD_CUSTOMER_DETAILS_V is a denormalized reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the CSD (Depot Repair) product family and presents consolidated customer information by joining party, account, and party site data. The view is designed to expose a single row per customer account, pairing the bill-to address of a party with the corresponding ship-to address, so that downstream Depot Repair flows, service requests, and return/repair transactions can resolve customer identity and addressing without navigating the full Oracle Trading Community Architecture (TCA) model.

Because CSD_CUSTOMER_DETAILS_V is a view rather than a base table, it holds no data of its own. Its role is predominantly reporting and integration: it provides a flattened projection of customer details that can be queried directly by concurrent programs, forms, XML Publisher reports, OBIEE extracts, and custom interfaces. The object carries a VALID status in the APPS schema, meaning its definition compiles successfully against the referenced TCA objects.

Underlying Base Objects

The view is defined over the following documented base objects, all referenced through APPS synonyms:

• HZ_PARTY_SITES_V — the source of address and site use information. The view text references it twice, aliased HPS1 for BILL_TO sites and HPS2 for SHIP_TO sites.
• HZ_CUST_ACCOUNTS — the customer account header, supplying account number and account name. Referenced twice as HCA1 (bill-to side) and HCA2 (ship-to side).
• HZ_PARTIES — the party master record, providing party number, party name, party type, and person name attributes.

The join logic is critical to interpreting the view correctly. HPS1 is restricted to SITE_USE_TYPE = 'BILL_TO' and joined to HCA1 and HP on PARTY_ID, while HPS2 is restricted to SITE_USE_TYPE = 'SHIP_TO' and joined to HCA2 on PARTY_ID. The two branches are joined only through the party identifier, so a row is returned when a party has both a bill-to and a ship-to site use defined. This makes HZ_PARTY_SITES_V — the object the user searched for — the central dependency of the view, since it supplies every address and country attribute projected.

Key Columns

• ROW_ID — row identifier derived from HCA1.ROWID, useful for identifying the source customer account row.
• PARTY_ID, PARTY_SITE_ID, LOCATION_ID — TCA keys linking the row back to the party, the specific party site, and the location record.
• PARTY_NUMBER, PARTY_NAME, PARTY_TYPE — party-level identity, including whether the party is a person, organization, or group.
• PERSON_FIRST_NAME, PERSON_LAST_NAME — populated for person-type parties.
• ACCOUNT_NUMBER, ACCOUNT_NAME — customer account attributes from HZ_CUST_ACCOUNTS.
• BILL_TO_COUNTRY, BILL_TO_ADDRESS — concatenated bill-to address assembled from the BILL_TO party site.
• SHIP_TO_COUNTRY, SHIP_TO_ADDRESS — concatenated ship-to address assembled from the SHIP_TO party site.

The address columns are concatenations of ADDRESS1 through ADDRESS4, CITY, STATE, and POSTAL_CODE. Because the concatenation does not insert delimiters between STATE and POSTAL_CODE, formatting in reports should account for this known behavior.

Common Use Cases and Queries

Typical uses include displaying customer bill-to and ship-to details on Depot Repair return documents, resolving customer identity for service authorizations, and feeding address data into shipping or invoicing interfaces. The view is also convenient for ad hoc TCA reconciliation, since it surfaces party, account, and site attributes in one pass.

A representative query selecting customer details for a given party number:

• SELECT party_id, party_name, account_number, bill_to_address, ship_to_address FROM apps.csd_customer_details_v WHERE party_number = :p_party_number;

Because the view performs multiple joins across HZ_PARTY_SITES_V, HZ_CUST_ACCOUNTS, and HZ_PARTIES without an explicit date or active-record filter, callers should apply their own partitioning or party-level predicates to control result size. When broader site coverage is required, HZ_PARTY_SITES_V or the underlying HZ_PARTY_SITES table should be queried directly rather than relying on this two-branch view.