Search Results get_nls_strings

Overview

APPS.JL_JLCOGLNE_XMLP_PKG is the generated PL/SQL package body that supports the Oracle E-Business Suite XML Publisher (BI Publisher) concurrent report JLCOGLNE. The report belongs to the Oracle Financials for Colombia (JL) localization, which delivers statutory accounting features required by Colombian fiscal and reporting regulations. The package implements the standard report-side logic used by the Oracle Reports to XML Publisher migration framework: an initialization routine that fires before the report data is fetched, a cleanup routine that executes after output is produced, and a set of formula functions that derive derived column values used during report rendering.

The underlying data model concerns the processing and validation of Colombian general ledger transactions and their associated NIT (tax identification number) classification. The package reads control information keyed by a concurrent request identifier and set of books so that each report execution is scoped to a single ledger and a single accounting period. Because the package is generated from an Oracle Reports PL/SQL library (the source header references JLCOGLNEB.pls), nearly all of its logic is procedural glue rather than business API exposure; it is classified as OTHER in the ETRM API classification scheme and is not referenced by any other database package.

Key Procedures and Functions

The package exposes seven documented routines:

• BEFOREREPORT — The before-report trigger for the XML Publisher template. It validates that the set of books parameter is populated, resolving the ledger name into the CP_SOB_NAME package variable, and retrieves the period name for the concurrent process from the control table. It also captures the concurrent request ID via FND_GLOBAL.CONC_REQUEST_ID and returns BOOLEAN success status. On missing or invalid data it raises an application error and aborts execution.
• AFTERREPORT — The after-report trigger. It performs end-of-report housekeeping, corresponding to the former SRWEXIT user exit in the Oracle Reports version, and returns a BOOLEAN success indicator.
• GET_NLS_STRINGS — The routine that initializes translated (NLS) display strings used by the report. This is the function most commonly searched for when investigating NLS behavior of the report. It returns BOOLEAN and is invoked from BEFOREREPORT; when it does not return TRUE, the report initialization is treated as incomplete. Its local variables include NLS_NO_DATA_FOUND and NLS_END_OF_FILE style placeholders that map exception conditions to localized message text.
• CP_PERIOD_NAMEFORMULA — A formula column function that supplies the value for the period name placeholder on the report layout.
• CF_1FORMULA — A formula column function that counts the general ledger transaction rows associated with the current process whose NIT classification equals '0'. This count supports the report's zero-NIT reporting logic.
• CP_SOB_NAME_P — The accessor/placeholder routine associated with the CP_SOB_NAME package variable, exposing the ledger name resolved during BEFOREREPORT to the report layout.
• CP_PERIOD_NAME_P — The accessor/placeholder routine associated with the CP_PERIOD_NAME package variable, exposing the period name resolved during BEFOREREPORT.

Tables Accessed

• GL_SETS_OF_BOOKS — Read in BEFOREREPORT to translate the P_SOB_ID parameter into the ledger name stored in CP_SOB_NAME. The query is restricted to a single row.
• JL_CO_GL_CONC_CTRL — The Colombian general ledger concurrent control table. It is queried by PROCESS_ID (the concurrent request ID) to retrieve the PERIOD_NAME for the run.
• JL_CO_GL_TRX — The Colombian general ledger transaction table. CF_1FORMULA counts rows in this table for the current process whose NIT_ID matches the '0' record.
• JL_CO_GL_NITS — The NIT reference table, used as a subquery source to resolve the NIT_ID corresponding to the literal NIT value '0'.

Usage Notes

This package is invoked exclusively by the XML Publisher concurrent program JLCOGLNE; it is not a callable business API and is referenced by no other package. The BEFOREREPORT and AFTERREPORT functions are wired to the report's before/after triggers, while the formula and placeholder functions are bound to specific layout fields in the RTF template. Because the underlying PL/SQL is generated, customizations should be applied through the Oracle Reports/XML Publisher source (JLCOGLNEB.pls) rather than by editing the package body directly. When diagnosing NLS or translated-message issues in this report, GET_NLS_STRINGS is the correct entry point to inspect.