Search Results delete_rows

Overview

APPS.PAY_DBITL_UPDATE_ERRORS_PKG is a PL/SQL package body shipped with Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 under the APPS schema. The package provides the core data-access layer for the PAY_DBITL_UPDATE_ERRORS table, which stores error records generated during the processing of external bank debit instructions. The "DBITL" component of the name refers to the debit instruction functionality in Oracle Payables and Oracle Payments, while "UPDATE_ERRORS" identifies the table as a repository for errors encountered when update operations are attempted against those instructions. The package encapsulates insert, delete, and fetch logic so that concurrent programs, forms, and dependent PL/SQL units do not manipulate the error table directly. The header comment indicates a copyright of 2006 with a version identifier of 120.1, reflecting the initial 12.x lineage and the "noship" status typical of an internal, non-shipped-in-the-UI utility package.

Key Procedures and Functions

• INSERT_ROW — Two overloaded forms exist. The first accepts user name, user entity ID, translated name, and message text, then internally delegates to the second form. The second form performs the actual insert into PAY_DBITL_UPDATE_ERRORS and returns the new ROWID through an OUT NOCOPY parameter. This overload pattern allows callers that do not need the ROWID to use the simpler signature while preserving the ability to retrieve it when required by downstream processing.
• DELETE_ROWS — Two overloaded forms. The first deletes a single logical error record keyed by user name, user entity ID, and translated name. The second accepts a DBMS_SQL.VARCHAR2S associative array of ROWIDs and performs a bulk FORALL delete. The array-based form returns immediately if the collection is empty, and iterates from index 1 to COUNT, which is the standard interface expected by Oracle Forms block-level delete processing.
• DELETE_ROW — Deletes a single row identified by its ROWID. This is the primitive used when the caller already holds a specific ROWID, for example from a prior INSERT_ROW call or a query.
• FETCH_ALL_ROWS — Retrieves the full set of error rows for presentation or downstream reconciliation. It is typically wired to a Forms block or a concurrent program query.

Tables Accessed

• PAY_DBITL_UPDATE_ERRORS — The primary and only application table touched. It is inserted into by INSERT_ROW, deleted from by both DELETE_ROWS overloads and DELETE_ROW, and queried by FETCH_ALL_ROWS. Its columns include USER_NAME, USER_ENTITY_ID, TRANSLATED_NAME, and MESSAGE_TEXT, which together identify the offending user entity and describe the error encountered.
• DBMS_SQL — Referenced only as the source of the VARCHAR2S type used for the ROWID array parameter in the bulk delete. No dynamic SQL execution against DBMS_SQL is implied by the documented code.
• PLITBLM — Referenced via an APPS synonym; this is the standard Forms/PL/SQL table-of-rows mechanism used by Oracle Forms to pass ROWID collections to server-side packages.

Usage Notes

The package is referenced by two other packages in the EBS schema, indicating that it sits beneath an orchestration layer that detects and reports debit instruction update failures. It is most commonly invoked from Oracle Forms when a user reviews or clears error rows, which explains the FORALL/VARCHAR2S delete signature matching Forms block semantics. It may also be called from concurrent programs that reconcile bank debit files. Because it is an APPS-owned, "noship" utility, customers should not modify it; extensions should be built as wrapper packages. Direct DML against PAY_DBITL_UPDATE_ERRORS is discouraged, since ROWID-based deletes depend on the package's precise handling of the returning clause.