Results for “csi_srs_party_name_v”

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

Overview

The CSI_SRS_PARTY_NAME_V view is a reporting-oriented database object owned by the APPS schema within the Oracle E-Business Suite Install Base (CSI) module. Its documented purpose is to display all parties who have Customer Products, effectively providing a consolidated registry of the party and customer account combinations that participate in the installed base. The view carries a VALID status in both Oracle EBS 12.1.1 and 12.2.2 and is typically consumed by Oracle Reports, Oracle XML Publisher (BI Publisher) reports, and ad-hoc SQL queries where a flat, denormalized list of installing parties is required.

The view is particularly relevant to users searching for the exists_in_ib flag, since that column is defined directly within this view and serves as the primary indicator of whether a given customer account owns at least one customer product instance in the Install Base repository. This makes the view a convenient single-source construct for validating installed base participation without writing explicit EXISTS subqueries against CSI_ITEM_INSTANCES.

Underlying Base Objects

The ETRM metadata documents three referenced base objects, all exposed via synonyms in the APPS schema:

• HZ_PARTIES — the Trading Community Architecture (TCA) master table of parties (aliased HZP).
• HZ_CUST_ACCOUNTS — the TCA customer account table (aliased HZA), joined to HZ_PARTIES on PARTY_ID.
• CSI_ITEM_INSTANCES — the core Install Base instance table, referenced in a scalar correlated subquery against OWNER_PARTY_ACCOUNT_ID.

The FROM clause performs an inner join between HZ_PARTIES and HZ_CUST_ACCOUNTS on PARTY_ID, meaning only parties that possess a customer account are returned. The EXISTS_IN_IB derivation is executed as an inline scalar subquery with a ROWNUM < 2 restriction, which terminates the lookup after the first matching instance for performance.

Key Columns

• PARTY_NAME — the display name of the party from HZ_PARTIES.PARTY_NAME.
• CUSTOMER_NUMBER — the customer account number from HZ_CUST_ACCOUNTS.ACCOUNT_NUMBER.
• PARTY_ID — the unique TCA party identifier from HZ_PARTIES.PARTY_ID, useful for joins back to other TCA objects.
• EXISTS_IN_IB — a derived DECODE flag returning 'Y' when at least one CSI_ITEM_INSTANCES row exists for the account, and 'N' otherwise. This column is the focal point for the "exists_in_ib" search term.

Common Use Cases and Queries

The most frequent usage is filtering accounts by installed base membership. A typical query would be:

• Listing all parties with installed base presence: SELECT party_name, customer_number, party_id FROM csi_srs_party_name_v WHERE exists_in_ib = 'Y';
• Identifying accounts with no installed base: SELECT customer_number FROM csi_srs_party_name_v WHERE exists_in_ib = 'N';
• Joining to CSI_ITEM_INSTANCES for detailed instance reporting after identifying qualifying accounts via EXISTS_IN_IB.

Note that the view does not expose instance-level detail, so downstream queries requiring serial numbers, instance status, or item information must join to CSI_ITEM_INSTANCES using the customer account identifier.