Search Results p_flexdata_det

Overview

GL_GLXRLACH_XMLP_PKG is the PL/SQL package that implements the Oracle General Ledger "Account Analysis" style XML Publisher (BI Publisher) report in Oracle E-Business Suite 12.1.1 and 12.2.2. The package naming convention (_XMLP_PKG) identifies it as a report logic container that is generated to support an XML Publisher-based concurrent report. Its role is to supply the runtime data model for a GL report that presents ledger account activity, balancing segment structure, and account descriptions in a formatted output. Because the package is owned by APPS and classified as OTHER, it is not a public API; it is a private report-support package whose procedures are invoked by the Oracle Reports/XML Publisher runtime and by the report's data model rather than by functional users directly.

Key Procedures and Functions

The package exposes twelve documented program units. The lifecycle-oriented members are BEFOREREPORT and AFTERREPORT, which handle pre- and post-processing of the report run, typically setting up session context and cleaning up after report generation. NEW_DESCFORMULA, OLD_DESC_P, and LEDGER_NAME_P are lexical or data-supplying functions/variables used to populate report fields such as account descriptions and the ledger name shown on the output. The account-flexfield columns are represented by P_FLEXDATA_SUM_P and P_FLEXDATA_DET_P, which correspond to the P_FLEXDATA_SUM and P_FLEXDATA_DET string variables that concatenate the SEGMENT1 through SEGMENT30 columns of the summary (cs1) and detail (cd) cursors, respectively, inserting newline characters between segments so the key account combination displays in a multi-line format. P_ORDER_BY_SUM_P and P_ORDER_BY_DET_P provide the ORDER BY clauses for the summary and detail queries, giving the report control over sorting. STRUCT_NUM_P supplies the account structure number used to resolve the key flexfield definition. WHERE_DAS_P and WHERE_TEMPLATE_P return the WHERE clause fragments that filter the report by the accounting/flexfield scope and by the applied report template. Notably, in the package source the P_FLEXDATA_DET variable definition appears first in a commented-out form and is then redefined with the active concatenation expression, illustrating that the identical SEGMENT concatenation pattern is applied to both the summary and detail cursors.

Tables Accessed

The ETRM metadata for this object lists no table references through APPS synonyms, and the documented excerpt is limited to the package specification. Based on the package's purpose and its references to cs1 and cd cursor aliases and SEGMENT1 through SEGMENT30 columns, the report is presumed to query General Ledger account analysis and balance/activity views (for example, GL account-code-combination and ledger structures) reflecting the account's flexible segment structure. Readers should confirm exact tables by inspecting the package body (GLXRLACHS.pls) in the instance, as the specification excerpt does not enumerate them.

Usage Notes

The package is not referenced by any other documented package (Referenced by 0 other packages), confirming that it is invoked only from the associated XML Publisher report definition and its concurrent program, not from custom PL/SQL. When the report "Account Analysis – XML" (or equivalent GL report using the GLXRLACH short name) is run from the Standard Report Submission form or the GL responsibility's report menu, the concurrent manager executes the report, and the XML Publisher engine calls BEFOREREPORT for initialization, resolves the template and structure parameters, executes the summary and detail queries using the WHERE and ORDER BY fragments supplied by WHERE_DAS_P, WHERE_TEMPLATE_P, P_ORDER_BY_SUM_P, and P_ORDER_BY_DET_P, and then produces output using the P_FLEXDATA_SUM and P_FLEXDATA_DET concatenations. AFTERREPORT performs final cleanup. Customizations should be limited to the report template (RTF) rather than modifying the package, since direct changes to a seeded APPS XMLP support package can be overwritten and can break the report's data model.