Results for “ap_ac_table_handler_pkg”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.AP_AC_TABLE_HANDLER_PKG is a PL/SQL package in the Oracle E-Business Suite Payables (AP) module. Its name derives from its role as a handler for the AP_AC (Accounts Payable / Automatic Clearing or payment check-related) tables. The package provides a controlled, programmatic interface for performing Data Manipulation Language (DML) operations against core Payables payment tables, specifically AP_CHECKS, AP_CHECKS_ALL, and CE_BANK_ACCOUNTS. Rather than allowing direct inserts, updates, and deletes against these sensitive tables, Oracle routes such operations through this handler package to centralize validation, maintain data integrity, and enforce consistent business rules.

The package is classified as API type OTHER in the ETRM 12.2.2 metadata. It is owned by the APPS schema and is currently in VALID status. It forms part of the underlying infrastructure that supports higher-level Payables payment APIs, notably AP_CHECKS_PKG, AP_PAYMENT_PUBLIC_PKG, and JL_AR_AP_WITHHOLDING_PKG, all of which reference it. Its presence across both the 12.1.1 and 12.2.2 releases reflects its role as a stable, low-level utility within the Payables payment processing stack.

Key Procedures and Functions

The package exposes four documented procedures, all focused on managing rows and monetary values within the payment tables it governs:

• INSERT_ROW — Handles insertion of new rows into the associated AP_AC tables. This procedure centralizes row creation so that any required defaulting, key population, or validation occurs before the record is physically written.
• UPDATE_ROW — Performs updates to existing rows. It is the controlled path for modifying existing payment records, ensuring that column-level changes are applied consistently with the package's business rules.
• DELETE_ROW — Removes rows from the associated tables. Centralizing deletion helps prevent orphaned or inconsistent payment data.
• UPDATE_AMOUNTS — Specializes in modifying monetary amount fields. Because payment amounts are financially sensitive, this dedicated procedure isolates amount-related updates so they can be validated and applied independently of general row updates.

The ETRM metadata documents these procedures by name without exposing parameter signatures; parameter lists should be obtained from the package specification in the database rather than assumed.

Tables Accessed

Through APPS synonyms, the package references the following documented tables:

• AP_CHECKS — The core Payables payments table, storing payment records across business groups. The handler manages row-level DML here.
• AP_CHECKS_ALL — The multi-organization (partitioned by org) view or table counterpart of AP_CHECKS, allowing the handler to operate in a specific operating unit context.
• CE_BANK_ACCOUNTS — The Cash Management bank accounts table, referenced to resolve or validate the disbursement bank account associated with a payment.

Usage Notes

This package is not intended for direct invocation by end users. It is a low-level handler invoked indirectly by higher-level Payables APIs. As documented, AP_CHECKS_PKG, AP_PAYMENT_PUBLIC_PKG, and JL_AR_AP_WITHHOLDING_PKG all reference AP_AC_TABLE_HANDLER_PKG, meaning standard payment creation, update, and withholding logic flows through it. It may also be called from Payables forms, concurrent programs (such as payment processing and check printing), and custom extensions that need to manipulate AP_CHECKS or AP_CHECKS_ALL rows. Custom code should invoke the higher-level public APIs wherever possible rather than calling this handler directly, since the handler assumes the calling layer has already performed full business validation. As with all APPS packages, any custom call must respect the standard initialization and multi-org setup conventions of the environment.