Search Results ar_lookups




Overview
Explore in AI Chat

Overview

AST_ORG_PROFILES_V is a TeleSales (AST) view owned by the APPS schema. It presents a consolidated, denormalized projection of organization-level party data used by the Oracle TeleSales application. The view joins the Trading Community Architecture (TCA) party registry to organization profile information and decodes numerous lookup codes into their human-readable meanings, producing a single reporting surface for organizational customers.

Within Oracle EBS 12.1.1 and 12.2.2, TeleSales relies on TCA as the system of record for parties and organization profiles. Rather than requiring reporting and integration consumers to reconstruct the multi-table join themselves, AST_ORG_PROFILES_V exposes party identity, organization firmographics, financial indicators, and decoded reference values in one relational row per organization party. Because one of the projected columns is REGISTRATION_TYPE, this view is frequently surfaced when searching for registration type data in an AST context.

Underlying Base Objects

The view is defined over the following documented base objects:

  • HZ_PARTIES (SYNONYM) — the master party entity; drives party name, number, type, status, category, and order history metrics.
  • HZ_ORGANIZATION_PROFILES (SYNONYM) — the organization-specific profile extension holding firmographic and financial attributes, outer-joined to HZ_PARTIES via a PARTY_ID(+) outer join.
  • AR_LOOKUPS (VIEW) — used repeatedly (aliased LKUP through LKUP7) as a lookup decode source for category, ownership, legal status, registration type, and certification level.

The view restricts PARTY.PARTY_TYPE to 'ORGANIZATION', and all lookup joins are outer joins keyed on their respective LOOKUP_TYPE and LOOKUP_CODE pairs.

Key Columns

Common Use Cases and Queries

The view supports organization directory reporting, TeleSales scoring and marketing segmentation, and integration extracts that need decoded organization attributes. Filtering on REGISTRATION_TYPE is a typical requirement.

SELECT party_number,
       organization_name,
       registration_type,
       legal_status,
       duns_number
FROM   apps.ast_org_profiles_v
WHERE  registration_type IS NOT NULL
ORDER  BY organization_name;

A second pattern aggregates order metrics for a specific organization category:

SELECT category_code,
       COUNT(*)                     organization_count,
       SUM(total_ordered_amount)    total_revenue
FROM   apps.ast_org_profiles_v
WHERE  internal_flag = 'Y'
GROUP  BY category_code;

Because the view is read-only and based on TCA synonyms, it should be queried rather than modified. For REST or interface extraction, the unique PARTY_ID is the recommended key for correlating rows back to HZ_PARTIES.