Search Results l_report_name




Overview
Explore in AI Chat

Overview

FA_FASPARAS_XMLP_PKG is the generated PL/SQL package body that backs the Oracle E-Business Suite concurrent program associated with the Parent Asset Report (report short name FASPARAS). The package resides in the APPS schema and is classified under the ETRM as an "OTHER" API type, meaning it is not a formally supported public API but rather the internal runtime support code produced for an Oracle Reports XML publisher (XMLP) report definition. Its principal business purpose is to supply the runtime binding values and report-level initialization logic that Oracle Reports requires when the Parent Asset Report is submitted from Fixed Assets. During execution the package resolves the concurrent request context, derives the displayable report name from the concurrent program definition, and exposes the report's placeholder (user parameter) values to the report layout. The package is documented against Oracle EBS 12.1.1 and 12.2.2, and its header indicates that the last source revision was checked in during the 2009 R12 development cycle.

Key Procedures and Functions

The ETRM metadata documents five program units in this package body.

  • REPORT_NAMEFORMULA — The only function carrying business logic. It accepts the Company Name value passed by the report, assigns it to the RP_Company_Name placeholder, captures the current concurrent request identifier from FND_GLOBAL, and queries the concurrent program definition to obtain the user-facing program name. It strips the trailing " (XML)" qualifier from that name and stores the result in RP_Report_Name, which is returned to the report. An exception handler defaults the report name to ':PARENT ASSET REPORT:' if the lookup fails.
  • BEFOREREPORT — The standard Oracle Reports BeforeReport trigger stub. In this package the SRW.USER_EXIT call to FND SRWINIT is commented out, and the function simply returns TRUE.
  • AFTERREPORT — The corresponding AfterReport trigger stub. The SRW.USER_EXIT call to FND SRWEXIT is likewise commented out, and the function returns TRUE.
  • RP_COMPANY_NAME_P — A placeholder accessor that returns the current value of the RP_COMPANY_NAME package variable to the report.
  • RP_REPORT_NAME_P — A placeholder accessor that returns the current value of the RP_REPORT_NAME package variable to the report.

Tables Accessed

The package body issues a single SQL statement, which joins two views:

  • FND_CONCURRENT_REQUESTS — The documented table reference in the ETRM metadata. It is used to correlate the live P_CONC_REQUEST_ID with the program application identifier and concurrent program identifier that submitted the report.
  • FND_CONCURRENT_PROGRAMS_VL — Referenced in the source to retrieve the translated user_concurrent_program_name for the identified program. This lookup is what supplies the RP_Report_Name value that appears on the printed output.

Because both objects are referenced through APPS synonyms, the package executes with the privileges of the APPS schema and relies on the standard Oracle Applications security model. No DML is performed; the package is strictly a read-only consumer of concurrent manager metadata.

Usage Notes

The search term "rp_company_name" corresponds directly to the RP_COMPANY_NAME placeholder and its accessor function RP_COMPANY_NAME_P. Users encountering this identifier are typically looking at the report's parameter list, a report trigger, or a debugging session rather than at a callable API. The package is invoked implicitly whenever the Parent Asset Report concurrent program is run; the Oracle Reports runtime calls REPORT_NAMEFORMULA, BEFOREREPORT, AFTERREPORT, and the two placeholder functions in sequence. It is not referenced by any other PL/SQL package according to the ETRM cross-reference data, so it should not be called from custom code. Customizations that require a different company name or report title should be made in the report definition or by wrapping the concurrent program, not by modifying this generated package body, since any change risks being overwritten during patching or upgrade. The FND SRWINIT and FND SRWEXIT user exits are disabled in this revision, so no explicit Oracle Applications initialization or cleanup is performed by the package itself.