Search Results c_changed_amountformula

Overview

APPS.AP_APXINUPD_XMLP_PKG is a PL/SQL package that supports the Oracle Payables Invoice Update/Inquiry XML Publisher concurrent report (APXINUPD). It is a report-specific driver package generated in the XML Publisher reporting style, following the naming convention AP_<report short name>_XMLP_PKG. The package encapsulates the server-side logic that the report requires: initialization of session state, retrieval of profile-dependent values (set of books, base currency, precision, chart of accounts), resolution of NLS strings, computation of derived columns, and formatting of the report output. Its file header places the source at version 120.0 dated 2007/12/27, indicating it is a long-standing component present in both EBS 12.1.1 and 12.2.2. The unit is classified as OTHER within the ETRM metadata, meaning it is not a public API and is not intended for direct invocation by external programs; it is bound to the concurrent program that renders the Payables invoice update report.

Key Procedures and Functions

The package exposes 44 documented procedures and functions. The initialization and control functions—GET_BASE_CURR_DATA, CUSTOM_INIT, GET_COVER_PAGE_VALUES, GET_NLS_STRINGS, BEFOREREPORT, AFTERREPORT, GET_COMPANY_NAME, GET_FLEXDATA, and CALCULATE_RUN_TIME—prepare report state before the data model executes and finalize it afterwards. BEFOREREPORT is the standard entry point invoked by the report trigger, while GET_BASE_CURR_DATA and GET_COVER_PAGE_VALUES populate the base currency, precision, minimum accounting unit, and cover-page parameters. The remaining functions are column formulas that the report groups use to derive display values. The C_VENDOR_SITE_IDFORMULA resolves the vendor site identifier, taking organization, site-keeping flag, vendor, vendor site code, and old site identifier into account. C_DUPLICATE_YES_NOFORMULA and C_UPDATE_DUP_VENDORFORMULA indicate whether a duplicate-vendor condition exists and whether the duplicate vendor should be updated. C_DUP_INVOICEFORMULA and C_NON_DUP_INVOICEFORMULA distinguish duplicate from non-duplicate invoices, while C_PAID_INVOICEFORMULA and C_UNPAID_INVOICEFORMULA classify payment state. Amount-oriented formulas include C_PAID_AMOUNTFORMULA and C_CHANGED_AMOUNTFORMULA. Recurring-payment handling is provided by C_DUP_RECURRING_COUNTFORMULA and C_RECURRING_COUNTFORMULA. Collectively these formulas implement the conditional logic that distinguishes duplicate vendors, duplicate invoices, and recurring payment records from their non-duplicate counterparts.

Tables Accessed

The package reads and writes data through APPS synonyms across the Payables and related schemas. Invoice data comes from AP_INVOICES_ALL, AP_INVOICE_DISTRIBUTIONS_ALL, AP_HISTORY_INVOICES_ALL, AP_INVOICE_PAYMENTS, and AP_INVOICE_PAYMENTS_ALL; payment instruments come from AP_CHECKS_ALL. Supplier and site information is drawn from AP_SUPPLIERS, AP_SUPPLIER_CONTACTS, and AP_SUPPLIER_SITES_ALL. Duplicate-vendor processing uses AP_DUPLICATE_VENDORS and AP_DUPLICATE_VENDORS_ALL, while recurring payments are read from AP_RECURRING_PAYMENTS and AP_RECURRING_PAYMENTS_ALL. FND_CONCURRENT_REQUESTS supplies the concurrent request context, and PO_AUTOSOURCE_DOCUMENTS is referenced for purchasing auto-source document information. The presence of the writable _ALL tables indicates the report and its supporting logic operate directly on the multi-org enabled base tables rather than on secured views alone.

Usage Notes

This package is invoked only through the Oracle Payables invoice update/inquiry report concurrent program. GET_COVER_PAGE_VALUES and GET_NLS_STRINGS run during the report's BeforeReport phase, and AFTERREPORT executes at completion. Because the ETRM metadata records zero packages referencing this unit, it is neither a dependency for other PL/SQL packages nor a supported integration point. Customizations that must influence report behavior should target the underlying base tables, the concurrent program definition, or the XML Publisher template rather than modifying this package. The embedded values P_CHV_INSTALLED_FLAG and P_MRP_INSTALLED_FLAG default to 'N', reflecting optional feature flags. The BEFOREREPORT, AFTERREPORT, CUSTOM_INIT, and *_FORMULA functions are generated and may be regenerated by the report builder; direct edits risk being overwritten during patching or upgrade. The user's search term "c_vendor_id" corresponds to the C_VENDOR_ID parameter referenced by C_VENDOR_SITE_IDFORMULA, which is the documented point in this package where vendor identity is resolved for the report output.