Results for “cs_ib_party_name_v”

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

Overview

The view CS_IB_PARTY_NAME_V is a reporting and integration construct within the Oracle E-Business Suite CS (Service) module. It presents a consolidated, denormalized projection that joins party-level identification data with installed base customer account data, exposing a party name, its associated customer number, and a flag indicating whether that customer participates in the Installed Base (IB) through the presence of customer product records. Its principal role is to provide a lightweight, query-friendly source for lookups and validation logic where a caller needs to resolve a party name against a customer account number and simultaneously determine whether the customer holds installed base products.

The view is documented under ETRM 12.2.2 metadata, and the provided implementation notes state that it is not implemented in this database. This indicates the view is an optional or legacy object whose presence depends on the specific patch level, product installation, or customization of the target environment rather than a guaranteed baseline object. Consultants should therefore verify existence in the data dictionary before relying on it in custom code or reports. The /*+ FIRST_ROWS */ hint embedded in the view text confirms its intended use as an interactive, row-limiting lookup rather than a bulk extraction source.

Underlying Base Objects

Although the documented base object list is empty in the supplied metadata, the view text explicitly defines its dependencies. It is constructed over two Trading Community Architecture (TCA) registry tables:

• HZ_PARTIES (HZP) — the master party registry supplying PARTY_NAME.
• HZ_CUST_ACCOUNTS (HZA) — the customer account layer supplying ACCOUNT_NUMBER.
• CS_CUSTOMER_PRODUCTS_ALL (CS) — referenced through a scalar subquery to detect installed base participation.

The join is driven by the equality HZP.PARTY_ID = HZA.PARTY_ID, which links the party identity to its customer account. The installed base determination is resolved by correlating CS.CUSTOMER_ID with HZA.CUST_ACCOUNT_ID. This design places the view squarely in the intersection of TCA (party and customer account model) and the Service installed base model.

Key Columns

• PARTY_NAME — sourced from HZ_PARTIES.PARTY_NAME; the display name of the party (organization or person) as maintained in the TCA registry.
• CUSTOMER_NUMBER — sourced from HZ_CUST_ACCOUNTS.ACCOUNT_NUMBER; the business-facing account number. This is the column most relevant to searches for "customer_number," and it is the value users typically key into inquiries and reports.
• EXISTS_IN_IB — a decoded indicator computed by a scalar subquery. When an active record exists in CS_CUSTOMER_PRODUCTS_ALL for the matching customer account, the value is 'Y'; otherwise 'N'. The ROWNUM < 2 predicate ensures only an existence test is performed.

Common Use Cases and Queries

The view supports rapid lookups that combine customer number resolution with installed base qualification.

• Searching for a customer number by party name, or confirming the name behind a known customer number.
• Filtering parties to those with active installed base products, for example to drive service eligibility checks.
• Populating selection lists or validation queries in Forms personalizations, OAF pages, or custom concurrent programs.

Representative query:

SELECT party_name,
       customer_number,
       exists_in_ib
  FROM cs_ib_party_name_v
 WHERE customer_number = :p_customer_number;

To list only customers with installed base presence:

SELECT party_name, customer_number
  FROM cs_ib_party_name_v
 WHERE exists_in_ib = 'Y'
 ORDER BY party_name;

Because the view applies a FIRST_ROWS hint and an existence-only subquery, it is optimized for targeted lookups rather than full-table scans; for high-volume extracts, query the underlying TCA and Service tables directly to avoid repeated subquery evaluation.