Search Results c_amount_remaining_dspformula




Overview
Explore in AI Chat

Overview

APPS.AP_APXINPSR_XMLP_PKG is the generated PL/SQL package that backs the Oracle Payables XML Publisher report commonly identified as the Invoice Print Preview / Invoice Register style concurrent program (APXINPSR). Rather than containing reusable business logic, this package is a report-specific "package body container" created to support the XML Publisher (BI Publisher) runtime. It declares the report's parameter values, global working variables, NLS message strings, and the formatted cell formulas that drive the layout of the printed output.

The package's scope is limited to a single concurrent report execution cycle. It reads setup and currency information, initializes report-level variables during the BEFORE REPORT trigger, computes derived display values for report columns, and cleans up after the report finishes in AFTER REPORT. Because it is an XML Publisher data-model package, its procedures and functions are invoked by the report's group and formula columns, not by other application code.

Key Procedures and Functions

  • GET_BASE_CURR_DATA — Populates the base (functional) currency attributes, including currency code, precision, minimum accounting unit, and description, using the ledger's set of books context.
  • CUSTOM_INIT — Performs report-specific initialization beyond the standard template setup, preparing values needed by the report layout.
  • GET_COVER_PAGE_VALUES — Derives the values printed on the report cover page, such as company name and report parameters.
  • GET_NLS_STRINGS — Loads translated message text (Yes, No, All, Void, N/A, No Data Exists, End of Report) into the package's C_NLS_* variables so the report renders in the session language.
  • BEFOREREPORT — The Oracle Reports BEFORE REPORT trigger, which orchestrates the initialization sequence prior to data fetch.
  • AFTERREPORT — The AFTER REPORT trigger, used for final cleanup and any end-of-report processing.
  • GET_COMPANY_NAME — Retrieves the organization or ledger name used as the report header.
  • C_AMOUNT_FOR_SUMFORMULA — Formula column that determines whether an invoice amount contributes to report totals, based on invoice type, remaining amount, payment status, and earliest settlement date.
  • C_AMOUNT_REMAINING_CONVERTFORM — Formula column that converts the remaining invoice amount shown on the report, applying base-currency precision and rounding rules. This is the object the user searched for; it is the displayed-value counterpart to the summation formula above.
  • C_AMOUNT_REMAINING_DSPFORMULA — Formula column that formats the remaining amount for display on the report line.
  • C_NLS_YES_P, C_NLS_NO_P, C_NLS_ALL_P, C_NLS_NO_DATA_EXISTS_P, C_NLS_VOID_P, C_NLS_NA_P, C_NLS_END_OF_REPORT_P — Accessor functions exposed to the report layout so the corresponding NLS string can be referenced from the XML template.
  • C_REPORT_START_DATE_P, C_COMPANY_NAME_HEADER_P, C_BASE_CURRENCY_CODE_P — Accessor functions returning the report start date, company name header, and base currency code to the template.

Tables Accessed

The package references two documented tables through APPS synonyms:

  • AP_SYSTEM_PARAMETERS — Supplies Payables system options used to seed report defaults and validation context.
  • FND_CURRENCIES — Provides currency attributes (precision, minimum accounting unit, description) required by GET_BASE_CURR_DATA and the amount conversion formulas.

Invoice and vendor data are not read directly by this package; they are supplied to the report through its own SQL query and passed into the formula columns.

Usage Notes

AP_APXINPSR_XMLP_PKG is not intended to be called from custom code, forms, or other concurrent programs. It is instantiated by the Oracle Reports/XML Publisher engine at run time when the associated invoice report concurrent program executes, and its members are referenced from report triggers and formula columns. Because the ETRM metadata records zero referencing packages, integrators should treat it as report-internal plumbing. Any modification should be confined to the report definition itself; customizations belong in a separate package or in the XML template rather than in this generated container.