Search Results get_invoice_details




Overview

ASP_INVOICE_CONTENT_PROVIDER is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema. Its documented purpose is to provide content for past due invoices, functioning as a content provider within the application service provider (ASP) framework that supports the Oracle EBS HTML-based or iStore-style user interfaces. The package was created on 16-Aug-2005 by developer axavier and carries the source file identifier aspaincb.pls. In the Header comment the revision is recorded as 120.4 (2005/09/28), and the package is flagged with the "noship" designation, indicating that it is not shipped as a standalone product deliverable but forms part of the internal support infrastructure. Within the ETRM classification the package is registered under the API classification OTHER, meaning it is not a formal public business API such as those found in the Oracle Receivables or Order Management product families, but rather an internal utility used to assemble display content. The package declares a standard set of private constants — G_PKG_NAME, G_FILE_NAME, and G_MODULE — used for error message construction and instrumentation consistent with Oracle's PL/SQL coding standards.

Key Procedures and Functions

The ETRM metadata documents exactly one procedure in this package body:

  • CREATE_CONTENT — The sole documented routine, described in the source comments as providing content for the past due invoices. Its name identifies it as a content-generation routine rather than a query-only API; it assembles or returns the presentation content associated with overdue invoice records. Detailed parameter lists are not reproduced in the available metadata and should not be assumed without inspecting the package specification (aspaincs.pls), which the header explicitly references for procedure details.

No other public routines are documented for this package body. Any additional logic present in the body would be private helper code supporting CREATE_CONTENT.

Tables Accessed

The package references four tables through APPS synonyms, each of which supports the customer and invoice data required to render past due invoice content:

  • AR_PAYMENT_SCHEDULES_ALL — Holds the payment schedule lines for transactions and is the primary source for determining amounts due, due dates, and delinquency status of open invoices.
  • RA_CUSTOMER_TRX_ALL — The Receivables transaction header table supplying invoice number, transaction date, transaction type, and bill-to customer information.
  • HZ_CUST_ACCOUNTS_ALL — The customer account table, providing the account-level identity needed to associate transactions with the correct customer.
  • HZ_PARTIES — The party table supplying the customer name and party-level attributes used when displaying invoice content to the end user.

All four tables are consistent with a read-only content provider focused on Receivables aging and customer identification; no insert, update, or delete activity is implied by the documented description.

Usage Notes

Because this package is classified as OTHER and is marked noship, it is not intended for direct invocation by customer extensions. It is invoked internally by whatever user-interface or content-assembly layer requires a list of past due invoices for a given customer or account context — typically an HTML-based self-service page or a JSP/UIX region that delegates data retrieval to a provider package. The CREATE_CONTENT routine would be called with an established session or customer context and would return the formatted content for rendering.

The ETRM metadata records that the package is referenced by zero other packages, confirming that it sits at the leaf of the dependency tree rather than acting as a shared service. In Oracle EBS 12.1.1 and 12.2.2 environments, developers investigating a search for "get_invoice_details" should note that no routine of that name exists in this package; the documented entry point is CREATE_CONTENT, and any similar-sounding function must reside in another package. Customizations should avoid modifying this package directly, as it is an Oracle-owned, non-shipped internal object subject to change without notice.