Search Results p_debugvalidtrigger

Overview

APPS.BOM_BOMRWURS_XMLP_PKG is the generated PL/SQL package body that supports the Oracle EBS Bill of Materials XML Publisher (BI Publisher) concurrent report BOMRWURS. The naming convention _XMLP_PKG identifies packages automatically produced by the Oracle Reports-to-XML Publisher migration utilities; these packages wrap the data model logic of a report and expose the standard report lifecycle hooks invoked by the XML Publisher engine at runtime. In EBS 12.1.1 and 12.2.2, the package resides in the APPS schema and is owned by APPS. Its API classification is OTHER, meaning it is not a published or supported integration API but an internal, report-generated artifact. The business function is to initialize the concurrent manager environment for the BOM report, retrieve the executing request identifier, and provide the trigger-validation stub required by the report definition. It is not intended for direct invocation by customers or extension developers.

Key Procedures and Functions

Three PL/SQL units are documented in the package body.

• P_DEBUGVALIDTRIGGER — A debugging control function returning BOOLEAN. In the shipped source it unconditionally returns TRUE. The name reflects its role as the trigger-validation hook consulted by the report framework to determine whether debug validation is active; it is the object most frequently inspected when users search for the term "p_debugvalidtrigger" in connection with this report.
• BEFOREREPORT — The before-report lifecycle function returning BOOLEAN. It assigns the current concurrent request ID to the package variable P_CONC_REQUEST_ID using FND_GLOBAL.CONC_REQUEST_ID, and contains a commented-out FND SRWINIT user exit (SRW.USER_EXIT) that was disabled during the XML Publisher conversion. It returns TRUE to signal successful initialization. Capturing the concurrent request ID allows downstream queries in the data model to filter by request parameters and support report-level auditing.
• AFTERREPORT — The after-report lifecycle function returning BOOLEAN. It contains a commented-out FND SRWEXIT user exit and returns TRUE. Because the SRW user exits are inert under XML Publisher, this function performs no substantive cleanup; it exists to satisfy the expected report interface.

No parameter lists are documented for these units; per the source, each function takes no arguments. The package contains no additional private procedures, and its specification is limited to these three functions.

Tables Accessed

No base tables are referenced directly within the package body as documented. All database access for the report is performed by the XML Publisher data definition and its associated query, not by this PL/SQL wrapper. The only external programmatic dependency is the FND_GLOBAL package, which supplies the concurrent request ID from the FND_CONCURRENT_REQUESTS context maintained by the concurrent manager. Package headers indicate the source was last revised in version 120.1 (2008/01/05), consistent with the R12 XML Publisher migration era.

Usage Notes

This package is invoked indirectly by the concurrent manager when the BOMRWURS XML Publisher report is submitted; the XML Publisher runtime calls BEFOREREPORT and AFTERREPORT at the appropriate stages of report execution. It is not referenced by any other documented package (referenced by 0 other packages) and should not be called from forms, workflow, or custom code. Customizations to BOMRWURS report behavior should be made through the XML Publisher data template and concurrent program definition rather than by modifying this generated package, since regeneration or patching may overwrite any changes. The presence of the commented-out SRW.USER_EXIT calls confirms the report has been fully converted to the XML Publisher architecture, in which FND SRWINIT and FND SRWEXIT are no longer required.