Search Results ap_dbi_pkg




Overview
Explore in AI Chat

Overview

APPS.AP_DBI_PKG is a PL/SQL package in Oracle E-Business Suite that supports the Payables "Daily Business Intelligence" (DBI) reporting infrastructure. Its principal role is to maintain the pre-aggregated DBI summary tables that underlie the Payables DBI dashboards and related analytical reporting, rather than to perform transactional processing of invoices or payments. The package is defined with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling user and resolves unqualified object references through that user's schema, a convention typical of packages that operate on APPS synonyms while permitting controlled invocation contexts. The package header carries a versioning header dated 2005, indicating it belongs to the long-standing DBI subsystem introduced in the 11i lineage and carried forward into Release 12.1.1 and 12.2.2. It is a low-level utility package: it is referenced by 24 other packages and is not part of the public, documented Oracle Payables API set, so it should be treated as internal infrastructure.

Key Procedures and Functions

Two procedures are documented for this package:

  • MAINTAIN_DBI_SUMMARY — The general-purpose maintenance routine for DBI summary data. It accepts a target table name, an operation indicator, one or two scalar key values, and an optional list of key values passed as a PL/SQL associative-array type (r_dbi_key_value_arr, a table of NUMBER(15)), together with a calling-sequence parameter used by Oracle's standard error-handling and debugging convention. The combination of table name, operation code, and key list allows a single generic entry point to insert, update, or delete rows in the appropriate DBI summary table for a given dimension key. This design is what makes the package reusable across many DBI subject areas and explains its wide dependency footprint.
  • INSERT_PAYMENT_CONFIRM_DBI — A specialized routine that records payment-confirmation data into the DBI structures. It receives the check run name, the base currency code, a key table name, a calling sequence, and a debug-mode flag defaulting to 'N'. This procedure supports the payment confirmation flow, ensuring that confirmed payment information is reflected in the DBI summaries used for cash and payment analysis.

Parameter lists are intentionally not reproduced here beyond what the metadata documents; callers should not construct invocations without reference to the shipped source.

Tables Accessed

The package accesses the following objects through APPS synonyms:

  • AP_CHECKS — payment documents, providing payment amounts, dates, and currency for summary aggregation.
  • AP_INVOICE_PAYMENTS and AP_PAYMENT_SCHEDULES — link invoices to their payments and scheduled amounts, supporting payables and cash summaries.
  • AP_INVOICE_DISTRIBUTIONS — distribution lines used for spend and accounting-dimension aggregation.
  • AP_SELECTED_INVOICES — the invoice selection set associated with a payment batch or check run.
  • AP_DBI_LOG — the DBI logging table, used to record processing activity, errors, and diagnostics.
  • PLITBLM — a generic Oracle Applications PL/SQL index-by table type used to pass collections such as the key-value array between program units.

Usage Notes

AP_DBI_PKG is not intended for direct invocation from Oracle Forms or from customer-written concurrent programs. It is invoked internally by the Payables DBI collection and refresh processes, and by the 24 dependent packages that consume its maintenance routines. In Release 12.1.1 and 12.2.2 the DBI architecture is largely subsumed by the Oracle Business Intelligence Applications and the Subledger Accounting extract flows, but the package and its summary tables remain present for backward compatibility. Developers investigating DBI discrepancies, or diagnosing ORA- errors during payment confirmation and DBI refresh, may find AP_DBI_LOG and this package relevant. Any custom code that calls it should qualify all objects with APPS, respect the calling-sequence parameter convention, and treat the package as unsupported internal API subject to change between patch levels.