Search Results ap_drilldown_pub_pkg




Overview
Explore in AI Chat

Overview

APPS.AP_DRILLDOWN_PUB_PKG is a public PL/SQL package in the Oracle E-Business Suite Payables (AP) module. In Oracle EBS 12.1.1 and 12.2.2, its role is to expose "drilldown" functionality that allows users to navigate from summarized Payables accounting information back to the underlying source transactions, and to retrieve the online accounting detail for invoices and payments. The package is classified as an API of type OTHER in the ETRM 12.2.2 metadata, sits under the APPS schema, and holds a VALID status. Its public nature means it is intended to be callable from outside the AP module — for example, from Oracle General Ledger, Subledger Accounting (SLA/XLA), or from custom integrations — rather than being an internal helper used only within AP.

Key Procedures and Functions

The documented package exposes three procedures/functions:

  • DRILLDOWN — Provides the core drilldown capability, resolving the linkage between a displayed accounting or payment record and its originating Payables transaction so the caller can navigate to source detail.
  • INVOICE_ONLINE_ACCOUNTING — Returns online accounting information associated with an invoice, allowing the caller to view the accounting entries generated for that invoice.
  • PAYMENT_ONLINE_ACCOUNTING — Returns online accounting information associated with a payment, exposing the accounting entries generated for that payment.

The ETRM metadata does not document parameter lists for these procedures, so their exact signatures should be verified against the package specification in the target environment before use.

Tables Accessed

The package references the following tables through APPS synonyms:

Usage Notes

AP_DRILLDOWN_PUB_PKG is typically invoked from Payables and General Ledger forms or from custom code that requires programmatic drilldown or online accounting retrieval. It is not referenced by any other package in the documented metadata, indicating that it is a top-level public entry point rather than a dependency of other APIs. Because its procedures return accounting and drilldown data, callers should be prepared to supply the relevant invoice or payment identifier and ledger context. When integrating, always confirm the actual parameter list from the package specification in the specific EBS release, as the ETRM documentation does not enumerate arguments. Use of the FND logging tables also implies that diagnostic behavior can be controlled through standard FND logging profiles.