Search Results ap_te_eis_pkg

Overview

AP_TE_EIS_PKG is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite Payables. The package name incorporates the "EIS" designation, which in the Oracle EBS Payables and Internet Expenses domain refers to the Expense Information System layer that supplies aggregated spend and transaction metrics for presentation in Oracle Daily Business Intelligence, expense dashboards, and related reporting views. Its documented purpose is to compute summary-level figures across invoices, invoice distributions, and payments, returning single scalar values such as totals, counts, and averages. In effect, AP_TE_EIS_PKG functions as a calculation engine for the Payables expense reporting stack rather than as a transactional API: it does not create, update, or validate Payables documents, and it is not registered as a public API for external integration. The ETRM metadata classifies it as API classification OTHER, confirming that it is an internal support package rather than a documented inbound or outbound interface.

Key Procedures and Functions

The ETRM documentation records nine procedures and functions within the package body, all of which are read-only aggregation routines. Their names describe their intent directly:

• GETINVOICETOTAL — returns the summed monetary value of invoices, typically scoped by an organizational or date predicate supplied by the caller.
• GETINVOICECOUNT — returns the number of qualifying invoices matching the supplied criteria.
• GETINVOICEAVERAGE — returns the mean invoice value derived from the invoice population defined by the caller.
• GETPAYMENTTOTAL — returns the summed value of payments recorded against Payables documents.
• GETPAYMENTCOUNT — returns the count of qualifying payment records.
• GETPAYMENTAVERAGE — returns the average payment amount for the qualifying payment set.
• GETPAYABLESINVOICECOUNT — returns a count restricted to standard Payables invoices, distinguishing them within the broader invoice population.
• GETPROJECTINVOICECOUNT — returns a count of invoices associated with project-related accounting, supporting project expenditure reporting.
• GETSELFSERVEINVOICECOUNT — returns a count of self-service invoices, the category originating from supplier self-service and Internet Expenses entry channels.

The documented parameter lists are not exposed in the ETRM record; callers should inspect the package specification via ALL_ARGUMENTS or the AP_TE_EIS_PKG spec source rather than assume a signature. All nine routines follow the same pattern: accept filtering criteria, execute a single aggregate query, and return the result.

Tables Accessed

The package is documented as referencing three Payables base tables through APPS synonyms:

• AP_INVOICES — the invoice header table, supplying invoice amounts, invoice types, dates, and organizational identifiers used by the invoice total, count, and average routines and by the three specialized count routines.
• AP_INVOICE_DISTRIBUTIONS — the invoice line distribution table, used where counting or aggregating must reflect distribution-level rather than header-level data.
• AP_INVOICE_PAYMENTS — the invoice-to-payment link table, providing the payment facts required by GETPAYMENTTOTAL, GETPAYMENTCOUNT, and GETPAYMENTAVERAGE.

Because every documented routine is an aggregate function, the access pattern is read-only SELECT with GROUP BY aggregation against these tables. No INSERT, UPDATE, or DELETE operations are implied by the metadata.

Usage Notes

ETRM records that AP_TE_EIS_PKG is not referenced by any other database object. This is significant: no view, trigger, or peer package depends on it directly, which indicates the package is invoked dynamically — most likely from Oracle Daily Business Intelligence collection programs, from Payables or Expenses dashboard regions, or from custom reporting code that calls the package explicitly. The nine routines are appropriate for embedding in custom BI Publisher reports, OAF pages, or concurrent programs that require pre-aggregated Payables metrics without issuing ad hoc SQL. Because the package reads current Payables data at call time, results reflect the transaction state as of execution and are not cached. The same package body is present in both 12.1.1 and 12.2.2, and the documented dependency set is identical across those releases. Developers extending or diagnosing this package should treat it as an internal, unsupported implementation detail of the expense reporting layer and avoid depending on it from custom code where a supported view or public API is available.