Search Results l_create




Overview
Explore in AI Chat

Overview

PV_PRGM_PMT_MODE_PVT is a private (PVT-classified) PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, filed under the source header pvxvppmb.pls. It encapsulates the business logic governing Program Payment Modes used within Oracle Procurement Contracts. A program payment mode associates a payment method code with a specific contract program and geography hierarchy, allowing procurement organizations to control how and where payments may be made on a given program. The package was originally created in April 2002 and carries a revision history reflecting bug fixes in 2003 (bug 2830585) and 2005 (bug 4572286), including the addition and later removal of a Copy_Prgm_Pmt_Mode routine for program-copy functionality. The "PVT" classification indicates that the package is not intended for direct customer invocation; it is consumed internally by the PL/SQL APIs and forms that manage procurement contract setup. The package is referenced by one other package, confirming its role as a subordinate implementation layer rather than a top-level public API.

Key Procedures and Functions

The package exposes eight documented procedures that together form a complete create-read-update-delete lifecycle, with supporting validation and concurrency-control routines:

  • CREATE_PRGM_PMT_MODE — Inserts a new program payment mode record, establishing the association between a program, geography hierarchy, and payment method code.
  • UPDATE_PRGM_PMT_MODE — Modifies an existing program payment mode record, typically to change the associated payment method or descriptive attributes.
  • DELETE_PRGM_PMT_MODE — Removes a program payment mode record from the underlying tables.
  • LOCK_PRGM_PMT_MODE — Acquires a row-level lock on the specified record to support optimistic concurrency control during multi-step transactions.
  • VALIDATE_PRGM_PMT_MODE — Performs business-rule validation of a payment mode record prior to persistence.
  • CHECK_ITEMS — An internal validation helper that verifies required attributes and referential conditions.
  • VALIDATE_REC — Validates an individual record, likely invoked during the create or update flow.
  • COMPLETE_REC — Finalizes a record by populating WHO columns and other standard EBS audit attributes before commit.

A helper procedure, Get_Pmnt_Mode_Desc, is additionally visible in the source excerpt; it derives a payment mode description from OE lookups and the payment mode table for a supplied payment method code, program ID, and geography hierarchy ID. This routine was specifically corrected under bug fix 2830585.

Tables Accessed

The package interacts with two application tables through APPS synonyms:

  • PV_PROGRAM_PAYMENT_MODE — The primary base table holding program payment mode definitions. All create, update, delete, lock, and query operations target this table.
  • PV_PROGRAM_PAYMENT_MODE_S — The corresponding translation (TL) table storing language-specific descriptive columns, written or maintained alongside the base record.
  • DUAL — Used for singleton SELECT operations, such as retrieving lookup meanings or sequence-derived values.

The description lookup additionally joins to OE_LOOKUPS to translate the payment method code into a user-facing meaning.

Usage Notes

Because PV_PRGM_PMT_MODE_PVT is categorized as a private API, it should not be called directly from custom code. In standard EBS 12.1.1 and 12.2.2 deployments, these procedures are invoked by the Procurement Contracts setup forms and by the public wrapper packages that orchestrate program payment mode configuration. Customers extending or integrating with this functionality are advised to use the corresponding public API rather than the PVT layer, as the private procedures may change between releases without notice. The l_create identifier referenced in user searches corresponds to the internal local variable naming convention used inside the create routine rather than a standalone callable interface.