Search Results p_min_precision

Overview

FA_FASLSCAL_XMLP_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that serves as the report logic container for the Fixed Assets depreciation schedule report published through the XML Publisher (BI Publisher) reporting framework. In the 12.1.1 and 12.2.2 releases, standard Oracle Reports concurrent programs were migrated to XML Publisher data definition templates, and each such report is paired with a generated PL/SQL wrapper package carrying the _XMLP_PKG suffix. This package supplies the bind parameters, report-level computation hooks, and format trigger functions that the XML Publisher engine invokes at runtime. The FA_FASLSCAL report family relates to asset depreciation schedule information, and this package is the technical artifact that controls how the report is initialized and how header-level values such as the report name and company name are resolved when the template is rendered across multiple operating units and ledgers.

Key Procedures and Functions

• BEFOREREPORT — The pre-execution hook. The XML Publisher engine calls this function before the report query executes to establish session context, default or validate input parameters, and prepare the report runtime environment. It returns a boolean indicating whether report execution should proceed.
• AFTERREPORT — The post-execution hook, invoked after the report data set has been processed. It performs cleanup and any finalization activities required once report rendering completes, and likewise returns a boolean status.
• RP_REPORT_NAMEFormula — A format trigger formula returning a VARCHAR2 value that supplies the report's display name to the template. It allows the printed or displayed report title to be resolved dynamically at run time rather than being hard-coded in the layout.
• RP_COMPANY_NAMEFormula — A sibling format trigger formula that returns the company or legal entity name as a VARCHAR2, letting the report header reflect the correct organization context for the concurrent request that is executing.

The package also declares four public variables that act as the report's parameter and derived-value holders: P_CONC_REQUEST_ID, P_MIN_PRECISION, P_FISCAL_YEAR_NAME, and P_FISCAL_YEAR. The user term p_min_precision refers to the P_MIN_PRECISION variable, which carries the numeric precision setting used when formatting monetary amounts in the depreciation schedule output.

Tables Accessed

• FA_SYSTEM_CONTROLS — The Fixed Assets system options table, read to obtain installation-level defaults and setup values needed to correctly render the report, such as the organization context and system-level precision behavior aligned with P_MIN_PRECISION.
• FND_CONCURRENT_REQUESTS — The concurrent manager request table, queried using P_CONC_REQUEST_ID to retrieve submission-time attributes of the running request, enabling the report to resolve runtime metadata and produce an appropriate completion status.

No additional tables are documented for this package, and the metadata records no other packages referencing it, indicating it is a terminal report-support unit rather than a shared library.

Usage Notes

This package is not intended for direct invocation by application code or custom extensions. It is instantiated by the XML Publisher concurrent program infrastructure when the associated Fixed Assets report is submitted from the Standard Request Submission form or scheduled through the concurrent manager. The FND_CONCURRENT_REQUESTS lookup is the standard mechanism by which such generated packages correlate execution with the parent request. Because the package is APPS-owned and classified as OTHER rather than as a public API, customizations should avoid calling its procedures directly; instead, developers should treat P_MIN_PRECISION and its sibling variables strictly as internal report parameters. Any modification to this package contradicts the 12.2.2 online patching model, where such generated report packages are delivered as part of the file system edition and should be extended only through supported template or data definition changes.