Search Results pv_program_payment_mode_u1

Overview

PV.PV_PROGRAM_PAYMENT_MODE is a transactional configuration table in the Oracle EBS Channel Revenue Management (formerly Trade Management) application, owned by the PV schema. It stores, at the intersection of a partner program and a geographic hierarchy node, the payment modes and payment mode types that are valid for that combination. In practice, the table answers the question: for a given program running in a given country or territory, which disbursement mechanisms may be used when a claim is settled. It therefore acts as a validation and defaulting source during claim creation, accrual processing, and settlement in the trade management and deduction lifecycle.

From a heuristic Data Vault perspective, the mined foreign key structure suggests a satellite-leaning classification. The row is keyed by its own surrogate identifier and carries descriptive attributes (mode of payment, mode type) plus a foreign key to a partner program, which is typical of a satellite attached to a program hub and qualified by a geography dimension. This is a modeling suggestion only; the object is a classic third-normal-form EBS intersection table rather than a Data Vault artifact.

Key Information Stored

• PROGRAM_PAYMENT_MODE_ID — surrogate primary key, enforced by PV_PROGRAM_PAYMENT_MODE_PK and by the unique index PV_PROGRAM_PAYMENT_MODE_U1. The unique index is the documented business-key candidate, though it is technically surrogate and carries no business meaning.
• PROGRAM_ID — foreign key to PV.PV_PARTNER_PROGRAM_B, identifying the partner program whose payment modes are being defined. Together with GEO_HIERARCHY_ID this forms the meaningful access path, supported by non-unique index PV_PROGRAM_PAYMENT_MODE_N1.
• GEO_HIERARCHY_ID — foreign key to XNP_GEO_HIERARCHY, identifying the geography node (typically a country) to which the payment mode applies.
• MODE_OF_PAYMENT — the payment mode value, held as a VARCHAR2(15) code (for example a check, credit, or offset style mechanism).
• MODE_TYPE — a VARCHAR2(15) classifier that categorises the payment mode, allowing multiple related modes to be grouped or filtered during claim processing.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting Multi-Org / security group isolation of the configuration rows.
• OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS WHO columns providing optimistic locking, audit trail, and the concurrent-program context that created or amended each row.

Common Use Cases and Queries

The dominant use case is determining the valid payment modes for a program in a specific country, either for validation in a form or for reporting on settlement configuration. A typical lookup joins the table to the geography hierarchy and the program base table:

• List payment modes for a program: SELECT MODE_OF_PAYMENT, MODE_TYPE FROM PV.PV_PROGRAM_PAYMENT_MODE WHERE PROGRAM_ID = :p_program_id;
• Restrict to a country by joining XNP_GEO_HIERARCHY on GEO_HIERARCHY_ID and filtering on the territory or country name.
• Identify programs configured for a payment mode: filter on MODE_OF_PAYMENT to find all programs using, for example, a particular credit mechanism, useful for impact analysis before a mode is retired.
• Audit and reconciliation reporting: query by LAST_UPDATE_DATE and LAST_UPDATED_BY to review configuration changes over a period, or compare MODE_OF_PAYMENT against MODE_TYPE to detect incomplete setup.
• Security-scoped extracts: add SECURITY_GROUP_ID predicates when extracting configuration for a specific operating unit or security group.

Related Objects

• PV.PV_PARTNER_PROGRAM_B — joined on PROGRAM_ID; the program definition that the payment mode configuration qualifies.
• XNP_GEO_HIERARCHY — joined on GEO_HIERARCHY_ID; provides the country or territory context for each payment mode row.
• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID; governs row visibility across security groups.
• PV.PV_PROGRAM_PAYMENT_MODE# — the runtime/policy variant of this table referenced by the base object in the dependency listing.
• Claim and settlement tables in the PV schema (for example claim line and settlement structures) that consume MODE_OF_PAYMENT as a validation and defaulting source during trade management processing.

No database object is referenced by PV_PROGRAM_PAYMENT_MODE beyond the foreign keys documented above, and it is referenced only within the PV application schema.