Results for “bic_parties_v”

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

Overview

BIC_PARTIES_V is a read-only database view historically catalogued under the BIC — Customer Intelligence product family within Oracle E-Business Suite. The BIC module is documented as obsolete in Oracle EBS 12.1.1 and 12.2.2, and the view is recorded in ETRM as "Not implemented in this database." As a result, BIC_PARTIES_V is not shipped or created in a standard Oracle EBS 12.1.1 or 12.2.2 installation and should be treated as a legacy artifact rather than a supported reporting or integration interface. Its purpose, as reflected in the view text, was to present a consolidated customer name alongside the identifiers that tie a trading party to its customer account record, providing a simplified, denormalized projection of party and account data for downstream customer intelligence reporting.

Underlying Base Objects

The view is defined over two standard Oracle Receivables and Trading Community Architecture (TCA) base tables: HZ_PARTIES (aliased P) and HZ_CUST_ACCOUNTS (aliased A). The join condition is A.PARTY_ID = P.PARTY_ID, which links each customer account to its owning party record in the TCA registry. The HZ_PARTIES table supplies the party identity, including PERSON_FIRST_NAME, PERSON_MIDDLE_NAME, PERSON_LAST_NAME, PARTY_NAME, PARTY_TYPE, and PARTY_ID. The HZ_CUST_ACCOUNTS table supplies the customer account context, including CUST_ACCOUNT_ID and ACCOUNT_NUMBER. ETRM documentation does not list referenced base objects explicitly; the relationship above is derived directly from the stored view text rather than from a separately documented object mapping.

Key Columns

• CUSTOMER_NAME — A derived display name. For PARTY_TYPE = 'PERSON', the view concatenates PERSON_FIRST_NAME, PERSON_MIDDLE_NAME, and PERSON_LAST_NAME with spaces. For PARTY_TYPE = 'ORGANIZATION', it returns PARTY_NAME. Because the DECODE covers only these two values, parties of other types yield NULL.
• PARTY_ID — The unique identifier of the party in HZ_PARTIES, the primary TCA party key.
• CUST_ACCOUNT_ID — The unique identifier of the customer account in HZ_CUST_ACCOUNTS, linking the party to its receivable account.
• ORG_ID — Exposed as a literal NULL in the SELECT list, providing a placeholder for multi-org filtering rather than a genuine operating unit value.
• ACCOUNT_NUMBER — The human-readable customer account number from HZ_CUST_ACCOUNTS.

Common Use Cases and Queries

The documented use case is customer intelligence reporting, where a simple list of account numbers, party identifiers, and resolved customer names is required without navigating the full TCA model. A representative query is:

SELECT CUSTOMER_NAME, PARTY_ID, CUST_ACCOUNT_ID, ACCOUNT_NUMBER FROM BIC_PARTIES_V WHERE CUSTOMER_NAME LIKE :p_name;

Analysts might also drive a lookup by account number:

SELECT PARTY_ID, CUSTOMER_NAME FROM BIC_PARTIES_V WHERE ACCOUNT_NUMBER = :p_account_num;

Because ORG_ID is always NULL, filtering by operating unit through this view is not possible; multi-org logic must be applied against the underlying tables or a different view. Given the obsolete status and the "Not implemented" designation, the recommended practice on EBS 12.1.1 and 12.2.2 is to reproduce the equivalent logic directly against HZ_PARTIES and HZ_CUST_ACCOUNTS, which remain fully supported base tables, rather than relying on BIC_PARTIES_V. Any legacy code, custom report, or interface referencing BIC_PARTIES_V should be reviewed and migrated accordingly.