Search Results p_run_validation

Overview

PA_PAXARPVD_XMLP_PKG is the generated PL/SQL package body associated with the Oracle Projects XML Publisher (BI Publisher) concurrent program used to produce the Purge Batch Validation Report. In Oracle EBS 12.1.1 and 12.2.2, report-based concurrent programs that were originally written using Oracle Reports are wrapped by an XMLP package that acts as the execution shell. This shell drives the report lifecycle: it initializes the runtime environment, resolves profile options and request IDs, executes any pre-report business logic, and exposes values to the report data model and layout templates.

The package is classified as OTHER in ETRM, meaning it is not a public API and is not intended for direct invocation by external code. It is consumed internally by the Oracle Projects purge/validation reporting process, which supports the Purge Batches functionality used to remove obsolete transaction data while validating batch integrity before the destructive purge is executed.

Key Procedures and Functions

• GET_COVER_PAGE_VALUES — Returns a Boolean indicating success in populating the cover-page level output values. Wrapped in an exception handler that returns FALSE on error.
• BEFOREREPORT — The principal before-report trigger. Captures the concurrent request ID via FND_GLOBAL.CONC_REQUEST_ID, resolves the PA_RULE_BASED_OPTIMIZER profile, populates numerous report parameters and lexical variables, and conditionally invokes validation logic when P_RUN_VALIDATION is set to 'Y'.
• GET_COMPANY_NAME — Retrieves the company name used on the report header.
• AFTERREPORT — The after-report trigger, executed once the report data has been generated, used for cleanup and finalization.
• C_COMPANY_NAME_HEADER_P — Returns the company name header value for use in the report layout.
• C_NO_DATA_FOUND_P — Returns the "no data found" message derived from PA_LOOKUPS for use in the report.
• C_DUMMY_DATA_P — Exposes a dummy placeholder value to the report template.
• C_BATCH_NAME_P — Returns the purge batch name.
• C_BATCH_DESCRIPTION_P — Returns the purge batch description.
• C_BATCH_STATUS_P — Returns the raw batch status code.
• C_THROUGH_DATE_P — Returns the batch transaction-through date.
• C_BATCH_STATUS_MEANING_P — Returns the decoded meaning of the batch status via PA_LOOKUPS.
• C_BATCH_ACTIVE_CLOSED_P — Returns the active/closed indicator flag for the batch.
• C_YES_P and C_NO_P — Return the localized Yes/No meanings from FND_LOOKUPS (YES_NO lookup type).
• C_RUN_VALIDATION_P — Returns the decoded Yes/No indicating whether validation was requested.
• C_REPORT_ERRORS_ONLY_P — Returns the decoded Yes/No indicating whether the report should display errors only. This is the parameter referenced by the user search term "c_report_errors_only_p" and corresponds to the concurrent program parameter P_REPORT_ERRORS_ONLY.

Tables Accessed

• PA_PURGE_BATCHES — The primary source of batch header data. Read to populate C_BATCH_NAME, C_BATCH_DESCRIPTION, C_BATCH_STATUS, C_THROUGH_DATE, and C_BATCH_ACTIVE_CLOSED, filtered by P_PURGE_BATCH_ID.
• PA_IMPLEMENTATIONS — Accessed to obtain implementation/company context, including the company name rendered on the report header.
• DUAL — Used in the DECODE construct to translate the Y/N parameters P_RUN_VALIDATION and P_REPORT_ERRORS_ONLY into the localized Yes/No meanings.
• PA_LOOKUPS — Read for lookup meanings such as the NO_DATA_FOUND message and the PURGE_BATCH status meanings. FND_LOOKUPS is also queried for the YES_NO lookup type meanings.

Usage Notes

This package is not invoked directly by end users or custom code; it is executed by the concurrent manager when the Purge Batch Validation Report (XML Publisher) concurrent program runs. The parameters passed into the concurrent program drive the package's parameter-handling functions: the purge batch ID selects the batch, the run-validation flag controls whether PA_PURGE_VALIDATE.BATCHVAL is called to validate the batch before reporting, and the report-errors-only flag controls whether the output is limited to validation errors. Because referenced by zero other packages, it has no downstream PL/SQL dependencies and should be treated as a self-contained report shell. Modifications are strongly discouraged, as the body is regenerated from Oracle Reports source (indicated by the RCS header and SRW user-exit comments) during standard Oracle patch application.