Search Results budget_name_p

Overview

APPS.GL_GLXRBJRN_XMLP_PKG is a report-support package generated for the Oracle General Ledger "Budget Journal" XML Publisher (BI Publisher) concurrent program, identified in the source header by the module prefix GLXRBJRN. The package acts as the PL/SQL anchor for the XML Publisher report definition, supplying the runtime bind parameters, session-level globals, and derived values that the report's data template and layout template consume during execution. It belongs to the standard General Ledger reporting family that renders ledger balances, budget journals, and account combinations through the XML Publisher engine rather than the legacy Oracle Reports runtime, though it retains the "_XMLP_PKG" naming convention produced by the Oracle Reports-to-XML conversion utilities.

The package exists primarily to satisfy the interface contract required by the XML Publisher concurrent program framework: it declares the report's parameter variables, exposes getter functions that the after-report and data-model phases call by name, and provides the BeforeReport and AfterReport entry points that the report engine invokes at defined lifecycle moments.

Key Procedures and Functions

• BEFOREREPORT — Lifecycle function executed before the report's data model runs. It performs initialization and validation of report inputs and any derived setup needed before rows are fetched.
• AFTERREPORT — Lifecycle function executed after the data model completes. It handles teardown, cleanup of package-level globals, and any post-processing that must occur once the report output has been produced.
• STRUCT_NUM_P — Getter returning the accounting flexfield structure number (STRUCT_NUM) used by the report.
• LEDGER_NAME_P — Getter returning the resolved ledger name (LEDGER_NAME) for the ledger selected at runtime.
• FLEXDATA_P — Getter returning the concatenated account segment string (FLEXDATA), built from segment1 through segment30 with newline delimiters, used to render the account combination.
• BUDGET_NAME_P — Getter returning the budget name (BUDGET_NAME) associated with the selected budget version.
• DAS_NAME_P — Getter returning the Data Access Set name (DAS_NAME) that governs the ledger and balancing segment security context of the report.
• WHERE_DAS_P — Getter returning the dynamically constructed WHERE clause fragment (WHERE_DAS) that restricts query results to the Data Access Set context. This function is the object most frequently referenced in searches, since it is the mechanism by which the report enforces Data Access Set security at the SQL level.

Tables Accessed

• GL_ACCESS_SETS — Read to resolve the Data Access Set assigned to the report's security context. The package uses this table to determine which ledgers the requesting user may see and to build the WHERE_DAS predicate returned by WHERE_DAS_P.
• GL_BUDGET_VERSIONS — Read to resolve the budget version selected by parameter and to derive the corresponding budget name returned by BUDGET_NAME_P. This ties the report output to a specific budget version rather than the ledger's default budget.

Both tables are referenced through APPS synonyms, consistent with standard Oracle EBS schema access conventions.

Usage Notes

GL_GLXRBJRN_XMLP_PKG is not intended for direct invocation by custom code. It is invoked exclusively by the XML Publisher concurrent program runtime when the Budget Journal report is submitted from the Submit Request window or from the General Ledger responsibility's standard report menus. The report engine calls BeforeReport, fetches the data model, invokes the getter functions as named data source columns, and finally calls AfterReport.

Because the package maintains report state in package-level variables such as P_LEDGER_ID, P_PERIOD_YEAR, and P_DAS_ID, it is stateful for the duration of a single concurrent request and is not reentrant across simultaneous submissions within the same session. The ETRM metadata records no inbound dependencies from other packages, confirming its role as a leaf-level report-support unit. Customizations should be limited to read-only inspection; modifications to the package body risk invalidating the XML Publisher report definition.