Search Results print_invoice_details




Overview
Explore in AI Chat

Overview

PSA_FA_INVOICE_DISTRIBUTIONS is an Oracle EBS PL/SQL package body owned by the APPS schema, classified as OTHER in the ETRM repository for release 12.2.2 (and applicable to 12.1.1). It resides in the Projects (PSA) product family and supports the integration between Oracle Payables invoice distributions and Oracle Assets. Its principal role is to identify Payables invoice distributions that meet user-supplied selection criteria and to update the asset tracking flag on those distributions so that they become eligible for transfer to Oracle Assets through the standard Projects-to-Assets and Payables-to-Assets flows.

The package is a non-API, internal utility, meaning it is not published for external integration but may be invoked by concurrent programs, forms, or custom code. It contains three documented procedures: UPDATE_ASSETS_TRACKING_FLAG, PRINT_HEADER_INFO, and PRINT_INVOICE_DETAILS. The header comment, dated 2007, includes FND_LOG instrumentation constants for statement, procedure, event, exception, error, and unexpected levels, indicating that execution is logged through the Oracle EBS logging framework using the path prefix PSA.PLSQL.PSAFATAB.PSA_FA_INVOICE_DISTRIBUTIONS.

Key Procedures and Functions

  • UPDATE_ASSETS_TRACKING_FLAG — The central procedure of the package and the object most commonly associated with the search term. It accepts selection criteria covering ledger, chart of accounts, a GL date range, and an account range, then constructs a dynamic WHERE clause using FA_RX_FLEX_PKG.FLEX_SQL to resolve the accounting flexfield range. It queries AP_INVOICE_DISTRIBUTIONS joined to GL_CODE_COMBINATIONS, filtering on posted distributions, and updates the asset tracking flag for the matching rows so they can be picked up by the asset transfer process.
  • PRINT_HEADER_INFO — Produces the header portion of the report or log output associated with the asset tracking update run, presenting the run parameters and contextual information.
  • PRINT_INVOICE_DETAILS — Produces the detail portion of the output, listing the invoices and distributions affected by the processing so that the results of the flag update can be reviewed.

Tables Accessed

  • AP_INVOICES_ALL — The invoice header table, referenced to relate distributions to their parent invoices for reporting and selection.
  • AP_INVOICE_DISTRIBUTIONS_ALL — The primary table acted upon; the asset tracking flag is updated here, along with keys such as invoice_id, invoice_distribution_id, and distribution_line_number used in the processing cursor.
  • AP_INVOICE_LINES_ALL — Invoice line information used to correlate distribution-level processing with the underlying invoice lines.
  • AP_INVOICE_DISTRIBUTIONS — The view used in the dynamic selection statement, joined to GL_CODE_COMBINATIONS for account validation.

Usage Notes

Because the package is classified as OTHER and is not referenced by any other documented package, it is typically invoked through a concurrent program or a custom wrapper rather than being called directly by standard application code. The procedure UPDATE_ASSETS_TRACKING_FLAG returns values through err_buf and ret_code OUT parameters, following the standard Oracle EBS concurrent program execution convention, which allows the caller to detect and report failures. Its parameters include p_ledger_id, p_chart_of_accounts, p_from_gl_date, p_to_gl_date, p_from_account, and p_to_account, enabling the same program to be run repeatedly for different ledgers and date ranges.

The dynamic SQL construction relies on FA_RX_FLEX_PKG.FLEX_SQL, so the account range must be expressed in terms of the accounting flexfield structure identified by the chart of accounts. Only distributions with a posted flag of Y are considered, which prevents unposted or incomplete distributions from having their asset tracking flag changed. Custom implementations should exercise care when invoking the procedure directly, as it performs a set-based update over potentially large volumes of Payables distributions; testing in a non-production environment and reviewing PRINT_INVOICE_DETAILS output before and after execution is advisable.