Search Results c_account_end_p

Overview

APPS.JL_JLCOGLAM_XMLP_PKG is the Oracle Reports PL/SQL library package body associated with the JLCOGLAM concurrent program report in Oracle E-Business Suite, functioning within the Latin American localizations for General Ledger. The package encapsulates report-level logic that executes at the standard Report Builder event points — before the report, before the parameter form, and after the report. Its principal responsibilities are to resolve and default the report's parameter values when the user does not supply them, to derive the chart of accounts and account range to be reported, and to populate descriptive heading information such as the reporting entity name and tax registration identifier. The package is owned by APPS and is classified as OTHER under the ETRM 12.2.2 metadata, reflecting that it is a report-support package rather than a published business API. It is not referenced by any other package, confirming that its scope is limited to the report with which it ships.

Key Procedures and Functions

The package exposes eleven documented program units. The three event functions — BEFOREREPORT, BEFOREPFORM, and AFTERREPORT — are invoked automatically by Report Builder during report execution. BEFOREREPORT performs the substantive initialization work: it derives literal start and end codes from the JL_CO_GL_MG_LITERALS table when the user has not entered them, retrieves the chart of accounts identifier and currency from the set of books, obtains the low and high account segment values, and resolves the reporting entity's name and registration number.

• BEFOREREPORT — Initializes report parameters and derived values prior to report data retrieval.
• AFTERREPORT — Post-report cleanup hook; the documented body returns TRUE without additional processing.
• BEFOREPFORM — Prepares values used by the report parameter form, including assignment of the concurrent request identifier from FND_GLOBAL.
• CP_COMP_NIT_P — Returns the company tax registration identifier (NIT) for display or filtering.
• CP_COMP_NIT_VERF_DIG_P — Returns the verification (check) digit associated with the company tax identifier.
• CP_LITERAL_START_P — Returns the resolved starting literal code parameter value.
• CP_LITERAL_END_P — Returns the resolved ending literal code parameter value.
• CP_LOCATION_ID_P — Returns the location identifier parameter used by the report.
• C_ACCOUNT_START_P — Returns the low account segment value derived from the chart of accounts.
• C_ACCOUNT_END_P — Returns the high account segment value derived from the chart of accounts; this is the function corresponding to the search term "c_account_end_p".
• C_CHART_OF_ACCOUNTS_ID_P — Returns the chart of accounts identifier resolved from the set of books.

Tables Accessed

The ETRM metadata documents a single directly referenced table, JL_CO_GL_MG_LITERALS (accessed through the APPS synonym). BEFOREREPORT queries this table using MIN and MAX aggregates on LITERAL_CODE, filtered by REPORTED_YEAR and SET_OF_BOOKS_ID, to establish the default literal range when the user leaves the corresponding parameters null. The other name-resolution queries visible in the package body draw on GL_SETS_OF_BOOKS for chart of accounts, currency, and book name information, and on XLE_FIRSTPARTY_INFORMATION_V for legal entity name and registration number, with a fallback to GL_SETS_OF_BOOKS when no legal entity record is found.

Usage Notes

This package is not intended for direct invocation by custom code. It is executed implicitly by Oracle Reports when the JLCOGLAM report is run, either from the Submit Requests form or from the standard concurrent program interface. The BEFOREPFORM function runs when the parameter form is displayed, BEFOREREPORT runs immediately before the report query executes, and AFTERREPORT runs at completion. Parameters that the user leaves blank are populated from the database defaults described above, so the report always receives a bounded literal and account range. Because it is a report library package owned by APPS and documented as OTHER, it should be treated as internal localization infrastructure; the supported integration points for these values remain the concurrent program parameters themselves rather than the package functions. Any modification would be overwritten by the standard Oracle patch cycle.