Search Results validate_prgm_pmt_mode

Overview

PV_PRGM_PMT_MODE_PVT_W is the published wrapper layer for the program payment mode private API in Oracle EBS. It belongs to the Oracle Program Management (PV) product family and is owned by the APPS schema. The package exposes a PL/SQL interface for maintaining program payment mode records, which define the payment instruments and associated attributes used when funds are disbursed against a program or award. In EBS 12.1.1 and 12.2.2 the package is registered as API classification OTHER, meaning it is invoked as a supporting API rather than as a fully published business object interface, although its procedures follow the standard EBS API conventions (p_api_version_number, p_init_msg_list, p_commit, p_validation_level, and the x_return_status / x_msg_count / x_msg_data error stack). The "_W" suffix indicates that this is the thin wrapper that converts between the table-based (rosetta) data structures used by the presentation layer and the record types defined in the underlying PV_PRGM_PMT_MODE_PVT package.

Key Procedures and Functions

The package documents eight procedures. The business-facing entry points are:

• CREATE_PRGM_PMT_MODE — Inserts a new program payment mode record. It accepts the standard API control parameters plus the entity attributes and returns the generated program_payment_mode_id.
• UPDATE_PRGM_PMT_MODE — Modifies an existing program payment mode record, using the same attribute set and standard API control parameters.
• VALIDATE_PRGM_PMT_MODE — The validation routine matching the user's search term. It applies entity-level validation rules to the record before it is persisted or accepted, populating the standard message stack on failure.
• CHECK_ITEMS — Performs item-level attribute checking, typically invoked from validation logic to verify required and cross-field conditions.
• VALIDATE_REC — Validates a single record instance held in the internal PL/SQL record structure.
• COMPLETE_REC — Completes or defaults a record prior to insert or update, filling derived attributes.
• ROSETTA_TABLE_COPY_IN_P2 — Copies a set of JTF table parameters (JTF_NUMBER_TABLE, JTF_VARCHAR2_TABLE_100, JTF_DATE_TABLE) into the prgm_pmt_mode_tbl_type structure used by the private package.
• ROSETTA_TABLE_COPY_OUT_P2 — Performs the reverse copy, moving the internal table structure back into the JTF column arrays for return to the caller.

Tables Accessed

The documented table reference for this package is the APPS synonym PLITBLM. This is a generic PL/SQL index-by table storage object used in EBS to hold collection data temporarily; the package does not reference the base program payment mode entity table directly through this synonym. The actual persistent writes and reads against the program payment mode entity are handled by the underlying private package PV_PRGM_PMT_MODE_PVT, which this wrapper delegates to. No other tables are documented as referenced by this object.

Usage Notes

PV_PRGM_PMT_MODE_PVT_W is not referenced by any other documented package, so it is normally invoked directly by the UI layer. In practice, the rosetta copy-in and copy-out procedures are used by Oracle Forms and OAF-based pages that pass multi-row data as JTF table parameters into and out of PL/SQL, while the create, update, and validate procedures are called from form triggers, custom concurrent programs, or custom PL/SQL that needs to maintain program payment modes programmatically. Callers should always inspect x_return_status and check x_msg_count / x_msg_data after each call, and should supply the correct p_api_version_number. Because the package is classified OTHER rather than as a public API, customizations should prefer supported public interfaces where available and treat this wrapper as an internal integration point subject to change across releases.