Search Results cp_gl_end

Overview

PA_PAXCCGLA_XMLP_PKG is the generated PL/SQL package body that supports the Oracle Project Accounting XML Publisher report PAXCCGLA (Subledger Accounting / GL Account Analysis style extract). Consistent with the Oracle Reports-to-XML-Publisher conversion pattern used throughout EBS 12.1.1 and 12.2.2, the package encapsulates the report's before-report and after-report logic, formula columns, and user-defined parameter processing. Its principal business role is to resolve GL accounting period boundaries from user-entered period names, build a dynamic GL_DATE range predicate, and expose report-level parameters such as the journal entry source name and company name to the underlying data model. In this way the report can restrict its accounting extract to a valid GL date window without requiring the user to supply explicit dates.

Key Procedures and Functions

• BEFOREREPORT — Executes before the data model query runs. It formats the interface date parameters, validates company name retrieval, resolves lookup values, and computes the GL date range predicate consumed by the report query.
• GET_COVER_PAGE_VALUES — Returns a BOOLEAN flag used to control cover page value resolution for the report layout.
• GET_COMPANY_NAME — Retrieves and validates the organization/company name for the report header; failure raises the internal init_failure exception.
• CF_ACCT_CURRENCY_CODEFORMULA, CF_FROM_DATEFORMULA, CF_TO_DATEFORMULA, ACCOUNT_IDFORMULA — Formula columns returning the account currency code, the from-date and to-date display values, and the account identifier respectively.
• AFTERREPORT — Post-processing hook invoked after report completion, typically used for cleanup and teardown of report-level state.
• AFTERPFORM — Parameter-form post-processing hook executed after user parameter validation.
• C_COMPANY_NAME_HEADER_P, C_NO_DATA_FOUND_P, C_DUMMY_DATA_P, CP_WHERE_P, CP_GL_START_P, CP_GL_END_P, CP_USR_JE_SNAME_P — Placeholder accessor functions exposing company name header text, the "no data found" message, dummy data handling, the dynamic WHERE clause, the computed GL start date, GL end date, and the user journal entry source name to the report layout.

Tables Accessed

• GL_JE_SOURCES — Queried to resolve the journal entry source name for 'Project Accounting' into the report parameter CP_USR_JE_SNAME. This identifies the SLA journal source used for project-related accounting entries.
• GL_PERIODS — Queried to derive the start_date and end_date for the "from" and "to" period names entered by the user, based on the period set name obtained from GL_SETS_OF_BOOKS. The resulting dates populate the cp_gl_start and cp_gl_end parameters.
• PA_LOOKUPS (implied by the NO_DATA_FOUND lookup) — Used to retrieve the localized "no data found" message text stored against lookup type 'MESSAGE'.
• GL_SETS_OF_BOOKS (implied) — Provides the period_set_name associated with the set of books selected by the user.

Usage Notes

This package is not called directly by other PL/SQL units; the ETRM metadata indicates it is referenced by zero other packages. It is invoked exclusively through the XML Publisher concurrent program that runs the PAXCCGLA report. The user-supplied parameters p_from_periods and p_to_period are converted to GL dates inside BEFOREREPORT, and the resulting l_where_clause (a GL_DATE BETWEEN predicate, or '1=1' when both periods are null) drives the report's data extraction. The parameter cp_gl_start is the key bind variable connecting user period input to the SQL predicate, making it directly relevant to searches such as "cp_gl_start". Customizations should avoid modifying this generated package body, as regeneration by the XML Publisher template utility will overwrite changes.