Search Results pv_channel_types_pk

Overview

PV_CHANNEL_TYPES is a reference and setup table owned by the PV (Partner Management) schema in Oracle E-Business Suite, available in both the 12.1.1 and 12.2.2 releases. It stores the definition of channel types used to classify how business is transacted — most notably the distinction between direct and indirect channels. Within Partner Management, this classification underpins channel partner and partner program configuration, allowing organizations to segment partners, opportunities, and transactions according to the route to market. The table is registered as VALID in the ETRM data dictionary for 12.2.2 and carries 32 documented columns.

The heuristic Data Vault classification mined from the foreign key structure is standalone, which suggests modeling this object as an independent reference (hub-like) entity rather than as a link or satellite. In practice, a Data Vault or warehouse design would treat CHANNEL_TYPE_ID as the business key of a small hub or reference table, with descriptive attributes such as CHANNEL_LOOKUP_TYPE and INDIRECT_CHANNEL_FLAG held alongside it.

Key Information Stored

The most significant columns documented in the ETRM schema are:

• CHANNEL_TYPE_ID — the surrogate primary key, defined by constraint PV_CHANNEL_TYPES_PK and additionally protected by unique index PV_CHANNEL_TYPES_U1.
• CHANNEL_LOOKUP_CODE and CHANNEL_LOOKUP_TYPE — the business-key candidates, enforced by unique index PV_CHANNEL_TYPES_U2. Together they identify a channel type by a code value and its associated lookup category.
• INDIRECT_CHANNEL_FLAG — the functional discriminator indicating whether the channel is indirect (partner-mediated) or direct.
• RANK — an ordering attribute used to sequence or prioritize channel types.
• SECURITY_GROUP_ID — the multi-tenant / security grouping reference, with a foreign key to FND_SECURITY_GROUPS.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the Oracle Applications framework.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO-column audit trail.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program and audit context for the row's last modification.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield (DFF) columns for extensible customer-defined data.

Note that the lookup code/type pairing reinforces the convention that channel types are seeded and validated against Oracle lookups, making the table a controlled vocabulary for partner channel classification.

Common Use Cases and Queries

Typical scenarios include identifying all indirect channels for partner reporting, driving defaulting logic in channel partner setup, and joining channel type descriptions to transactional partner data. Common query patterns include:

• Retrieving indirect channels: SELECT channel_type_id, channel_lookup_code FROM pv_channel_types WHERE indirect_channel_flag = 'Y'.
• Resolving a lookup value to its surrogate key via the business key: SELECT channel_type_id FROM pv_channel_types WHERE channel_lookup_code = :code AND channel_lookup_type = :type.
• Extracting the full reference set for a data warehouse dimension: SELECT channel_type_id, channel_lookup_type, channel_lookup_code, indirect_channel_flag, rank FROM pv_channel_types ORDER BY rank.
• Auditing setup changes using the WHO and concurrent program columns, filtering on last_update_date and last_updated_by.

Because the table is small and reference-oriented, it is frequently cached or replicated into reporting schemas; joins to it are typically on CHANNEL_TYPE_ID.

Related Objects

• FND_SECURITY_GROUPS — referenced by PV_CHANNEL_TYPES.SECURITY_GROUP_ID, governing row-level security for channel type records.
• FND_LOOKUP_VALUES — the customary source for CHANNEL_LOOKUP_TYPE and CHANNEL_LOOKUP_CODE validation.
• PV_CHANNEL_TYPES_PK / PV_CHANNEL_TYPES_U1 / PV_CHANNEL_TYPES_U2 — the primary key and unique index structures that enforce identity and business-key uniqueness.
• Partner Management partner and program tables — channel classification is consumed by partner setup objects that reference CHANNEL_TYPE_ID to categorize partners and channels.
• Channel manager and partner reporting views — reporting objects that denormalize channel type descriptions for analytics.
• FND_STANDARD audit and DFF structures — the framework tables and definitions that back the WHO columns and ATTRIBUTE flexfield segments.