Results for “ast_lm_per_quick_w_acc_v”

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

Overview

AST_LM_PER_QUICK_W_ACC_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, documented under the AST – TeleSales product family. It is a component of the Oracle TeleSales / Lead Management framework and serves as the "Quick Win" person-with-account lookup, presenting a consolidated, denormalized list of person-type parties joined to their customer account information. The view is designed to support fast, user-facing search and selection within the TeleSales application, where an agent needs to identify a person, verify their account, and confirm contact and territory details without navigating multiple base tables.

The name parses as "Lead Management, Person, Quick Win, Account, View," reinforcing its role as a pre-joined, performance-oriented projection rather than a transactional entity. Because it exposes descriptive attributes (name, address, phone, email, territory, status) rather than operational columns, it is typically consumed for reporting, list-of-values, and integration extraction rather than for DML. Like all APPS views, it is expected to be treated as read-only; the schema does not provide a documented INSTEAD OF trigger or DML path.

Underlying Base Objects

The view is defined over four referenced objects, three of which are synonyms to base tables:

• HZ_PARTIES (SYNONYM) — aliased PARTY; the primary source of person records. Filtered to PARTY_TYPE = 'PERSON' and restricted to party status values of 'A' (active) or 'I' (inactive).
• HZ_CUST_ACCOUNTS (SYNONYM) — aliased HCA; outer-joined to HZ_PARTIES on PARTY_ID, with an additional outer-join predicate requiring account STATUS = 'A' so that person records without an active account are still returned.
• FND_TERRITORIES_TL (SYNONYM) — aliased FTT; a translated territories table, outer-joined on TERRITORY_CODE = PARTY.COUNTRY. The join is language-qualified using USERENV('LANG') against both LANGUAGE and SOURCE_LANG to return territory names in the session language.
• AR_LOOKUPS (VIEW) — aliased ALK; supplies the decoded meaning for party status. The join uses LOOKUP_TYPE = 'CODE_STATUS' and LOOKUP_CODE = PARTY.STATUS, resolving the status into the STATUS_MEAN column.

The outer-join (+) syntax throughout indicates Oracle legacy join syntax; the view is valid under both EBS 12.1.1 and 12.2.2.

Key Columns

• PARTY_ID, CUST_ACCOUNT_ID, ACCOUNT_NUMBER — keys and human-readable account identifier for the person and their customer account.
• PERSON_FIRST_NAME, PERSON_MIDDLE_NAME, PERSON_LAST_NAME — name components of the person party.
• ADDRESS, CITY, STATE, POSTAL_CODE, PROVINCE, COUNTRY, COUNTRY_NAME — the concatenated address line plus geographic attributes; COUNTRY_NAME is the decoded territory short name.
• EMAIL_ADDRESS — contact email from the party record.
• STATUS, STATUS_MEAN — party status code and its AR_LOOKUPS meaning.
• PHONE_COUNTRY_CODE, PHONE_AREA_CODE, PHONE_NUMBER, PHONE_EXTENSION — primary phone components.
• FULL_PHONE_NUMBER, PHONE_AREA_NUMBER — derived concatenations: the full formatted number and the area code plus number combined.

Common Use Cases and Queries

Typical scenarios include TeleSales agent lookups, person/account reconciliation reports, and extraction of contact data into marketing or CRM integrations.

• Searching for a person by last name and account:
• SELECT party_id, account_number, person_last_name, full_phone_number FROM apps.ast_lm_per_quick_w_acc_v WHERE person_last_name = :name;
• Listing active persons with their territory and contact details:
• SELECT person_first_name, person_last_name, country_name, email_address FROM apps.ast_lm_per_quick_w_acc_v WHERE status = 'A';
• Extracting account/person contact feeds for integration:
• SELECT cust_account_id, account_number, phone_area_number FROM apps.ast_lm_per_quick_w_acc_v;

Because the view has no bind variables or context-dependent filters beyond session language, it can be queried directly; organizations frequently wrap it with additional predicates to limit result sets for performance.