Search Results cf_corbformula

Overview

PA_PAXACRTA_XMLP_PKG is the generated PL/SQL package that supports the Oracle Projects concurrent program identified by the internal short name PAXACRTA. Like other packages whose names carry the _XMLP_PKG suffix, it is produced by the Oracle XML Publisher (BI Publisher) report registration process when a report definition is converted into an EBS concurrent program. The package acts as the server-side engine for the report: it receives the concurrent program's input parameters, prepares session-level and cover-page values, executes the underlying report query, and returns formatted output to the XML Publisher runtime for rendering as a printed document or report file.

The report served by this package is associated with Oracle Projects capitalization and project-type classification reporting. Its parameter list and formula functions focus on project type class codes, billable and capital indicators, and cost distribution across project classifications. In release 12.1.1 and 12.2.2 the package resides in the APPS schema and ships as a standard, non-customizable component; the header comment references source file PAXACRTAS.pls, consistent with the Oracle Projects (PA) module naming convention. No other packages in the documented EBS instance reference it, confirming that it is invoked exclusively by the concurrent manager and the XML Publisher runtime rather than by external PL/SQL code.

Key Procedures and Functions

• BEFOREREPORT — Standard XML Publisher pre-execution hook. Establishes session state and initializes the values needed before the report data query runs.
• GET_COVER_PAGE_VALUES — Populates the cover-page variables (company name, no-data message, and related header fields) used when the report is rendered.
• GET_COMPANY_NAME — Retrieves the organization name for the report header, derived from the PA_IMPLEMENTATIONS setup.
• AFTERREPORT — Standard post-execution hook that finalizes the report run.
• FMT — Numeric formatting helper that converts a number to a formatted character string for output.
• CF_CORBFORMULA — The function matched by the user's search term. It accepts a project type class code and returns a formatted string, used as a report cell formula to classify project types (for example, capitalizable vs. non-capitalizable or billable vs. non-billable categories).
• CF_NOTCORBFORMULA — Companion formula that returns the complementary classification for a project type class code, providing the inverse or "not" case of CF_CORBFORMULA.
• C_FMT_MASKFORMULA — Returns a formatting mask string applied to report columns.
• CF_CMT_EXCEPTIONSFORMULA — Formats summarized exception code values for display in the report.
• CF_CMT_LINE_EXCEPTFORMULA — Formats individual rejection/exception code lines.
• C_COMPANY_NAME_HEADER_P, C_NO_DATA_FOUND_P, C_DUMMY_DATA_P, C_RETCODE_P — Accessor functions that expose the package-level global variables (company header, no-data message, dummy data indicator, and return code) to the report template.

Tables Accessed

The package references two APPS synonyms. PA_IMPLEMENTATIONS is the Oracle Projects installation and setup table; it is queried to obtain the operating unit or organization name used in the report header and cover page, consistent with the GET_COMPANY_NAME and GET_COVER_PAGE_VALUES routines. DUAL is used for single-row scalar evaluations, such as computing format masks or evaluating formula expressions without touching application data. No insert, update, or delete operations are documented, which is expected for a reporting package.

Usage Notes

This package is not intended to be called directly from forms or custom PL/SQL. It is generated and owned by the Oracle Projects XML Publisher report definition and is invoked by the concurrent manager when the corresponding report request is submitted, and by the XML Publisher engine during data-source execution and template rendering. Customizations should never be applied to the package body itself, because the XML Publisher registration process will regenerate it and overwrite changes; business logic adjustments belong in the report data definition or template. The CF_CORBFORMULA and CF_NOTCORBFORMULA functions are referenced only by report layout formulas, which explains why a search for that term resolves to this object: it is a report-internal formula, not a public API. Any diagnostic work on report output should begin with the BEFOREREPORT and AFTERREPORT hooks and the return-code accessor, since these govern run success and message display.