Search Results p_to_comp




Overview

APPS.WIP_WIPREORQ_XMLP_PKG is the packaged PL/SQL body that backs the Oracle Work in Process "WIP Reorder Point" style XML Publisher concurrent program (report short name WIPREORQ). It assembles the query fragments, substitution values, and formula columns that the Oracle Reports / XML Publisher runtime uses to produce a shop-floor exception report showing assemblies that are open, short of supply, or below reorder point within a specified date and sequence window. The package is a report driver rather than a business-rule engine: its responsibilities are limited to initialising the concurrent request context, deriving fragmentary WHERE and HAVING clauses from user-entered parameters, and computing precision and summary formulas for the output layout.

Key Procedures and Functions

Tables Accessed

The documented metadata lists no tables referenced through APPS synonyms, as the physical SQL is embedded in the report definition rather than the package. The dynamic fragments generated by LIMIT_LINES, OPEN_SHORT_LIMITER, and the LIMIT_*SUPPLY_TYPE functions nevertheless presuppose WIP and BOM query aliases such as WL (WIP lines), WRO (WIP requirements/operations), WRS (WIP resource scheduling), BCD (BOM calendar dates), and MSI (MTL system items) as implied by the header comments and formula text. These fragments are concatenated into the report query to filter the assembly, line, and supply-type ranges selected.

Usage Notes

WIP_WIPREORQ_XMLP_PKG is invoked exclusively by the concurrent program that runs the report; it is referenced by no other package. It should not be called directly from forms or custom code. Customers extending the report should treat LIMIT_BULK_SUPPLY_TYPE, LIMIT_VENDOR_SUPPLY_TYPE, and the LIMIT_* limiter functions as the supported extension points for supply-type filtering, and note that the package is marked noship in its header revision, indicating it is not shipped as a public API. Behaviour is version-tolerant across 12.1.1 and 12.2.2, as the body depends only on FND_GLOBAL and profile-derived precision values.