Search Results get_base_curr_data

Overview

APPS.JL_JLCOFARR_XMLP_PKG is a report logic package body residing in the Oracle E-Business Suite Applications (APPS) schema. Its name follows the standard Oracle Reports XML Publisher (XMLP) package naming convention, in which the _XMLP_PKG suffix identifies PL/SQL generated for a report whose output is rendered through the XML Publisher engine. The JL prefix associates the package with the Oracle Financials for Asia/Pacific (JL) product family, and the abbreviated component JLCOFARR indicates it supports a fixed assets report — specifically a company-level or book-level fixed asset report oriented toward a reporting currency. The package encapsulates the server-side data-fetching and formatting logic that a concurrent report request executes before the retrieved data set is passed to the report template. It is classified in the ETRM repository as an OTHER API (not a public or private API), meaning it is intended for internal use by the report it backs rather than for direct invocation by other application components. The header comment records a last modification in December 2007, indicating the logic is stable and consistent across the EBS 12.1.1 and 12.2.2 releases. The package references no other packages and is referenced by none, confirming its role as a self-contained report utility.

Key Procedures and Functions

The ETRM metadata documents fourteen procedures and functions, of which the user's search term GET_BASE_CURR_DATA is the first.

• GET_BASE_CURR_DATA — The principal initialization routine. It retrieves the company name and the category flexfield structure from FA_SYSTEM_CONTROLS, assigns them to package-level globals (C_COMPANY_NAME and CAT_FLEX_STRUCT), and resolves the reporting currency code from the general ledger set of books associated with the requested asset book type.
• RAISE_ERR — Raises an application error using an Oracle Application Object Library message name through FND_MESSAGE, terminating report execution with a user-defined message.
• RAISE_ORA_ERR — Similar to RAISE_ERR but additionally captures the Oracle error number and message via SQLCODE and SQLERRM before raising the application error. It is used to handle unexpected database exceptions.
• AFTERREPORT — The report completion trigger, which performs cleanup (including the FND SRWEXIT user exit in the original Reports implementation) and returns a boolean status.
• F_NET_VALFORMULA and F_APP_VALUATIONFORMULA — Formula functions that compute formatted values for report output columns such as net book value and the applied valuation.
• FORMULA2FORMULA — A helper function that resolves one report formula from another, typically for derived or dependent column calculations.
• C_COMPANY_NAME_P, C_STATUS_P, C_APP_VALUATION_P, CP_NET_VALUE_P, CAT_FLEX_STRUCT_P, C_ALL_SEGS_P — Accessor functions returning the corresponding package-level global values (company name, report status, applied valuation, net value, category flexfield structure, and all segments) to the report layout.
• BEFOREREPORT — The report initialization trigger, invoked before report data retrieval to establish parameter context and call the base currency routine.

Tables Accessed

The package reads from three fixed asset tables through APPS synonyms. FA_SYSTEM_CONTROLS supplies the company name and the category flexfield structure used to label and group report output. FA_BOOK_CONTROLS links an asset book type to its set of books, providing the join path needed to determine the reporting currency. FA_BOOKS is joined on BOOK_TYPE_CODE to identify the asset book or books within scope. Through GL_SETS_OF_BOOKS (accessed in the same query as the base currency lookup), the package derives the CURRENCY_CODE that drives the "base currency" orientation of the report. The package performs read-only queries; no inserts, updates, or deletes are documented.

Usage Notes

This package is invoked automatically when the associated fixed assets report is submitted as a concurrent program. The BEFOREREPORT trigger calls GET_BASE_CURR_DATA to populate package globals before the data model query executes, and the various _P accessor functions supply those globals to the report template during layout. AFTERREPORT provides post-processing cleanup. Custom code or additional report definitions may call the public accessors to reuse the same base currency and company context, but because the package is classified as OTHER in ETRM, direct invocation from outside the report is discouraged. The exclusion of the SRW message calls (commented out in favor of RAISE_APPLICATION_ERROR) reflects the migration from the legacy Oracle Reports character-mode runtime to the XML Publisher architecture, which is the standard execution model in EBS 12.1.1 and 12.2.2.