Search Results p_to_job

Overview

The APPS.WIP_WIPRELIN_XMLP_PKG package body supports the Oracle E-Business Suite Work in Process (WIP) shop floor execution reporting framework. It is the server-side PL/SQL implementation associated with an XML Publisher (XMLP) concurrent program — the "WIP Release Line" style report, identified by the internal short name WIPRELIN. The package accompanies a corresponding report definition (typically an .rdf or XML template) and provides the programmatic hooks that Oracle Reports and the concurrent manager invoke before, during, and after report execution.

Its principal business purpose is to dynamically assemble the SQL WHERE-clause fragments that constrain a WIP release line report by work order (job/entity name), production line, and date range. Parameters such as P_FROM_JOB and P_TO_JOB are supplied by the user through the concurrent program parameter form; the package converts those ranges into reusable SQL predicate strings that the report query appends to its base statement.

Key Procedures and Functions

The package body exposes six documented program units:

• LIMIT_JOBS — Returns a SQL predicate fragment restricting WE.WIP_ENTITY_NAME between the values supplied in P_FROM_JOB and P_TO_JOB. When only one bound is populated, an unbounded (>= or <=) predicate is generated; when neither is supplied, a blank fragment is returned. This is the unit directly relevant to the search term p_to_job, which serves as the upper bound of the work order range.
• LIMIT_LINES — Analogous function that builds a predicate on WL.LINE_CODE from P_FROM_LINE and P_TO_LINE, allowing the report to be restricted to a range of production lines.
• LIMIT_DATES — Builds a compound date-range predicate against RS.FIRST_UNIT_START_DATE and RS.LAST_UNIT_COMPLETION_DATE, supporting overlapping and fully contained interval logic between P_FROM_DATE and P_TO_DATE.
• AFTERREPORT — Report-level trigger executed after the report body has been processed; used for post-processing and cleanup.
• AFTERPFORM — Executes after the parameter form is submitted but before the main report query, allowing validation or derivation of parameter values.
• BEFOREREPORT — Fires before report execution, typically used to initialize package state and confirm the dynamically assembled predicates.

Tables Accessed

The documented metadata lists no directly referenced tables through APPS synonyms; the package operates primarily as a predicate generator rather than a data-access module. The predicate strings it returns reference aliases — WE (WIP entities / WIP_ENTITIES), WL (lines, associated with WIP_LINES), and RS (a release/detail alias) — which are resolved by the calling report query rather than within this package body. Consequently, no DML is performed here.

Usage Notes

This package is invoked indirectly by Oracle Reports and the XML Publisher concurrent program engine when the associated WIP release line report is run. It is not intended for direct invocation from custom code, although the LIMIT_* functions may be reused by custom code that calls the same aliases. Because the package builds predicates through string concatenation of parameter values, care should be taken if it is ever extended; behavior depends on parameters being supplied by trusted concurrent program inputs. The package is referenced by zero other packages in the documented metadata, confirming its role as a report-specific shell.