Search Results c_base_currency_code

Overview

APPS.AP_APXINDTL_XMLP_PKG is the server-side PL/SQL package body supporting the Oracle Payables Invoice Detail Report, an XML Publisher (BI Publisher) concurrent report registered under the AP application. The report prints invoice, distribution, and payment-schedule detail for a selected range of invoices, and the package supplies the runtime values that the report layout requires: the ledger base currency definition, translated NLS strings, company and vendor descriptive flexfield data, and dynamically constructed query predicates.

The package is a generated report data-definition package (the _XMLP_PKG naming convention). It is not a public API; its API classification is OTHER, it exposes no committed entry points, and the ETRM metadata records that it is referenced by zero other packages. Its public functions are invoked by the report trigger framework at run time, and the constants it populates — most notably the base currency code and its precision settings — are consumed by the XML layout tokens and by the lexical parameters that drive the SQL statement.

Key Procedures and Functions

• GET_BASE_CURR_DATA — Resolves the ledger base currency by joining AP_SYSTEM_PARAMETERS to FND_CURRENCIES_VL, populating the package globals that hold base currency precision, minimum accountable unit, and description. This is the function most closely associated with the search term c_base_currency_code, since the base currency code drives rounding and formatting of all monetary columns in the report.
• CUSTOM_INIT — Placeholder initialization hook, retained for report-specific setup.
• GET_COVER_PAGE_VALUES — Populates cover-page tokens such as report title and run parameters.
• GET_NLS_STRINGS — Reads FND_LOOKUPS and AP_LOOKUP_CODES to load translated meanings for the YES/NO values and the "ALL" parameter, and constructs the no-data-exists message string.
• BEFOREREPORT / AFTERREPORT — Standard XML Publisher report triggers that orchestrate initialization before the data model executes and cleanup afterwards.
• GET_COMPANY_NAME, GET_FLEXDATA, GET_NLS_VENDOR_TYPE — Derive the operating unit/company name, descriptive flexfield concatenated segments, and the vendor type lookup meaning for grouping and display.
• SET_DYNAMIC_WHERE / SET_QUERY — Assemble the dynamic WHERE clause and the report query text from the user's submitted parameters.
• C_ALLCURR_* formula functions — A set of XML Publisher formula columns (C_ALLCURR_DSCNT_AMT_TKNFORMULA, C_ALLCURR_INV_AMTFORMULA, C_ALLCURR_DSCNT_AMT_LOSTFORMUL, C_ALLCURR_NO_RATE_CNTFORMULA, C_M_ALLCURR_INV_AMTFORMULA, C_M_ALLCURR_DTKN_AMTFORMULA, C_M_ALLCURR_DLST_AMTFORMULA, C_M_ALLCURR_NO_RATE_CNTFORMULA) that convert entered amounts into the base currency for display, including handling of rows where no exchange rate exists.
• C_BASE_CURRENCY_CODE_P — The package-level wrapper/constant exposing the base currency code to the layout.

Tables Accessed

The ETRM metadata documents AP_SYSTEM_PARAMETERS as the primary table referenced through APPS synonyms; the source excerpt confirms this table is joined to FND_CURRENCIES_VL in GET_BASE_CURR_DATA to obtain the base currency code, precision, minimum accountable unit, and currency description. GET_NLS_STRINGS additionally reads FND_LOOKUPS and AP_LOOKUP_CODES for translated YES/NO meanings and the NLS report parameter value. Read access is sufficient; the package performs no DML.

Usage Notes

The package is invoked exclusively by the Oracle Payables Invoice Detail Report concurrent program when that program's output format is XML Publisher. Users submit the report from the Payables responsibility; the report framework calls BEFOREREPORT, which chains into CUSTOM_INIT, GET_BASE_CURR_DATA, GET_COVER_PAGE_VALUES, GET_NLS_STRINGS, and SET_QUERY before the data model executes, then calls AFTERREPORT on completion. Custom code should treat this package as internal: because it is not a registered API and is referenced by no other packages, its functions and globals may change between patches. Any modification affects only the report's own output and should be re-applied after upgrades, as the package is regenerated by the report definition.