Search Results p_resp_application_id

Overview

The APPS.XLA_TP_SUMMARY_RPT_PKG package body provides the XML extract logic for the Trading Partner Summary Report within Oracle E-Business Suite Subledger Accounting (XLA). The package is a report-supporting PL/SQL unit rather than a general-purpose application programming interface; it is classified as OTHER in the ETRM repository, reflecting its role as an internal report generator rather than a callable business API. Its core responsibility is to assemble the data set consumed by the Oracle Reports / BI Publisher engine when the Trading Partner Summary Report is executed.

A defining characteristic of this package is its dependency on P_RESP_APPLICATION_ID. The beforeReport trigger function invokes XLA_SECURITY_PKG.set_security_context(P_RESP_APPLICATION_ID) as one of its first operations. This call establishes the correct transaction security context for the reporting session, ensuring that the extracted data is filtered according to the responsibility under which the report is run. The parameter therefore acts as the security anchor for the extract, so the report respects Subledger Accounting access restrictions rather than exposing the full ledger population.

Key Procedures and Functions

• BEFOREREPORT — A Boolean-returning function bound to the report's Before Report trigger. It sets the security context using P_RESP_APPLICATION_ID and derives the effective period boundaries for the extract from the user-supplied P_PERIOD_FROM and P_PERIOD_TO parameters. It also emits constant NULL placeholders for party-related columns so that the report's XML structure remains fixed even when no trading partner data qualifies.
• MIN_PERIOD — A helper function added in October 2007 to resolve the lower boundary of the reporting period. It supports accurate date range selection for the extract query.
• MAX_PERIOD — The complementary helper function returning the upper boundary of the reporting period, forming the paired range with MIN_PERIOD for period-based report filtering.

Tables Accessed

• GL_LEDGERS — Provides ledger definitions used to scope the reporting extract to the appropriate accounting ledger.
• GL_PERIODS — Supplies period start and end dates. The package converts the stored dates to fully qualified timestamps (start-of-day and end-of-day respectively) so that the report range is inclusive.
• GL_PERIOD_STATUSES — Used to validate the period status / open-and-closed state of the ledger periods, ensuring the extract aligns with periods that carry accounting activity.

Usage Notes

This package is invoked indirectly through the Trading Partner Summary Report concurrent program or its associated XML publisher report definition; it is not intended for direct invocation by external custom code. The version history shows it was modified in September 2007 to accommodate a third-party type parameter, and again in October 2007 to incorporate fixes for Bug 6401736 and Bug 6460402. Because the package references only three global ledger tables and no subledger transaction tables directly, its primary outputs are the period ranges and the report's structural placeholders, with row-level party data supplied by the report query. When troubleshooting missing data or column misalignment in the report output, verify the responsibility passed through P_RESP_APPLICATION_ID, confirm the responsibility has Subledger Accounting access, and validate the ledger period status for the selected range.