Search Results p_locator_data
Overview
APPS.WIP_WIPSULIN_XMLP_PKG is a PL/SQL package that supports the Oracle EBS Work in Process (WIP) concurrent program behind the "WIP Supply Line" XML Publisher (BI Publisher) report, identifiable by the XMLP suffix characteristic of reports migrated from the original Oracle Reports runtime to the XML Publisher engine. The package encapsulates the server-side report logic triggered through the Oracle Reports/XMLP execution model: its procedures drive the report lifecycle events that the report engine calls at defined points during execution, namely before the report body is produced, after the report has run, following the parameter form processing, and when applying row-level selection criteria. Its scope is therefore narrower than a general-purpose WIP transaction package; it exists to supply data retrieval filtering and report teardown behavior for a single concurrent report rather than to expose callable business APIs.
Key Procedures and Functions
The package exposes four documented procedures/functions, each corresponding to a standard Oracle Reports/XML Publisher report trigger:
- BEFOREREPORT — Executes the report-level Before Report trigger logic. It is the entry point for initializing report state, deriving session context, and preparing the data set required by the report query before any output is generated.
- AFTERPFORM — Runs the After Parameter Form trigger logic. It is invoked after the concurrent program parameters have been accepted and validated, and is used to condition the report based on the parameter values supplied at submission.
- LIMIT_BY_LINE_RANGE — A report-specific function that applies line-range restriction logic, most plausibly constraining the supply line records returned to the report to a bounded set determined by user-supplied parameters.
- AFTERREPORT — Runs the After Report trigger logic, providing cleanup or post-processing behavior once the report formatting and output have completed.
Per the ETRM metadata, the package references SYS.STANDARD and is itself self-referenced under APPS, and no explicit parameter lists are published; the procedures are documented by name and lifecycle placement only.
Tables Accessed
The ETRM 12.2.2 record documents no tables referenced through APPS synonyms for this package. This is consistent with a report-support package whose data extraction is defined either in the XML Publisher data template or in the SQL statements embedded in the package body, rather than in direct PL/SQL DML against base WIP tables. Where direct SQL is present, it is executed as the APPS schema user; APPS stores the report logic and relies on the APPS synonym layer for any base-table access.
Usage Notes
WIP_WIPSULIN_XMLP_PKG is not intended for direct invocation from forms or custom code. It is called by the Oracle Reports runtime host (or the XML Publisher concurrent program wrapper) as the WIP Supply Line report executes in the background, with each procedure firing at its corresponding report trigger. In Oracle EBS 12.1.1 and 12.2.2, the package remains VALID and should be treated as report infrastructure: modifications belong to a custom copy rather than to the seeded APPS object, since patch application may overwrite the original definition. The self-referential dependency entry reflects routine PL/SQL recompilation metadata rather than a functional recursive call. Customizations should preserve the four-trigger contract described above.
-
PACKAGE: APPS.WIP_WIPSULIN_XMLP_PKG
12.1.1
-
PACKAGE: APPS.WIP_WIPSULIN_XMLP_PKG
12.2.2
-
PACKAGE BODY: APPS.WIP_WIPSULIN_XMLP_PKG
12.1.1
-
PACKAGE BODY: APPS.WIP_WIPSULIN_XMLP_PKG
12.2.2
-
APPS.WIP_WIPSULIN_XMLP_PKG dependencies on FND_GLOBAL
12.1.1
-
APPS.WIP_WIPSULIN_XMLP_PKG dependencies on FND_GLOBAL
12.2.2