Search Results fa_fasmaint_xmlp_pkg




Overview

APPS.FA_FASMAINT_XMLP_PKG is the generated PL/SQL package body that backs the Oracle Assets Asset Maintenance report (FASMAINT), an XML Publisher (BI Publisher) concurrent program. The package's central responsibility is to supply the data model for the report: it resolves session and profile context, initializes the before/after report triggers, defines the report's SQL queries and lexicals, and inserts the retrieved rows into the report interface table that the XML template consumes. It resides in the APPS schema and is classified as a non-public, report-support object rather than a callable application programming interface.

In Oracle EBS 12.1.1 and 12.2.2, using XML Publisher with Oracle Reports requires a wrapper package of this shape (the *_XMLP_PKG convention) so that the publishing engine can drive report execution through standard entry points such as BEFOREREPORT and AFTERREPORT, and so that formulas and lexicals can be expressed in PL/SQL. Because the package is documented as valid and referencing only pre-existing Assets and SYS objects, it is not version-specific in behavior between the two releases; the difference lies in the file system and middle-tier topology (10.1.2/10.1.3 versus 12.2's WLS/Forms and Reports split), not in this database object.

Key Procedures and Functions

  • BEFOREREPORT — the standard XML Publisher pre-processing trigger. It establishes the runtime environment before the report query executes, including global and session context used by the data fetch.
  • AFTERREPORT — the corresponding post-processing trigger, used to finalize or clean up state once the data set has been produced.
  • GET_CURRENCY_CODE — resolves the currency code applicable to the reporting context, driving the precision and presentation of monetary figures on the report.
  • C_CURRENCY_CODE_P — the bind/parameter reference associated with the currency code, used by the report's query and lexicals.
  • C_REQUEST_ID_P — exposes the concurrent request ID to the report logic, the standard mechanism for correlating report output with the FND_CONCURRENT_REQUESTS record and for row partitioning.
  • RP_COMPANY_NAMEFORMULA — a report formula returning the company (legal entity / ledger) name for the report header.
  • DO_INSERTFORMULA — the formula that performs the insertion of fetched rows into the report interface table, making them available to the XML template.
  • RAISE_ORA_ERR — a utility for surfacing a formatted Oracle error from within report processing, supporting controlled failure diagnostics.

Tables Accessed

  • FA_MAINT_REP_ITF — the Asset Maintenance report interface table; this is the primary write target, populated via DO_INSERTFORMULA and read by the XML Publisher data template.
  • FA_BOOK_CONTROLS — the depreciation book definitions, supplying book-level attributes (currency, calendar, accounting rules) required to interpret maintenance records.
  • FA_SYSTEM_CONTROLS — installation-level Assets system options, providing defaults such as the primary ledger and organization-wide reporting settings.
  • FND_CURRENCIES — Oracle Application Object Library currency definitions, used with GET_CURRENCY_CODE to render amounts correctly.

The dependency metadata also shows references to GL_SETS_OF_BOOKS, FARX_C_MT, FND_GLOBAL and the standard DBMS_STANDARD and STANDARD packages, reflecting ledger name resolution, entity/global session values and error handling.

Usage Notes

The package is invoked indirectly: an end user submits the Asset Maintenance report as a concurrent request, and the XML Publisher/report runtime calls BEFOREREPORT, executes the data fetch, invokes the insert and company-name formulas, then calls AFTERREPORT. It should not be called from custom code, and the ETRM metadata confirms it is referenced by zero other database objects, indicating a terminal consumer of Assets data rather than a reusable API. Any customization should be applied through the report definition or a copy of the object, not by modifying the shipped APPS package.