Search Results pa_rule_based_optimizer




Overview

The APPS.PA_PAXAASRP_XMLP_PKG package body is the generated PL/SQL side of a concurrent-program XML Publisher (BI Publisher) report in Oracle E-Business Suite Projects (PA). The report definition name, PAXAASRP, is the classic Oracle Reports-to-XML-Publisher naming convention for a run-time report within the Projects application, and the package exists solely to service that report's cover page and report-level logic. Rather than performing heavy calculation, it supplies the header values and initialization hooks that the report layout consumes when the concurrent request executes.

A notable detail for anyone searching on the term pa_rule_based_optimizer is the presence of the profile-option retrieval calls in BeforeReport. The commented FND GETPROFILE block references the profile option PA_RULE_BASED_OPTIMIZER, mapping it into a report parameter (:p_rule_optimizer), alongside a related PA_DEBUG_MODE flag. These rule-based optimizer settings govern the Projects budgeting and cost engine behavior, and the report originally surfaced them (and a function code) on its cover page so that users could confirm the active optimizer configuration for the run.

Key Procedures and Functions

  • GET_COVER_PAGE_VALUES — Populates or validates the values shown on the report cover page. It returns a BOOLEAN success indicator and traps exceptions, returning FALSE on failure.
  • BEFOREREPORT — The Oracle Reports BeforeReport trigger, invoked before the report executes. It resolves the function code supplied by the user (via p_function_code) to a function name from PA_FUNCTIONS, assigns it to the c_function_name variable, and invokes GET_COMPANY_NAME to resolve the organization's set-of-books name. It raises an initialization failure if company-name lookup fails.
  • GET_COMPANY_NAME — Retrieves the ledger name from GL_SETS_OF_BOOKS joined to PA_IMPLEMENTATIONS, returning it into the c_company_name_header variable used as the report header. Returns FALSE on lookup failure.
  • AFTERREPORT — The Oracle Reports AfterReport trigger, performing report cleanup and returning TRUE.
  • C_COMPANY_NAME_HEADER_P — Placeholder accessor returning the compiled company header value to the report layout.
  • C_FUNCTION_NAME_P — Placeholder accessor returning the resolved function name to the report layout.

All parameter lists are intentionally omitted here; the documented signatures are undocumented in the ETRM excerpt and are not inferred.

Tables Accessed

  • PA_FUNCTIONS — Read in BeforeReport to translate a supplied function code into its descriptive function name (truncated to 40 characters) for display on the report.
  • PA_IMPLEMENTATIONS — Joined with the General Ledger set-of-books table to determine the operating unit's implementation and its associated ledger.
  • GL_SETS_OF_BOOKS — Provides the ledger name used as the report's company header value.

These are referenced through APPS synonyms, consistent with standard EBS packages executing under the APPS schema.

Usage Notes

This package is not intended for direct invocation. It is called by the Oracle Reports/XML Publisher run-time engine when the associated Projects concurrent program executes. The report is submitted from the Projects responsibility as a standard concurrent request; the engine automatically calls BeforeReport and AfterReport, and the accessor functions are consumed by the report layout's data model. The package is referenced by zero other PL/SQL packages, confirming its role as a standalone report driver. Because the profile-option lookups are commented out in this version, the rule-based optimizer and debug-mode parameters are no longer actively populated by the package; any custom extension that needs these values must retrieve PA_RULE_BASED_OPTIMIZER through FND_PROFILE.VALUE independently. The header comments indicate the last revision predates the 12.x code line, so in 12.1.1 and 12.2.2 it should be treated as a stable, low-risk report component.