Search Results ap_pbatch_sets_s

Overview

AP_PBATCH_SET_HEADER_PKG is an Oracle Application Object Library style PL/SQL package in the APPS schema that encapsulates the core Data Manipulation Language operations against the AP_PBATCH_SETS table, which stores Payment Batch Set definitions used by Oracle Payables. In Oracle EBS 12.1.1 and 12.2.2, the package provides a single, controlled interface for inserting, locking, updating, and deleting payment batch set header records, insulating callers such as Oracle Forms or concurrent programs from direct table access. The documented header comment ($Header: apbsethb.pls 120.2 2004/10/27) confirms the code lineage dates to the 11i era and was carried forward into Release 12; the naming convention and structure match the standard Oracle "table handler" pattern generated for base tables. The object is classified as an "OTHER" API rather than a public or private Oracle-provided API, indicating it is an internal implementation artifact supporting the Payables payment batch set form, not a formally supported integration API.

Key Procedures and Functions

• INSERT_ROW — Inserts a new payment batch set header into AP_PBATCH_SETS. It obtains a new primary key by selecting the sequence AP_PBATCH_SETS_S.NEXTVAL, performs the insert, then re-queries the inserted row by ROWID (returned through an OUT parameter) so the caller receives the canonical row handle. The procedure raises NO_DATA_FOUND if the ROWID fetch fails.
• LOCK_ROW — Acquires a row-level lock on an existing payment batch set so the calling form can safely read and subsequently update it without concurrent modification.
• UPDATE_ROW — Applies changes to an existing payment batch set header record, including standard WHO columns such as LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.
• DELETE_ROW — Removes a payment batch set header record from AP_PBATCH_SETS.

All four procedures follow the Oracle table-handler convention, accepting and returning a ROWID for the affected record and propagating errors through FND_MESSAGE using the SQLAP application's AP_DEBUG message when the failure is not the internal exception number -20001.

Tables Accessed

• AP_PBATCH_SETS — The primary base table. It holds the payment batch set header rows, keyed by BATCH_SET_ID and populated with BATCH_SET_NAME, INACTIVE_DATE, and the standard WHO audit columns. All four procedures read or write this table.
• AP_PBATCH_SETS_S — The database sequence used exclusively by INSERT_ROW to generate the next BATCH_SET_ID primary key value.

Usage Notes

This package is invoked indirectly by the Oracle Payables Payment Batch Set form and related internal processing when users create, modify, or delete payment batch sets. The ETRM metadata records zero other packages referencing it, confirming it is a leaf-level table handler rather than a shared utility. The routine performs no business validation—it assumes the caller has already applied validation rules through the corresponding form or higher-level API. Because it is classified as a non-public internal object, custom code should not depend on its signature without verifying it against the target patch level, since Oracle may alter undocumented internals across Release 12 updates. The embedded debug_info variable, assigned descriptive literals before each significant step, provides a diagnostic trail surfaced through FND_MESSAGE when errors occur, enabling support analysts to pinpoint the failing operation from the CALLING_SEQUENCE token passed by the caller.