Search Results ams_p_acct_v

Overview

AMS_P_ACCT_V is a validity-checked view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Within the AMS (Marketing) product family, it exposes customer account records sourced from the Oracle Receivables and Trading Community customer model. Per the ETRM documentation, the view "returns all entries from the HZ_CUST_ACCOUNTS_ALL table" and is designated "Used for list generation only." This designation is significant: the view is intended to populate selection lists, Lov (List of Values) components, and lookup-driven UI elements within AMS marketing pages, rather than to serve as a transactional or high-volume reporting source. It therefore provides a denormalized, presentation-friendly projection of account data for marketing list building, audience selection, and account pickers embedded in AMS list generation flows.

Underlying Base Objects

According to ETRM 12.2.2 metadata, the referenced base object is HZ_CUST_ACCOUNTS, resolved at runtime via its APPS synonym (conceptually HZ_CUST_ACCOUNTS_ALL). The view is a straightforward single-table projection with column aliasing. The first two columns are renamed: CUST_ACCOUNT_ID is exposed as AMS_ACCT_ID, and PARTY_ID is exposed as CUST_PARTY_ID. These aliases align the view's interface with AMS conventions, where the account identifier and party identifier are consumed by AMS list-generation APIs and concurrent programs. Because the definition references only one base object and applies no joins, filters, or aggregation, the view inherits the row set and security characteristics of HZ_CUST_ACCOUNTS_ALL. Note that the view definition includes no ORG_ID predicate; callers that require operating-unit isolation must apply security context appropriately. The view is not a multi-org secured object itself, and developers should confirm that any consumer running under Multi-Org rules applies the correct MO profile context.

Key Columns

The view exposes a broad set of customer account attributes. Principal columns include:

• AMS_ACCT_ID (aliased from CUST_ACCOUNT_ID) — the primary account identifier used by AMS for account selection.
• CUST_PARTY_ID (aliased from PARTY_ID) — the owning party (organization or person) in the TCA model.
• ACCOUNT_NUMBER — the human-readable customer account number.
• STATUS, CUSTOMER_TYPE, CUSTOMER_CLASS_CODE — account lifecycle and classification attributes used to filter eligible accounts in list generation.
• CURRENT_BALANCE, CREDIT_CLASSIFICATION_CODE, ACCOUNT_LIABLE_FLAG, RESTRICTION_LIMIT_AMOUNT — credit and financial standing indicators.
• ACCOUNT_ESTABLISHED_DATE, ACCOUNT_ACTIVATION_DATE, ACCOUNT_TERMINATION_DATE — dates supporting account-eligibility windows.
• PRIMARY_SALESREP_ID, SALES_CHANNEL_CODE, PRIMARY_SPECIALIST_ID, SECONDARY_SPECIALIST_ID — sales and marketing ownership fields.
• PAYMENT_TERM_ID, PRICE_LIST_ID, ORDER_TYPE_ID, FREIGHT_TERM, SHIP_VIA, WAREHOUSE_ID — order-management defaults.
• Who columns and attribute flexfields — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_ID, and ATTRIBUTE1–20 / GLOBAL_ATTRIBUTE1–20.

Because the view text includes all documented columns, note that the user's search term "hold_bill_flag" is not one of the columns exposed by AMS_P_ACCT_V. Billing hold attributes reside on other customer and site-level objects (for example, credit and billing profile tables in Receivables), not on this AMS view. A query searching AMS_P_ACCT_V for HOLD_BILL_FLAG will raise ORA-00904.

Common Use Cases and Queries

Typical uses include populating account selection lists during AMS list generation, validating that a chosen account is active, and retrieving account context for marketing campaigns. A representative query:

SELECT ams_acct_id, cust_party_id, account_number, status, customer_class_code, current_balance FROM apps.ams_p_acct_v WHERE status = 'A' ORDER BY account_number;

For account pickers restricted to a class:

SELECT ams_acct_id, account_number FROM apps.ams_p_acct_v WHERE customer_class_code = :p_class AND NVL(status,'A') = 'A';

To locate accounts for a specific party:

SELECT ams_acct_id, account_number, account_activation_date FROM apps.ams_p_acct_v WHERE cust_party_id = :p_party_id;

Given its "list generation only" status, this view should not be used for heavy extraction or as a substitute for direct queries against HZ_CUST_ACCOUNTS_ALL when full multi-org security and performance tuning are required. Developers seeking billing hold logic must reference the appropriate Receivables billing profile objects instead.