Search Results c_no_data_found_p




Overview

PA_PAXCCARS_XMLP_PKG is a report-supporting PL/SQL package body owned by APPS in Oracle E-Business Suite. It is the packaged companion to an Oracle Reports XML Publisher (XMLP) concurrent program in the Projects (PA) module — the naming convention PA_..._XMLP_PKG identifies it as the generated server-side package that Oracle Reports creates when a report is converted to, or run through, the XML Publisher engine. Its role is to supply the interface variables, header values, and before/after report logic that the report executable requires, rather than to implement the substantive business transaction itself.

The package exposes the standard Oracle Reports package structure: initialization logic in BEFOREREPORT, teardown in AFTERREPORT, and a set of getter functions that surface package-level constants to the report layout. The user search term "c_dummy_data_p" corresponds to one of these getter accessors, indicating that the person was tracing how a report-level dummy data flag is populated and returned.

Key Procedures and Functions

Tables Accessed

The documented body references two tables through APPS synonyms. PA_LOOKUPS is queried for the MESSAGE lookup type with code NO_DATA_FOUND, supplying the display string stored in C_NO_DATA_FOUND. GL_SETS_OF_BOOKS is queried for the ledger NAME corresponding to the GL_SET_OF_BKS_ID profile option, populating the report header. Both are read-only lookups performed during initialization; no inserts, updates, or deletes are documented.

Usage Notes

This package is not invoked by other PL/SQL packages — the metadata records zero referencing packages. It is called implicitly by the Oracle Reports runtime when the associated PA XML Publisher concurrent program executes, with BEFOREREPORT firing before the report query and AFTERREPORT after output generation. The C_*_P getter functions are referenced as report formula or parameter columns so that layout elements can display the ledger name, the NO_DATA_FOUND message, and the dummy-data indicator. Because it is a generated-style XMLP wrapper, customization should be avoided; changes belong in the underlying report definition, and the package should be regenerated rather than patched by hand under EBS 12.1.1 or 12.2.2.