Search Results p_set_of_books_id

Overview

APPS.AP_TE_EIS_PKG is a PL/SQL package that belongs to the Oracle Payables (AP) module and is classified under the EIS (Executive Information System / business intelligence) family of database objects. Its primary business function is to supply aggregated payables metrics — invoice totals, invoice counts, invoice averages, and payment statistics — for reporting and dashboard-style consumption. The package is declared with AUTHID CURRENT_USER, meaning its SQL statements execute with the privileges of the invoking user rather than the defining user, which is consistent with a utility or reporting package designed to be called from a variety of runtime contexts. The header comment ($Header: apteeiss.pls 120.2 2004/10/25 ...) indicates a long-lived, stable object that has been part of the Payables schema since at least Release 11i and remains documented in the ETRM repository for EBS 12.1.1 and 12.2.2. The package does not maintain persistent state; it operates as a read-only aggregation layer over core Payables transaction tables. There is no signature for Setup or initialization APIs, confirming its role strictly as a metrics provider rather than a transaction-processing API.

Key Procedures and Functions

The package exposes nine public subprograms. Their documented purposes are as follows:

• GetInvoiceTotal — returns the aggregated monetary total of invoices within a supplied date range.
• GetInvoiceCount — returns a count of invoices; the signature includes classification flags for payables, project, and self-service invoice types, allowing a caller to obtain a segmented count.
• GetInvoiceAverage — computes an average invoice value from previously derived total and count inputs, making it a pure calculation helper rather than an independent query.
• GetPaymentTotal — returns the total payment amount for a given ledger (P_Set_Of_Books_Id) across a date range.
• GetPaymentCount — returns the number of payments for a given ledger and date range.
• GetPaymentAverage — returns the average payment amount for a given ledger and date range.
• GetPayablesInvoiceCount — returns the count of standard Payables invoices for a given ledger and date range.
• GetProjectInvoiceCount — returns the count of project-related invoices for a given ledger and date range.
• GetSelfServeInvoiceCount — returns the count of self-service (iSupplier/Web) invoices for a given ledger and date range.

Notably, six of the nine procedures accept P_Set_Of_Books_Id as an IN VARCHAR2 parameter, which is the direct link to the user’s search term. This ledger identifier scopes every payment-related and invoice-category metric to a single accounting set of books (or ledger), and it is passed as a string rather than a number to accommodate the internal conventions of the EIS reporting framework.

Tables Accessed

The documented tables accessed via APPS synonyms are:

• AP_INVOICES — the invoice header table, used to derive invoice totals, counts, and category breakdowns.
• AP_INVOICE_DISTRIBUTIONS — the invoice distribution lines, used where accounting-level or project-related aggregation is required, particularly for project invoice counts.
• AP_INVOICE_PAYMENTS — the invoice-to-payment association table, used to compute payment totals, counts, and averages.

All access is read-only. No dml_operations against these tables are attributed to the package.

Usage Notes

Because AP_TE_EIS_PKG is referenced by zero other documented packages, it is not a dependency of standard Payables transaction flows. It is designed to be invoked directly by reporting front-ends — Oracle EIS/Discoverer worksheets, custom Oracle Forms, or concurrent programs — that need pre-aggregated payables figures. Callers typically supply a P_Set_Of_Books_Id to restrict results to a single ledger, along with start and end dates. The IN OUT NOCOPY NUMBER result parameter is consistent with a pattern where the caller initializes the variable and the procedure overwrites it, often through a small PL/SQL wrapper in a report or form trigger. Since the package relies on the P_Set_Of_Books_Id convention rather than the newer ledger/ledger-set identifiers, sites upgrading from 11i should verify that their calling code passes the correct set-of-books value for 12.1.1 and 12.2.2 environments.