Search Results c_request_id




Overview

FA_FASMAINT_XMLP_PKG is the generated PL/SQL package body that supports the Oracle Assets FA FASMAINT report — the Concurrent Program responsible for building the fixed asset maintenance report extract. It is an XML Publisher (BI Publisher) report package, created automatically by Oracle Reports when a report definition is migrated or compiled against the XML Publisher data model. The package body acts as the report's server-side anchor: it initialises the runtime environment before the query is executed, retrieves report parameters and placeholders, exposes lexical/column values back to the report layout engine, and cleans up the temporary interface table after the output has been produced.

In release 12.1.1 and 12.2.2 this package lives in the APPS schema and is classified as OTHER in the ETRM registry, meaning it is not a public API but an internal report-support unit. It is not referenced by any other package, confirming that its only caller is the Oracle Reports runtime itself via the FND concurrent manager.

Key Procedures and Functions

  • BeforeReport — The report-level Before Report trigger. It populates P_CONC_REQUEST_ID from fnd_global.CONC_REQUEST_ID, then derives the functional currency code and currency precision for the book supplied in P_BOOK by joining the book controls, the set of books, and FND_CURRENCIES. The results are stored in the report placeholders C_Currency_Code and P_Min_Precision so the layout can format amounts correctly.
  • AfterReport — The report-level After Report trigger. Its primary purpose is to delete the rows this run inserted into FA_MAINT_REP_ITF, keyed on C_request_id. This is the exact point where the searched term c_request_id is used as the delete predicate, ensuring each concurrent request cleans up only its own interface rows.
  • C_REQUEST_ID_P — A placeholder accessor function that returns the value of the package-level variable C_request_id, allowing the report layout (or repeating frames/anchors) to reference the current concurrent request identifier.
  • C_CURRENCY_CODE_P — Accessor returning the package-level C_currency_code variable set during BeforeReport.
  • GET_CURRENCY_CODE — A helper that resolves and returns the currency code for a given book. The documented body simply handles NO_DATA_FOUND silently and otherwise routes unexpected errors through the error raiser.
  • RAISE_ORA_ERR — Central error-handling routine. It captures SQLERRM and raises APPLICATION_ERROR(-20101) to abort the report cleanly, replacing the older SRW.PROGRAM_ABORT mechanism used in character-mode Reports.
  • RP_COMPANY_NAMEFORMULA — A report formula column that selects the company name from FA_SYSTEM_CONTROLS and returns it for the report header. It returns a single space when no row is found.
  • DO_INSERTFORMULA — A formula function that delegates to the Assets public API FARX_C_MT.do_insert, passing P_BOOK and the report parameters to stage the maintenance extract rows.

Tables Accessed

  • FA_BOOK_CONTROLS — Read in BeforeReport to obtain the set of books identifier associated with the requested book type code.
  • GL_SETS_OF_BOOKS and FND_CURRENCIES — Joined to derive the functional currency code and its precision for the selected book.
  • FA_SYSTEM_CONTROLS — Read by the company name formula to place the operating company name on the report output.
  • FA_MAINT_REP_ITF — The report interface table. Rows are inserted during the report run (indirectly through FARX_C_MT) and are deleted in AfterReport using request_id = C_request_id.

Usage Notes

This package is never invoked directly by application forms or custom code. It is instantiated by the Oracle Reports/XML Publisher runtime when the FASMAINT concurrent program is submitted from the Assets responsibility. The C_request_id variable is the lynchpin of multi-user safety: because it is seeded from fnd_global.CONC_REQUEST_ID, concurrent runs against the same book do not interfere with one another's interface rows, and the AfterReport cleanup guarantees the temporary table is left empty. Customisations should not modify this generated package; the underlying business logic belongs to FARX_C_MT and the report definition itself.