Search Results delete_prgm_pmt_mode

Overview

PV_PRGM_PMT_MODE_PVT is a private PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It forms part of the Oracle Procurement (PV) module and manages the program payment mode records that govern the association between a program, a geographic hierarchy, and the mode of payment permitted for that combination. In the context of Oracle EBS 12.1.1 and 12.2.2, this package encapsulates the low-level data manipulation logic for the PV_PROGRAM_PAYMENT_MODE entity, providing a controlled API surface used internally by the PV module rather than by external callers. The package header carries a header revision of 120.0, dated 27-MAY-2005, with creation attributed to Peter Nixon on 26-APR-2002 and a subsequent modification on 30-APR-2002, indicating an origin in the earlier releases that has persisted through the 12.x code line. Its classification as a PVT (private) package signals that it is not intended for direct invocation by customers or third-party extensions; instead it is invoked by public wrapper APIs or forms that require the underlying transactional behavior.

Key Procedures and Functions

The package exposes eight documented procedures and functions that together implement the standard create, update, validate, and delete lifecycle for a program payment mode record.

• CREATE_PRGM_PMT_MODE — Inserts a new program payment mode record, populating the program, geographic hierarchy, and payment mode attributes along with standard WHO columns.
• UPDATE_PRGM_PMT_MODE — Modifies an existing program payment mode record, applying changed attribute values while preserving the audit trail.
• DELETE_PRGM_PMT_MODE — Removes a program payment mode record. This procedure is the specific object referenced by the search term "delete_prgm_pmt_mode" and is the standard entry point for logically or physically deleting a program payment mode row.
• LOCK_PRGM_PMT_MODE — Obtains a row-level lock on the target record, typically used at the start of a transaction to prevent concurrent modification before an update or delete.
• VALIDATE_PRGM_PMT_MODE — Performs entity-level validation on the program payment mode record, checking required attributes and business rules before persistence.
• CHECK_ITEMS — A helper routine that examines the individual attributes of the record to determine which items are present, missing, or changed.
• VALIDATE_REC — Validates the complete record structure, complementing the entity-level validation with record-level checks.
• COMPLETE_REC — Populates any omitted or defaulted attributes on the record and finalizes it prior to the insert or update operation.

Tables Accessed

The package operates against three documented data sources. PV_PROGRAM_PAYMENT_MODE is the primary transactional table holding one row per program, geographic hierarchy, and payment mode combination. PV_PROGRAM_PAYMENT_MODE_S is the corresponding MLS (Multi-Language Support) shadow table that stores the translated or language-specific descriptive columns for the same entity. DUAL is referenced for standard scalar operations such as retrieving sequence values or evaluating simple expressions. The package reads and writes to the base table and its MLS companion, while DUAL is used only for non-transactional value retrieval.

Usage Notes

Because PV_PRGM_PMT_MODE_PVT is a private package, it is not exposed as a public API. In Oracle EBS 12.1.1 and 12.2.2, it is invoked indirectly, most commonly from Oracle Forms-based setup screens in the Procurement module where administrators define program payment modes, and from whichever public API or concurrent program layer wraps the private package. The ETRM metadata indicates that the package is referenced by one other package, confirming this wrapper relationship. Developers performing data fixes or custom extensions should generally call the public wrapper rather than the private package directly, since invoking the private package bypasses the layering and support guarantees of the public interface. When the private package is called in custom code, the LOCK_PRGM_PMT_MODE, VALIDATE_PRGM_PMT_MODE, and COMPLETE_REC steps should be sequenced before CREATE or UPDATE to preserve the integrity checks the module relies upon. The DELETE_PRGM_PMT_MODE procedure likewise expects the record to be locked and validated before deletion.