Search Results gl_je_headers_u1

Overview

APPS.JG_JGZZGLJRN_XMLP_PKG is the packaged backend of a Global Accounting (JG) XML Publisher concurrent report that produces a general journal listing. The package body coordinates report execution by resolving user-supplied report parameters into the bind and lexical variables consumed by the report's underlying SQL query, then delegating output rendering to the XML Publisher engine. Its scope spans ledger (or ledger set) selection, data access set validation, chart of accounts resolution, period and currency filtering, and legal entity address/registration information used for statutory reporting headers.

The package belongs to the Global Accounting localized reporting layer, which is significant for installations using Global Ledger or country-specific journal reporting requirements. The embedded header comment ($Header: JGZZGLJRNB.pls 120.2 2007/12/25 16:06:35 npannamp noship $) indicates the source is marked "noship" — that is, it is not shipped as part of the standard product but delivered as a localized or customer-requested concurrent program, consistent with its APPS ownership and OTHER API classification.

Key Procedures and Functions

The documented package exposes 89 procedures and functions, most of which follow the XML Publisher formula-column convention (names suffixed with FORMULA) and parameter-resolution convention (names suffixed with _P).

• BEFOREREPORT / AFTERREPORT — Report-level lifecycle anchors. BEFOREREPORT captures the concurrent request ID into P_CONC_REQUEST_ID, formats the execution timestamp, converts canonical request-date parameters via FND_DATE.CANONICAL_TO_DATE, validates the data access set against GL_ACCESS_SETS, and derives ledger-restriction fragments based on whether the selected P_LEDGER_ID is a ledger or a ledger set (OBJECT_TYPE_CODE = 'S').
• GET_LE_INFO, GET_EFF_PERIOD_NUM — Helpers that populate legal entity attributes and the effective accounting period number used on the report.
• LE_*FORMULA series — LEGAL_ENTITY_NAMEFORMULA, LE_ADDRESS_LINE_1FORMULA through LE_ADDRESS_LINE_3FORMULA, LE_CITYFORMULA, LE_POSTAL_CODEFORMULA, LE_REGISTRATION_NUMBERFORMULA, LE_ACTIVITY_CODEFORMULA, and LEGAL_ENTITY_IDFORMULA supply legal-entity header data to the report layout.
• CF_LEDGER_NAMEFORMULA — Returns the ledger name displayed on the report output.
• Parameter and where-clause builders — DATA_ACCESS_SET_NAME_P, CHART_OF_ACCOUNTS_ID_P, DAS_WHERE_P, CURR_WHERE_JRNL_P, and PERIOD_WHERE_P construct the lexical WHERE clauses and derived parameters used by the report query. SECONDARY_TRACK_SEGMENT_DESCFO resolves secondary tracking segment descriptions.

Tables Accessed

The package reads (and does not directly write) from the following APPS synonyms:

• GL_ACCESS_SETS — validated to derive DATA_ACCESS_SET_NAME from P_ACCESS_SET_ID; failure raises GL_PLL_INVALID_DATA_ACCESS_SET.
• GL_LEDGERS — queried for OBJECT_TYPE_CODE to distinguish ledger from ledger set.
• GL_LEDGER_SET_ASSIGNMENTS — joined when the parameter identifies a ledger set, producing the ledger-set WHERE fragment.
• GL_PERIODS, GL_JE_CATEGORIES, GL_JE_SOURCES — supply period, journal category, and journal source validation used by the period and journal WHERE builders.
• GL_LEDGER_CONFIG_DETAILS, GL_LEDGER_NORM_SEG_VALS — used in legal entity and segment description resolution.
• FND_DOCUMENT_SEQUENCES — retrieved for document sequence information on the report.
• DUAL — used to derive REP_EXECUTION_DATE and convert start/end date parameters.

The tables referenced list notably does not include GL_JE_HEADERS or GL_JE_LINES; those are referenced directly by the report's own SQL query (the data model), not by this package body.

Usage Notes

This package is invoked implicitly by the XML Publisher concurrent program associated with the JGZZGLJRN report definition. Administrators run it from the Submit Request form or via FND_REQUEST.SUBMIT_REQUEST, supplying parameters such as ledger or ledger set, data access set, period, currency, and journal source/category. The BEFOREREPORT trigger fires before the data model executes, so any parameter errors (invalid access set, missing ledger) surface as report-level warnings. Because the source is marked "noship," the package should be treated as a localized extension; upgrades should verify version 120.2 or later remains compatible with the EBS 12.1.1/12.2.2 GL and JG schema. The unrelated search term gl_je_headers_u1 refers to the unique index on GL_JE_HEADERS and is not manipulated by this package; journal header rows are read by the report's SQL, not here.