Search Results cp_comp_name_p

Overview

APPS.JL_JLCLGCAL_XMLP_PKG is a generated PL/SQL package that backs the Oracle EBS Localizations (JL) concurrent program JLCLGCAL, a General Ledger calendar/reporting utility delivered under the Oracle Financials for regional legislations. The package is constructed in the standard Oracle Reports/XML Publisher server-side pattern, where a concurrent program's runtime bind parameters are declared as global package variables and the report's computed columns and group formulas are implemented as package functions. It is compiled with AUTHID CURRENT_USER and carries the source header marker JLCLGCALS.pls 120.1, dated 2007/12/25. The package is classified as OTHER and is not a public application programming interface; it is intended solely for invocation by the JLCLGCAL concurrent program and its XML Publisher report definition.

Key Procedures and Functions

The 23 documented program units divide into three functional groups. The first group supplies the report's data values to the layout: AFTERREPORT performs end-of-run processing after the report body is produced, and the numerous _P functions — STRUCT_NUM_P, C_ACCOUNT_START_P, C_ACCOUNT_END_P, WHERE_FLEX_P, C_ACCT_P, SET_OF_BOOKS_NAME_P, CP_COMP_NAME_P, CP_COMP_ADDRESS1_P, CP_COMP_TAXPAYER_ID_P, CP_COMP_ESTAB_TYPE_P, CP_COMP_ADDRESS2_P and DELIMITER_P — each return the value of the corresponding package-level variable for use in the report template. The second group implements derived column formulas: C_DOC_NUMFORMULA and C_DOCUMENTFORMULA resolve the document number and document identification from the accounting flexfield model definition; CF_1FORMULA and C_END_BALFORMULA compute opening and closing balances by netting the debit and credit amounts supplied to them. The third group resolves the reporting window and selection criteria: START_EFFECTIVE_PERIOD_NUMFORM and END_EFFECTIVE_PERIOD_NUMFORMUL return the numeric effective period identifiers that bound the report, while GET_DYNAMIC_WHERE assembles the dynamic SQL WHERE clause used to filter the ledger data. The user's search term, end_effective_period_numformul, corresponds to the END_EFFECTIVE_PERIOD_NUMFORMUL function, which supplies the upper bound of the period range to the report.

Tables Accessed

The package reads the following objects through APPS synonyms: FND_ID_FLEX_STRUCTURES, to validate the chart of accounts structure and segment ranges; GL_PERIOD_STATUSES, to determine the effective accounting periods within the requested range; GL_JE_SOURCES_TL, to obtain translated journal source descriptions; and JL_ZZ_GL_AXI_MODELS together with JL_ZZ_GL_AXI_MODEL_RANGES, the localization tables that hold the accounting flexfield model definitions and their account ranges. The JL_ZZ_GL_AXI_MODEL_RANGES data drives the WHERE_FLEX and account-range constants and the dynamic WHERE clause. No INSERT, UPDATE or DELETE operations are documented; the package behaves as a read-only reporting unit.

Usage Notes

JL_JLCLGCAL_XMLP_PKG is not referenced by any other database package (zero dependencies), confirming that it is a top-level report driver rather than a callable API. It is invoked when the JLCLGCAL concurrent program is submitted, typically from the Standard Request Submission (SRS) window or the Regional Localizations responsibility; the XML Publisher engine passes the request parameters into the package variables and calls the formula functions during report layout. The STRICT trace and debugging switches (P_TRACE_SWITCH, P_DEBUG_SWITCH) may be set through the concurrent program definition for diagnostics. Custom code should not call these functions directly, as the package is regenerated whenever the underlying report definition is modified; integrators requiring the same data should query GL_PERIOD_STATUSES and the JL_ZZ_GL_AXI_MODEL tables instead.