Search Results wip_wiprertg_xmlp_pkg

Overview

APPS.WIP_WIPRERTG_XMLP_PKG is a PL/SQL package that supports the Oracle Work in Process (WIP) reporting infrastructure within Oracle E-Business Suite. The package name convention combines the WIP application prefix with the "XMLP" suffix, indicating it is bound to an XML Publisher (BI Publisher) based concurrent program. Its role is to supply report-level logic — parameters, layout groupings, and runtime computations — to the associated WIP concurrent report. The package is registered as VALID in the APPS schema, and its documented API classification is OTHER, distinguishing it from standard public APIs; it is intended for internal use by the report engine rather than direct customer invocation. Dependency metadata shows the package references SYS.STANDARD (the PL/SQL base package) and is self-referenced, and it is referenced by no other documented packages, consistent with its role as a report-specific utility package rather than shared application infrastructure.

Key Procedures and Functions

The package exposes six documented procedures and functions, typical of an XML Publisher report data definition package:

• BEFOREREPORT — Executed prior to report generation; used to initialize package-level state, set up session contexts, or prepare global variables consumed by the report queries.
• ASSEMBLY_SPEC — Returns or formats assembly-level specification information for the report output, likely supplying the assembly grouping or header logic.
• LINE_SPEC — Parallel to ASSEMBLY_SPEC, provides line-level specification data used to build the repeating row structure of the report.
• DATE_RANGE — Derives or validates the date range applied to the report, ensuring that the parameter window is correctly passed to the underlying query.
• AFTERREPORT — Executed after the report completes; commonly used for cleanup, post-processing, or finalization of report-level values.
• AFTERPFORM — Fires after the parameter form has been submitted, allowing the package to adjust or validate parameters before the main report logic executes.

These entry points follow the standard Oracle Reports/XML Publisher package pattern and are not documented as accepting externally supplied parameters in the ETRM record.

Tables Accessed

The ETRM metadata documents no tables referenced via APPS synonyms for this package. This suggests the package itself performs minimal or no direct SQL against application tables, instead serving as a formatting and control layer while the report's underlying query — embedded in the XML Publisher data template — retrieves WIP data such as assembly requirements, job details, and resource transactions. Where SQL is present, dependencies are resolved through the APPS synonym layer, but no specific table list is captured in the supplied record.

Usage Notes

WIP_WIPRERTG_XMLP_PKG is invoked automatically by the concurrent manager when the corresponding WIP XML Publisher concurrent program is submitted. The Oracle Reports-style procedures — BEFOREREPORT, AFTERPFORM, and AFTERREPORT — are called by the report runtime at their respective lifecycle stages, while ASSEMBLY_SPEC, LINE_SPEC, and DATE_RANGE are called during output generation. It is not intended for direct invocation from forms, custom concurrent programs, or ad hoc PL/SQL; because its classification is OTHER and it is referenced by no other packages, external code should not bind to it. Compatibility spans Oracle EBS 12.1.1 and 12.2.2, though the package body is delivered as Oracle proprietary and confidential information, so modifications are neither supported nor advisable. Administrators troubleshooting the associated WIP report should treat this package as an internal artifact and direct investigations to the concurrent program definition, its parameters, and the XML Publisher template.