Search Results c_dsp_previous_sumformula

Overview

PA_PAXALRUN_XMLP_PKG is a public PL/SQL package in the APPS schema (AUTHID CURRENT_USER) that supports the Oracle Projects concurrent program for mass allocation processing, executed as an XML Publisher (XMLP) report. The "XMLP_PKG" suffix indicates that the package is an Oracle Reports/XML Publisher report definition package generated to back a concurrent program driven by a BI Publisher data template. The package encapsulates report-level logic for the Mass Allocation Execution report (associated with the PAXALRUN report short name and header identifier visible in the source comment "PAXALRUNS.pls"). It exposes global variables and wrapper functions that the report triggering framework calls at runtime (BEFOREREPORT, AFTERREPORT), that display derived attributes on the report cover page and body, and that perform existence checks against the allocation and exception tables to decide whether data or exception notice lines must be printed.

Key Procedures and Functions

The package exposes roughly twenty-four documented functions and procedures. Their intended purposes are:

• GET_COVER_PAGE_VALUES — populates cover-page attributes such as company name, run identification, run mode, and run period before the report renders.
• BEFOREREPORT — the standard Oracle Reports format trigger executed before report output; initialises session and global package state.
• AFTERREPORT — the standard format trigger executed after report output; performs cleanup and final derived-value assignment.
• GET_COMPANY_NAME — retrieves the reporting entity (operating unit/company) name header.
• DRAFT_EXCEPTION_EXISTS — returns a numeric flag indicating whether unprocessed draft allocation exceptions exist for the run.
• ALLOC_TXN_EXISTS — returns a flag indicating whether allocation transactions exist for the run.
• RELEASE_EXCEPTION_EXISTS — returns a flag indicating whether release exceptions exist for the run.
• C_FMT_MASKFORMULA — resolves the currency formatting mask applied to numeric columns on the report.
• C_DSP_SUM_CURRENT_ALLOCATIONFO, C_DSP_SUM_PREV_ALLOCATIONFORMU, C_DSP_TOTAL_ALLOCATIONFORMULA — display formatting functions for summed current, previous-period, and total allocation amounts.
• C_DSP_CURRENT_ALLOCATIONFORMUL, C_DSP_CURRENT_SUMFORMULA, C_DSP_PREVIOUS_SUMFORMULA, C_DSP_TOT_SUMFORMULA — display formatting functions for current allocation, current sum, previous sum, and total sum values.
• C_COMPANY_NAME_HEADER_P, C_NO_DATA_FOUND_P, C_DUMMY_DATA_P, C_RULE_NAME_P, C_REQUEST_ID_P — getter wrappers returning the corresponding package global variables (company name header, no-data message, dummy data flag, rule name, and request id) to the report layout.

Tables Accessed

All table references are resolved through APPS synonyms. PA_ALLOC_RULES supplies allocation rule definition data (name, currency, rule id). PA_ALLOC_EXCEPTIONS underpins the DRAFT_EXCEPTION_EXISTS and RELEASE_EXCEPTION_EXISTS checks. PA_TRANSACTION_INTERFACE, PA_TRANSACTION_SOURCES, and PA_TRANSACTION_XFACE_CONTROL support the ALLOC_TXN_EXISTS determination by inspecting staged allocation transactions and their interface control rows. PA_IMPLEMENTATIONS provides installation/implementation-level attributes such as the functional currency used by C_FUNC_CURRENCY. DUAL is referenced for single-row utility selections. The package is read-mostly: it queries these tables to populate report globals and existence flags rather than performing direct DML.

Usage Notes

PA_PAXALRUN_XMLP_PKG is invoked by the Oracle Projects concurrent program that runs the Mass Allocation report. Its BEFOREREPORT and AFTERREPORT functions are called automatically by the report engine, and the display formatting functions (all prefixed C_DSP_ or C_FMT_) are called from the XML Publisher/Reports layout as column or formula triggers. The variable C_FUNC_CURRENCY — the object returned when users search on c_func_currency_p — holds the functional currency code (VARCHAR2(15)) resolved from the implementation, and is surfaced to the layout through the standard _P getter convention. It is not designed for direct calls from custom code; the supported contract is the concurrent program and its report template. The package is not referenced by any other package in the repository, confirming it is a leaf-level report-support unit. The package exposes no documented parameters or private helpers, so callers should treat the globals and getter functions as the public interface.