Search Results pv_attribute_codes_vl

Overview

AST_PTR_RELATION_DETAILS_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite TeleSales (AST) module. It consolidates partner relationship data, partner profile attributes, revenue targets, and organizational preferences into a single queryable structure that supports partner performance analysis, channel management reporting, and downstream integration. The view denormalizes information that would otherwise require multiple joins across the Oracle Trading Community Architecture (TCA) and TeleSales partner tables, presenting a flattened result set suitable for concurrent programs, Oracle Discoverer workbooks, and custom report development.

The view is particularly relevant to partner revenue tracking and currency analysis, since it exposes both target and actual revenue figures alongside the functional currency preference of the party organization. The TARGET_CURRENCY_CODE column surfaces the preferred functional currency associated with the partner organization profile, enabling reporting in the appropriate currency context.

Underlying Base Objects

The view is defined over the following documented base objects:

• PV_PARTNER_PROFILES (synonym) — the primary driver table, providing partner-level profile attributes such as target and actual revenue, partner level, purchase method, and resource assignments.
• PV_ATTRIBUTE_CODES_VL (view) — supplies the attribute code (partner level) description through a language-dependent lookup.
• HZ_RELATIONSHIPS (synonym) — establishes the relationship between the partner party and the subject party, filtered on DIRECTIONAL_FLAG = 'F'.
• HZ_ORGANIZATION_PROFILES (synonym) — provides the organization's preferred functional currency, constrained to the current profile via EFFECTIVE_END_DATE IS NULL.
• HZ_PARTIES (synonym) — supplies the preferred VAD party name.
• JTF_RS_RESOURCE_EXTNS (synonym) — referenced twice, once for the channel manager and once for the phone support representative, resolving resource names.

Outer joins are applied to the attribute code, preferred VAD party, channel manager, and phone support resource lookups so that partner rows are retained even when these optional references are null.

Key Columns

The view exposes the following significant columns:

• PARTNER_ID — the identifier of the partner party, joining to HZ_PARTIES and PV_PARTNER_PROFILES.
• TARGET_CURRENCY_CODE — the preferred functional currency associated with the partner's organization profile, used to interpret TARGET_REVENUE values.
• REV_TO_DATE_CURRENCY_CODE — the currency context for revenue-to-date figures.
• TARGET_REVENUE and REVENUE_YEAR_TO_DATE — the partner's revenue goal and achieved revenue.
• PARTNER_LEVEL — the attribute code representing the partner's classification tier.
• PURCHASE_METHOD — how the partner's purchases are conducted.
• OPPORTUNITY_EXCHANGE — flag indicating lead sharing approval.
• AUTOMATIC_MATCHING — flag permitting automatic matching of opportunities.
• CHANNEL_MANAGER and PHONE_SUPPORT_PERSON — resource names for assigned individuals.
• LAST_ASSIGNMENT_DATE and PREFERRED_VAD — assignment recency and preferred value-added distributor.

Common Use Cases and Queries

Typical usage includes partner revenue attainment reporting, currency-aware target analysis, and resource assignment audits. A representative query selecting target revenue with its currency context follows:

SELECT partner_id, target_currency_code, target_revenue, revenue_year_to_date, partner_level FROM apps.ast_ptr_relation_details_v WHERE target_currency_code = 'USD';

Additional scenarios include listing partners by channel manager, filtering on automatic_matching = 'Y', or reconciling revenue-to-date against targets for a given partner level. Because the view relies on outer joins, reports should anticipate null values in optional columns such as channel manager and preferred VAD.