Results for “pv_partner_program_b”

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

Overview

PV_PARTNER_PROGRAM_B is the foundational base table of the Partner Management module (product code PV) in Oracle E-Business Suite 12.1.1 and 12.2.2. It captures the definition of a partner program — the business construct through which an enterprise enrolls, qualifies, tier-structures, and governs its channel partners — together with the membership rules that govern how partners are admitted to and retained within that program. Every downstream partner management artifact, including memberships, enrollment requests, benefits, contracts, checklists, and responsibility mappings, is anchored to a row in this table via the PROGRAM_ID column.

From a dimensional modeling perspective, the metadata's heuristic Data Vault classification identifies this object as a hub. This is a reasonable modeling suggestion: PROGRAM_ID is the stable business key issued once per program, and the table functions as the central anchor from which numerous satellite and link relationships radiate. Surrounding attribute groups (dates, statuses, questionnaire display flags, fee-waiver flags) would map naturally to satellites, while tables such as PV_PG_ELIG_PROGRAMS and PV_PG_ENRL_CHANGE_RULES behave as links.

Key Information Stored

The table is defined with 52 columns. The most operationally significant are:

• PROGRAM_ID — the surrogate primary key, enforced by PV_PARTNER_PROGRAMS_B_PK and the unique index PV_PARTNER_PROGRAM_B_U1. It is the singular identifier propagated to all dependent partner management tables.
• PROCESS_RULE_ID — the second business-key candidate, enforced by unique index PV_PARTNER_PROGRAM_B_U2, linking the program to its lifecycle processing rules in PV_PROCESS_RULES_B.
• PROGRAM_TYPE_ID — foreign key to PV_PARTNER_PROGRAM_TYPE_B, classifying the program (for example, membership, certification, or benefits-oriented).
• PROGRAM_PARENT_ID — a self-referencing foreign key that supports hierarchical or nested program structures.
• PROGRAM_LEVEL_CODE and PROGRAM_STATUS_CODE — define the program's tier level and its lifecycle state (active, inactive, or obsolete).
• PROGRAM_START_DATE and PROGRAM_END_DATE — the effective window during which the program may be joined or administered.
• PROGRAM_OWNER_RESOURCE_ID — identifies the internal resource accountable for program administration.
• MEMBERSHIP_VALID_PERIOD and MEMBERSHIP_PERIOD_UNIT — express the default duration of a partner's membership and the unit of measure for that duration.
• ENABLED_FLAG, NO_FEE_FLAG, and WAIVE_SUBSIDIARY_FEE_FLAG — control whether the program is enabled and how membership fees are treated for it and its subsidiaries.
• ALLOW_ENRL_WOUT_CHKLST_FLAG and ALLOW_ENRL_UNTIL_DATE — govern whether enrollment may bypass a checklist and the cutoff date for enrollment.
• PREREQ_PROCESS_RULE_ID and CITEM_VERSION_ID — link the program to any prerequisite process rule and to a channel item version.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the Oracle Applications framework.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — the standard WHO audit columns, plus the fifteen ATTRIBUTE descriptive flexfield columns.

Common Use Cases and Queries

The table is the primary driver for partner program configuration and reporting. Typical patterns include:

• Listing all currently active programs with their type, effective dates, and fee configuration:
  SELECT p.program_id, t.program_type, p.program_status_code, p.program_start_date, p.program_end_date, p.no_fee_flag FROM pv.pv_partner_program_b p, pv.pv_partner_program_type_b t WHERE p.program_type_id = t.program_type_id AND p.enabled_flag = 'Y' AND p.program_status_code = 'ACTIVE';
• Resolving the translated name and description of a program by joining to PV_PARTNER_PROGRAM_TL on PROGRAM_ID.
• Auditing membership duration policy by extracting MEMBERSHIP_VALID_PERIOD and MEMBERSHIP_PERIOD_UNIT.
• Walking the program hierarchy using a self-join on PROGRAM_PARENT_ID to produce a recursive indented listing of parent and child programs.
• Measuring program adoption by counting rows in PV_PG_MEMBERSHIPS grouped by PROGRAM_ID.
• Identifying programs whose PROGRAM_END_DATE falls within a given window for renewal planning.

Related Objects

The table participates in an extensive foreign key network. The most significant relationships are:

• PV_PARTNER_PROGRAM_TL — the translation table joined on PROGRAM_ID, supplying language-specific names and descriptions.
• PV_PARTNER_PROGRAM_TYPE_B — referenced via PROGRAM_TYPE_ID, providing program classifications.
• PV_PROCESS_RULES_B — referenced twice, through PROCESS_RULE_ID and PREREQ_PROCESS_RULE_ID, for lifecycle and prerequisite processing.
• PV_PG_MEMBERSHIPS and PV_PG_ENRL_REQUESTS — reference PROGRAM_ID and hold the enrollment and membership transactions.
• PV_PG_ELIG_PROGRAMS and PV_PG_ENRL_CHANGE_RULES — express eligibility and change-from/change-to transitions (CHANGE_FROM_PROGRAM_ID, CHANGE_TO_PROGRAM_ID).
• PV_PROGRAM_BENEFITS and PV_PROGRAM_CONTRACTS — attach benefits and contractual terms via PROGRAM_ID.
• PV_PROGRAM_PAYMENT_MODE — records payment mode configuration per program.
• PV_GE_PTNR_RESPS and PV_GE_RESP_MAP_RULES — map organizational responsibilities and status transitions to programs.
• PV_GE_CHKLST_ITEMS_B, PV_GE_QSNR_ELEMENTS_B, and PV_GE_NOTIF_RULES_B — reference programs polymorphically through USED_BY_ENTITY_ID and NOTIF_FOR_ENTITY_ID.
• PV_GE_HISTORY_LOG_B — tracks changes to programs through HISTORY_FOR_ENTITY_ID.