Results for “current_role_state”

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

Overview

AST_CUST_ACCOUNTS_ROLES_V is a TeleSales (AST) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a denormalized, read-only projection of customer account role assignments, combining role data from the Trading Community Architecture (TCA) model with the associated party, party site, account site, address, and territory attributes required by TeleSales and other downstream consumers.

The view is the principal access point for queries involving acct_role_type and related role classification values. Rather than forcing callers to navigate the HZ_CUST_ACCOUNT_ROLES, HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES, and HZ_LOCATIONS hierarchies independently, it exposes a flattened row per customer account role. Each row carries both the coded ROLE_TYPE value and its decoded MEANING, which is central to the purpose of the view in TeleSales reporting and integration.

Underlying Base Objects

The view is defined over the following documented objects, all referenced through APPS synonyms except AR_LOOKUPS, which is itself a view:

• HZ_CUST_ACCOUNT_ROLES — source of role rows, identifiers, role state, dates, primary flag, descriptive flexfield attributes, and audit columns.
• HZ_CUST_ACCOUNTS and HZ_CUST_ACCT_SITES — account header and account site context.
• HZ_PARTIES and HZ_RELATIONSHIPS — party identity, party name, person name components, and the relationship linkage between party and role.
• HZ_PARTY_SITES and HZ_LOCATIONS — party site and address attributes, joined to the account site with outer joins.
• FND_TERRITORIES_TL — territory short name for the address country.
• AR_LOOKUPS — joined twice, once to decode ROLE_TYPE into MEANING, and once to decode CURRENT_ROLE_STATE into a second meaning column.

The join to HZ_CUST_ACCT_SITES and HZ_PARTY_SITES is outer ((+)), so roles that are not yet associated with a site still appear. Inner joins to HZ_PARTIES, HZ_RELATIONSHIPS, HZ_CUST_ACCOUNTS, HZ_LOCATIONS, and FND_TERRITORIES_TL restrict the result set to roles whose party, relationship, account, and address context is fully resolvable.

Key Columns

• ROLE_TYPE and MEANING — the coded and decoded customer account role type (for example, Bill-To, Ship-To, or other AR lookup–defined roles). This is the column set most commonly targeted by searches on acct_role_type.
• CUST_ACCOUNT_ROLE_ID, PARTY_ID, CUST_ACCOUNT_ID, CUST_ACCT_SITE_ID, PARTY_SITE_ID — the primary keys and foreign keys that trace the role back into the TCA model.
• PARTY_NAME, PERSON_FIRST_NAME, PERSON_MIDDLE_NAME, PERSON_LAST_NAME — party identification, whether the party is an organization or a person.
• CURRENT_ROLE_STATE and the decoded CURRENT_ROLE_STATE_EFFECTIVE — the role's current status, decoded through AR_LOOKUPS.
• BEGIN_DATE, END_DATE, PRIMARY_FLAG — role validity window and primary designation.
• Address columns (ADDRESS1–ADDRESS4, CITY, STATE, PROVINCE, COUNTY, POSTAL_CODE, COUNTRY) plus TERRITORY_SHORT_NAME — the site's geographic context.
• Audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, OBJECT_VERSION_NUMBER) and ATTRIBUTE1–ATTRIBUTE20 — standard EBS audit and DFF storage.

Common Use Cases and Queries

Typical uses include TeleSales account/role 360 reporting, validating that a party holds a required account role before an order or call, and exporting role data to downstream systems. A representative query that lists all roles of a given type for a customer is:

• SELECT party_name, cust_account_id, role_type, meaning, current_role_state_effective, primary_flag
• FROM apps.ast_cust_accounts_roles_v
• WHERE role_type = 'BILL_TO'
• AND current_role_state_effective = 'Active';

To retrieve all roles for a specific account, filter on CUST_ACCOUNT_ID; to assemble a site-level address report, select the address and territory columns grouped by CUST_ACCT_SITE_ID. Because the view resolves lookup meanings through AR_LOOKUPS, queries should never hard-code meaning strings when a coded lookup value is available.