Results for “get_distribution_total”

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

Overview

APPS.AP_INVOICES_UTILITY_PKG is a foundational PL/SQL utility package body in the Oracle E-Business Suite Payables (AP) module. Its documented status is VALID, and it is classified under API classification OTHER within the ETRM 12.2.2 metadata. The package aggregates a broad set of reusable helper routines that query and derive invoice-related attributes rather than serving as a single transaction API. It centralizes logic for retrieving descriptive and status information about invoices, prepayments, purchase orders, receipts, holds, approvals, and posting state. Because the package references more than forty underlying tables and views through APPS synonyms, and is itself referenced by 45 other database objects, it functions as a shared service layer that other Payables packages depend upon for consistent information retrieval. Its scope spans supplier invoices, expense reports, prepayment application, self-assessed tax, and payment schedules, reflecting the central role invoicing data plays across the Payables subledger.

Key Procedures and Functions

The metadata documents 62 procedures and functions. Representative members include the following:

• CHECK_UNIQUE and CHECK_UNIQUE_VOUCHER_NUM — validate uniqueness of invoice identifiers, including voucher numbers, supporting duplicate-supplier-invoice prevention.
• GET_PREPAY_NUMBER and GET_PREPAY_DIST_NUMBER — return prepayment and prepayment distribution reference numbers.
• GET_PREPAID_AMOUNT, GET_TOTAL_PREPAYS, and GET_AVAILABLE_PREPAYS — retrieve prepayment balances and available prepaid amounts for application against invoices.
• GET_DISTRIBUTION_TOTAL — computes the total of an invoice's distributions.
• GET_POSTING_STATUS and GET_APPROVAL_STATUS — report the accounting posting state and workflow approval state of an invoice.
• GET_PO_NUMBER, GET_PO_NUMBER_LIST, and GET_RELEASE_NUMBER — resolve purchase order and release references linked to invoice lines and distributions.
• GET_RECEIPT_NUMBER — returns receipt references associated with matched invoice activity.
• GET_AMOUNT_WITHHELD — returns the portion of an invoice subject to withholding.
• GET_NOTES_COUNT, GET_HOLDS_COUNT, and GET_SCHED_HOLDS_COUNT — provide counts of notes and holds at the invoice and schedule level.
• GET_AMOUNT_HOLD_FLAG and GET_VENDOR_HOLD_FLAG — indicate whether amount-based or vendor-level holds are active.

Tables Accessed

The package reads and writes through APPS synonyms, with the most significant dependencies being AP_INVOICES_ALL and AP_INVOICE_LINES_ALL for header and line data, AP_INVOICE_DISTRIBUTIONS_ALL for accounting distributions, and AP_PAYMENT_SCHEDULES_ALL for scheduled payment information. Prepayment logic relies on AP_PREPAY_UTILS_PKG and related history structures. Hold and approval queries reference AP_HOLDS, AP_HOLDS_ALL, and AP_APINV_APPROVERS. Purchase order correlation draws on PO_HEADERS, PO_LINE_LOCATIONS_ALL, PO_RELEASES, and PO_VENDOR_SITES_ALL, while receipt matching uses RCV_SHIPMENT_HEADERS and RCV_TRANSACTIONS. Expense-related data is sourced from AP_EXPENSE_REPORT_HEADERS and AP_EXPENSE_REPORT_LINES. Payment and bank data come from AP_CHECKS, AP_INVOICE_PAYMENTS, AP_PAYMENT_HISTORY, IBY_EXTERNAL_PAYEES_ALL, and IBY_PMT_INSTR_USES_ALL. Additional references include AP_SYSTEM_PARAMETERS_ALL, FINANCIALS_SYSTEM_PARAMS_ALL, GL_SETS_OF_BOOKS, XLA_EVENTS, and FND_MESSAGE/FND_LOG for messaging and diagnostics.

Usage Notes

AP_INVOICES_UTILITY_PKG is not referenced by any database object per the dependency metadata, yet it is referenced by 45 other packages, indicating it is invoked predominantly from Payables forms, concurrent programs, and other PL/SQL packages rather than through direct event triggers. Typical invocation scenarios include the Invoice Workbench and related inquiry forms displaying posting status, approval status, holds counts, or prepayment availability; concurrent programs such as invoice validation and matching that require PO, release, and receipt references; and custom extensions that need standardized lookups of invoice attributes. Because the package depends on AP_CLM_PVT_PKG, AP_PREPAY_UTILS_PKG, AP_IBY_UTILITY_PKG, FV_GTAS_UTILITY_PKG, and APP_EXCEPTION, callers should invoke it within the APPS schema context and account for logging and exception behavior. Developers extending Payables should reuse these documented routines rather than duplicating invoice data retrieval, and should be aware that the package is version-sensitive across EBS 12.1.1 and 12.2.2, where table and view synonyms, particularly those tied to IBY and XLA, may differ.