Search Results get_parameter_values




Overview

AP_APXFPMDR_XMLP_PKG is an Oracle Application Object Library XML Publisher (BI Publisher) report logic package belonging to the Oracle Payables application. It supports the concurrent report identified internally as APXFPMDR, and it encapsulates the PL/SQL that the XML Publisher runtime engine executes before and after the report data model is processed. The package follows the standard _XMLP_PKG convention used throughout Oracle E-Business Suite release 12.1.1 and 12.2.2, where a report-specific package contains initialization routines, NLS string retrieval, parameter derivation, and cover page value population. Its principal business purpose is to gather session-level reporting context — base currency attributes, company name, chart of accounts identifier, report dates, and localized text labels — so that the accompanying XML template renders correctly in the user's language and operating unit context. The package is owned by APPS and is classified as OTHER in the ETRM repository, meaning it is not published as a public application programming interface and should not be called directly by external integrations.

Key Procedures and Functions

The documented package exposes twenty-three procedures and functions. The main entry points invoked by the XML Publisher concurrent program are BEFOREREPORT and AFTERREPORT, which bracket report execution. GET_BASE_CURR_DATA queries the ledger base currency and its precision, minimum accountable unit, and description, assigning them to the package globals C_BASE_CURRENCY_CODE, C_BASE_PRECISION, C_BASE_MIN_ACCT_UNIT, and C_BASE_DESCRIPTION. GET_PARAMETER_VALUES is the routine relevant to the user's search; it derives or validates the runtime report parameter values used by the data model. GET_COVER_PAGE_VALUES populates the values shown on the report cover page, while GET_COMPANY_NAME retrieves the organization name for the header. GET_NLS_STRINGS resolves translated lookup meanings for the YES/NO indicators and the "ALL" NLS report parameter, and sets the message text for the AP_APPRVL_NO_DATA condition. CUSTOM_INIT provides a hook for report-specific initialization. Each function returns a BOOLEAN success indicator and traps errors through a WHEN OTHERS handler that returns FALSE. The remaining documented members are getter functions that expose cached package state to the XML template: C_BASE_CURRENCY_CODE_P, C_BASE_PRECISION_P, C_BASE_MIN_ACCT_UNIT_P, C_BASE_DESCRIPTION_P, C_COMPANY_NAME_HEADER_P, C_REPORT_START_DATE_P, C_NLS_YES_P, C_NLS_NO_P, C_NLS_ALL_P, C_NLS_NO_DATA_EXISTS_P, C_CHART_OF_ACCOUNTS_ID_P, and C_NLS_END_OF_REPORT_P.

Tables Accessed

The package reads configuration and reference data through APPS synonyms. AP_SYSTEM_PARAMETERS supplies the base currency code for the Payables installation, which anchors all currency formatting performed by the report. FND_CURRENCIES_VL provides precision, minimum accountable unit, and description for that currency. FND_LOOKUPS is queried for the YES_NO lookup meanings, and AP_LOOKUP_CODES supplies the NLS REPORT PARAMETER displayed field. The report data model additionally references AP_SUPPLIER_SITES_ALL, CE_BANK_ACCOUNTS, CE_BANK_ACCT_USES_ALL, and HZ_PARTIES to resolve supplier site, bank account, and trading partner party information used in the extracted output. All access is read-only; the package does not perform inserts, updates, or deletes.

Usage Notes

AP_APXFPMDR_XMLP_PKG is invoked exclusively by the XML Publisher concurrent program manager during execution of the APXFPMDR report. The BEFOREREPORT function runs first to initialize globals, resolve NLS strings, and cache base currency and company data; the data model query then executes; and AFTERREPORT performs any cleanup. Because the package is referenced by zero other packages in the ETRM repository, it has no inbound dependencies and is not intended for reuse. Customizations should be limited to the CUSTOM_INIT hook, which Oracle provides as the supported extension point. Direct calls from forms or custom PL/SQL are unsupported, and any modification requires recompilation under the APPS schema with the standard XML Publisher package grants intact.