Results for “p_report_style”
17 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
XLA_MULTIPERIOD_RPRTG_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the Subledger Accounting (XLA) product family. Its filename, xlarpmpa.pkh, and the header comment confirm its role: it invokes XLA_MULTIPERIOD_ACCOUNTING_PKG.complete_journal_entries and generates an XML extract for reporting multiperiod recognition entries, accrual reversal entries, and any associated errors. In practice the package underpins the Multiperiod Accounting reporting flow, allowing users to review, extract, and reconcile the accounting entries that Subledger Accounting produces when revenue or cost is recognized across more than one accounting period. The XML output it generates is consumed by the corresponding Oracle Reports or BI Publisher report definition, which renders the multiperiod entry lines, accrual reversals, and error diagnostics for the selected ledger, process category, and date range.
Key Procedures and Functions
The ETRM 12.2.2 metadata documents two procedures:
- BEFOREREPORT — Executed as the report's Before Report trigger. It prepares the reporting context by populating the package's global variables from the concurrent program parameters, including application, ledger, process category, end date, errors-only flag, report style, transfer-to-GL and post-in-GL flags, GL batch name, valuation method, and security values used to constrain data access. It also initializes the XML extract structures needed by the data model.
- AFTERREPORT — Executed as the After Report trigger. It finalizes the reporting cycle, releasing package state and completing any post-processing required once the XML extract and report output have been produced.
The package declaration reveals an extensive set of global variables (p_application_id, p_ledger_id, p_process_category_code, p_end_date, p_errors_only, p_report, p_transfer_to_gl, p_post_in_gl, p_valuation_method_code, and security tokens). These are populated by the report parameters and drive both the call to the accounting engine and the filter predicates used to select extract rows.
Tables Accessed
Through APPS synonyms the package references the following objects:
- GL_JE_SOURCES_TL — source of the journal entry source name displayed in report parameters.
- XLA_AE_HEADERS — the primary Subledger Accounting journal header table driving multiperiod recognition entries.
- XLA_ENTITY_ID_MAPPINGS — resolves subledger entity identifiers to accounting events for reporting context.
- XLA_EVENT_CLASS_ATTRS and XLA_EVENT_TYPES_B — provide event class and event type definitions used to classify multiperiod accounting activity.
- DBA_TAB_COLUMNS, USER_TAB_COLUMNS, USER_OBJECTS, USER_SYNONYMS — data dictionary lookups used for dynamic SQL construction and object resolution.
- PLITBLM — the standard PL/SQL integer table used for passing id lists into queries.
Usage Notes
XLA_MULTIPERIOD_RPRTG_PKG is not an API in the conventional sense; it is a report-support package. It is invoked indirectly through the Multiperiod Accounting reporting concurrent program, whose report definition calls BEFOREREPORT and AFTERREPORT at runtime. Because it depends on parameters such as ledger, process category, end date, and GL transfer/post flags, it should be executed only through the shipped concurrent program rather than called directly from custom code. No other packages reference it (referenced by 0 packages), confirming it is invoked exclusively from the report layer. Because it reads XLA and GL tables without modifying them, no special privileges beyond standard Subledger Accounting access are required, but users must have ledger and data access security set appropriately for the p_security_* parameters to return correct results.