Results for “prospect_flag”

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

Overview

ARBV_CUSTOMERS is a Receivables (AR) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a consolidated, reporting-oriented projection of customer master and customer profile information, joining the TCA (Trading Community Architecture) customer entities HZ_CUST_ACCOUNTS, HZ_PARTIES, and HZ_CUSTOMER_PROFILES. Because these entities are separated across TCA tables, a single query against ARBV_CUSTOMERS surfaces the customer identifier, party name and classification, account number, credit and collection attributes, tax attributes, shipping and freight defaults, and organization-level demographic data in one row.

The view is documented in ETRM with a status of VALID and is typically used as a reference source for reporting, data conversion validation, and integration extracts. It does not own data; every column is derived from the underlying TCA tables via the APPS synonyms. The view's internal SQL applies SUBSTRB and DECODE functions for presentation, and uses the EBS "_LA:" lookup-attachment convention to instruct the Oracle Forms and Framework layers to translate coded values into user-facing lookup meanings.

Underlying Base Objects

• HZ_CUST_ACCOUNTS (SYNONYM, alias CU) — Supplies the customer account record, including CUST_ACCOUNT_ID, ACCOUNT_NUMBER, STATUS, CUSTOMER_TYPE, CUSTOMER_CLASS_CODE, ORIG_SYSTEM_REFERENCE, TAX_CODE, TAX_ROUNDING_RULE, TAX_HEADER_LEVEL_FLAG, SHIP_PARTIAL, SHIP_VIA, FOB_POINT, and FREIGHT_TERM.
• HZ_PARTIES (SYNONYM, alias P) — Supplies party-level attributes such as PARTY_NAME, PARTY_TYPE, ORGANIZATION_NAME_PHONETIC, CATEGORY_CODE, SIC_CODE, JGZZ_FISCAL_CODE, TAX_REFERENCE, GSA_INDICATOR_FLAG, plus organization-only fields (EMPLOYEES_TOTAL, YEAR_ESTABLISHED, FISCAL_YEAREND_MONTH, ANALYSIS_FY, potential revenue, MISSION_STATEMENT).
• HZ_CUSTOMER_PROFILES (SYNONYM, alias CP) — Supplies credit and collection profile data, including ACCOUNT_STATUS, CREDIT_RATING, PERCENT_COLLECTABLE, RISK_CODE, and CREDIT_CHECKING.

Because the referenced objects are synonyms pointing into the TCA schema, the view inherits TCA's multi-organization and party model. DECODE logic tied to P.PARTY_TYPE ensures that organization-only attributes return NULL when the party is a person, preserving clean column semantics for mixed customer populations.

Key Columns

• CUST_ACCOUNT_ID / ACCOUNT_NUMBER — Unique customer account identifier and its user-visible account number.
• PARTY_NAME / PARTY_TYPE / ORGANIZATION_NAME_PHONETIC — Party name, party classification (Organization or Person), and phonetic organization name.
• STATUS, CUSTOMER_TYPE, CUSTOMER_CLASS_CODE — Lookup-backed account status, customer type, and category code exposed through the _LA translation convention.
• TAX_CODE, JGZZ_FISCAL_CODE, TAX_REFERENCE — Tax-related identifiers and fiscal codes.
• CREDIT_RATING, RISK_CODE, PERCENT_COLLECTABLE, CREDIT_CHECKING, ACCOUNT_STATUS — Credit and collections profile attributes.
• SHIP_VIA, FOB_POINT, FREIGHT_TERM — Default order-management shipping and freight references.
• ORGANIZATION-ONLY metrics — Employees, year established, fiscal year-end month, analysis fiscal year, and current/next fiscal year potential revenue.

The "_LA:" markers are not literal data; they signal lookup translation metadata (lookup type, code, and meaning column) to the EBS UI layer.

Common Use Cases and Queries

ARBV_CUSTOMERS is commonly used to extract a denormalized customer picture for reporting, reconciliation, and integration into downstream systems.

• Listing active customer accounts with their credit rating and status.
• Extracting party name and account number for conversion validation.
• Reporting organization-level demographics alongside account defaults.

Example query:

SELECT cust_account_id,
       account_number,
       party_name,
       customer_class_code,
       credit_rating,
       risk_code,
       percent_collectable,
       tax_code
FROM   apps.arbv_customers
WHERE  status = 'A';

Because ARBV_CUSTOMERS consolidates three TCA base objects, it removes the need to hand-write joins across HZ_CUST_ACCOUNTS, HZ_PARTIES, and HZ_CUSTOMER_PROFILES, making it a preferred source for customer-centric reporting in both 12.1.1 and 12.2.2.