Search Results channel_manager




Overview
Explore in AI Chat

Overview

APPS.AST_PTR_RELATION_DETAILS_V is a supplementary database view in the Oracle E-Business Suite 12.1.1 and 12.2.2 applications schema (APPS). It belongs to the Partner Management (AST) product family and is classified as an internal Oracle view used to simplify form coding rather than as a supported public interface. The FND Design Data identifier AST.AST_PTR_RELATION_DETAILS_V confirms its registration within the applications design repository. The view consolidates partner relationship attributes — including partner level, assignment history, purchase method, preferred VAD, revenue targets and year-to-date figures, channel contacts, and matching indicators — into a single denormalized projection that becomes convenient when an Oracle Forms block requires values spanning multiple base entities.

In the context of the search term "automatic_matching," the view exposes an AUTOMATIC_MATCHING (VARCHAR2) column. This column reflects the partner profile configuration governing whether opportunities or leads are matched automatically to the partner. Reporting or integration code that must evaluate partner matching behavior without direct joins to the partner profile tables can read this attribute from the view.

Oracle's documentation explicitly warns that the view is for Oracle Internal Use Only and is not supported for direct customer access except through standard Oracle Applications programs. Oracle further notes it may change dramatically between minor or major releases, so any dependency should be treated as fragile.

Underlying Base Objects

The view is defined over five referenced objects, each accessed through APPS synonyms:

  • PV_PARTNER_PROFILES — the core partner profile record supplying partner-level attributes such as level, purchase method, and revenue targets.
  • PV_ATTRIBUTE_CODES_VL — a translated attribute code view, typically used to decode lookup or attribute values; this is the only referenced object that is itself a view rather than a table synonym.
  • HZ_PARTIES — the Trading Community Architecture (TCA) registry of parties, providing the party identity behind the partner.
  • HZ_ORGANIZATION_PROFILES — TCA organization profile data, supplying organization-level classification.
  • HZ_RELATIONSHIPS — TCA relationship records linking parties, for example a partner to a channel manager or other contact.
  • JTF_RS_RESOURCE_EXTNS — resource extension information used to resolve resource-based names, such as the channel manager or phone support person.

The documentation states the view is not referenced by any other database object, confirming that it terminates the dependency chain and is only invoked from application form logic.

Key Columns

Common Use Cases and Queries

Typical usage centers on partner administration forms and internal diagnostics. A minimal query retrieving matching configuration is:

  • SELECT partner_id, partner_level, automatic_matching FROM apps.ast_ptr_relation_details_v;
  • SELECT partner_id, channel_manager, phone_support_person, target_revenue, revenue_year_to_date FROM apps.ast_ptr_relation_details_v WHERE partner_level = :level;

Given the internal-use warning, production integrations should source the same attributes from the underlying PV_PARTNER_PROFILES and TCA tables rather than depending on this view.