Search Results put_encoding
Overview
FA_XML_REPORT_PKG is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Assets (Fixed Assets, FA) product family and provides the XML report generation infrastructure used by the Asset Impairment and Cash Generating Unit reporting features. The package is declared with AUTHID CURRENT_USER, meaning its SQL statements execute with the privileges of the invoking session rather than the definer, which is consistent with its role as a report-generation utility invoked from concurrent programs and other calling contexts.
The package serves two distinct purposes. First, it supplies low-level XML output primitives — encoding declarations, start tags, end tags, and CLOB-to-file writing — that allow callers to construct well-formed XML documents incrementally. Second, it exposes two higher-level report entry points that query the Fixed Assets schema and emit XML output for presentation or downstream processing. The package contains six documented procedures in total and is not referenced by any other documented package, indicating it functions as a terminal consumer rather than a shared library within the documented call graph.
Key Procedures and Functions
- PUT_ENCODING — Emits the XML encoding declaration for the generated document. This is the procedure most directly associated with the user's search term and is typically the first formatting call made when a report begins writing its XML stream.
- PUT_STARTTAG — Writes an opening XML element tag to the output stream, accepting the tag name as its input. Used to build the element hierarchy of the report document.
- PUT_ENDTAG — Writes the corresponding closing XML element tag, accepting the tag name as its input. Paired with PUT_STARTTAG to delimit report sections.
- CLOB_TO_FILE — Writes the accumulated XML content, held in a CLOB, to a file. This procedure bridges the in-memory XML generation performed by the tag and encoding primitives and the physical output artifact consumed by the reporting layer.
- ASSET_IMPAIRMENT_REPORT — The principal report generator for asset impairment data. It is a concurrent-program style procedure with
errbufandretcodeoutput parameters, and it accepts inputs identifying the book, ledger, and accounting period, with optional inputs to narrow the report to a specific impairment or cash generating unit. Additional parameters carry the concurrent request ID and a status value for internal control and are not exposed to the user at submission time. - LIST_ASSETS_BY_CASH_GEN — Produces a listing of assets associated with a cash generating unit. Like the impairment report, it follows the concurrent-program signature convention with
errbufandretcodeoutputs, and it accepts a book type, set of books, cash generating unit identifier, and asset identifier as selection criteria.
Tables Accessed
The package reads from a focused set of Fixed Assets tables and views. The core asset and financial data is drawn from FA_ADDITIONS_B (asset definitions), FA_BOOKS and FA_MC_BOOKS (asset book balances in the primary and multiple reporting currencies), and FA_BOOK_CONTROLS, which governs book and period status. Period context is supplied by FA_DEPRN_PERIODS. Impairment-specific data is sourced from FA_IMPAIRMENTS and its multi-currency counterpart FA_MC_IMPAIRMENTS, while FA_CASH_GEN_UNITS supplies cash generating unit definitions. FA_LOOKUPS_TL provides translated lookup values, most likely for decoding status or type codes into readable text. Oracle-supplied packages DBMS_LOB and DBMS_XMLGEN are referenced for CLOB manipulation and XML document assembly respectively. All base tables are accessed through APPS synonyms, consistent with standard EBS data access conventions.
Usage Notes
FA_XML_REPORT_PKG is not intended for direct end-user invocation. The report procedures — ASSET_IMPAIRMENT_REPORT and LIST_ASSETS_BY_CASH_GEN — are structured as concurrent program entry points, evidenced by their standard errbuf and retcode signature, and are registered as Oracle Assets reports submitted through the standard concurrent manager request submission flow or a designated responsibility menu. The formatting procedures (PUT_ENCODING, PUT_STARTTAG, PUT_ENDTAG, CLOB_TO_FILE) are internal helpers called by the report procedures or by custom code that needs to emit XML in the same style; PUT_ENCODING is typically the first call in any such sequence. Because the package is AUTHID CURRENT_USER, callers must have appropriate privileges on the underlying FA tables or must execute it in a context where APPS-level access is granted. Customizations that require asset impairment output in XML form can invoke the report procedures directly, but the supported path is through the registered concurrent program. As the package is referenced by no other documented package, changes to it carry limited downstream package-level impact.