Search Results quantity_rem_in_prev_p

Overview

WIP_WIPDJDSP_XMLP_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that serves as the server-side program unit for the Discrete Job Dispatch Report (WIPDJDSP), a Work in Process (WIP) reporting concurrent program delivered as an Oracle Reports XML Publisher (XMLP) report. The package encapsulates the report's PL/SQL logic, allowing the XML Publisher/BI Publisher report definition to invoke packaged functions and formulas rather than embedding logic directly in the report template. It is classified as OTHER in the ETRM metadata, meaning it is not a public application programming interface and should not be treated as a supported integration point. The package header declares a set of public package variables (including P_CONC_REQUEST_ID, ORG_ID, SORT_CODE, FROM_DATE, TO_DATE, P_ITEM_DATA, P_FROM_DEPT, P_TO_DEPT, P_QTY_PRECISION, P_INCLUDE_UNRELEASE, P_DEBUG, and P_SCHEDULE_GROUP) that hold report parameters and derived values for the duration of a report run, together with eleven documented procedures and functions. These elements support the report's requirement to display discrete job dispatch information restricted by organization, date range, item, department, and schedule group criteria, and to compute remaining quantities across operations.

Key Procedures and Functions

The package exposes eleven documented program units. BEFOREREPORT and AFTERREPORT perform report-level initialization and cleanup, including resolution of the organization context and other setup values before output is generated. AFTERPFORM executes after the report's parameter form processing, enabling derived values to be established once user-entered parameters are available. DYNAMIC_ORDER_BY returns a character string used to build the report's ORDER BY clause dynamically, permitting the sort order to vary at runtime based on the report parameter SORT_CODE. DATE_LIMITER returns a character string that constructs the SQL predicate restricting results to the FROM_DATE and TO_DATE range. DEPARTMENT_LIMITER returns a character string that builds the SQL predicate limiting results to the department range supplied in P_FROM_DEPT and P_TO_DEPT; this is the function relevant to the search term "department_limiter" and it is invoked by the report's data model to inject department filtering into the query. STATUS_LIMITER returns a character string that supplies the predicate restricting jobs by status. C_LIMITER returns a VARCHAR2 string that conducts additional conditional filtering, typically composing the schedule group and unreleased-job criteria. C_QUANTITY_IN_PREVFORMULA derives the cumulative quantity from prior operations for a given work entity and operation sequence. QUANTITY_REMAININGFORMULA computes the quantity remaining for an operation from scheduled, in-queue, and running quantities together with the prior-operation quantity. QUANTITY_REM_IN_PREV_P exposes the package-level state variable QUANTITY_REM_IN_PREV.

Tables Accessed

The metadata documents two referenced tables accessed through APPS synonyms: FND_ID_FLEX_STRUCTURES and WIP_OPERATIONS. FND_ID_FLEX_STRUCTURES is the key flexfield definition table, read to determine the item flexfield structure and segment configuration so that item identifiers can be correctly interpreted and displayed; the package variable item_id_flex_num corresponds to this purpose. WIP_OPERATIONS is the core WIP table holding discrete job operation sequences, departments, and operation-level quantities; it supplies the department, status, and quantity data that the limiter functions and quantity formulas operate on. Additional WIP and inventory tables may be referenced through the report's underlying query, but only these two are documented for the package.

Usage Notes

WIP_WIPDJDSP_XMLP_PKG is invoked indirectly when the Discrete Job Dispatch Report concurrent program is submitted. The Oracle Reports XML Publisher engine calls BEFOREREPORT, AFTERPFORM, the limiter functions, and the quantity formulas as the report executes; end users never call the package directly. Because the package is referenced by zero other packages and is not classified as a public API, it should not be invoked from custom code, and any customizations should be applied through the supported report or concurrent program configuration rather than by modifying the package. In EBS 12.1.1 and 12.2.2 the package resides in the APPS schema and is shipped with a version header dated 2008, reflecting a mature, stable report component.