Search Results pv_program_payment_mode




Overview
Explore in AI Chat

Overview

The PV_PROGRAM_PAYMENT_MODE table resides in the PV (Partner Management) schema and stores the payment mode configuration defined against a partner program. In Oracle EBS Release 12.1.1 and 12.2.2, Partner Management supports channel and partner programs in which compensation, rebates, and settlement terms are governed by rules attached to the program itself. PV_PROGRAM_PAYMENT_MODE is the child entity that records, per program, which mode of payment applies, which geographic hierarchy the mode is scoped to, and the classification of that mode. Each row therefore represents a single payment-mode assignment for a given partner program.

From a dimensional modeling perspective, the mined foreign-key structure classifies this object as satellite-leaning. Its business content is descriptive and time-stamped with the standard audit columns, and it hangs off a parent program header, which is the characteristic satellite pattern. Analysts building a Data Vault or star-schema layer should treat PV_PROGRAM_PAYMENT_MODE as a satellite of the PV_PARTNER_PROGRAM_B hub rather than as an independent hub, with PROGRAM_ID acting as the driving foreign key and the audit columns supplying the load metadata.

Key Information Stored

The table is documented with twelve columns. The most operationally significant are:

The surrogate key (PROGRAM_PAYMENT_MODE_ID) should not be confused with the business identity of the record; the meaningful relationship is PROGRAM_ID plus the mode attributes.

Common Use Cases and Queries

Report developers typically join this table to the program header to list payment configurations across partner programs, or to the geography hierarchy to determine which modes apply to a territory. A representative query joins the program header and the geo hierarchy:

  • SELECT ppb.program_id, ppb.program_name, ppm.mode_of_payment, ppm.mode_type, gh.hierarchy_name FROM pv_program_payment_mode ppm, pv_partner_program_b ppb, xnp_geo_hierarchy gh WHERE ppm.program_id = ppb.program_id AND ppm.geo_hierarchy_id = gh.hierarchy_id ORDER BY ppb.program_name, ppm.mode_type;

Common scenarios include auditing which payment modes are active for a program before compensation runs, verifying that a program is not configured with overlapping modes for the same geography, and extracting change history from the audit columns to reconcile mode changes against settlement batches. Security-aware extracts must filter by SECURITY_GROUP_ID to respect user data access.

Related Objects

The following objects are directly related through documented primary and foreign key relationships:

  • PV_PARTNER_PROGRAM_B — parent program header; joined on PV_PROGRAM_PAYMENT_MODE.PROGRAM_ID = PV_PARTNER_PROGRAM_B.PROGRAM_ID.
  • XNP_GEO_HIERARCHY — geography hierarchy lookup; joined on PV_PROGRAM_PAYMENT_MODE.GEO_HIERARCHY_ID = XNP_GEO_HIERARCHY.HIERARCHY_ID.
  • FND_SECURITY_GROUPS — security partitioning reference; joined on PV_PROGRAM_PAYMENT_MODE.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID.
  • PV_PROGRAM_PAYMENT_MODE_PK / PV_PROGRAM_PAYMENT_MODE_U1 — the primary key constraint and unique index over PROGRAM_PAYMENT_MODE_ID.

Additional dependencies are expected through the Partner Management compensation and settlement flows that consume program payment configuration, but the objects listed above are those confirmed by the documented key structure.