Search Results line_limiter

Overview

APPS.WIP_WIPLBOSP_XMLP_PKG is the packaged body that supports the WIP Line-Based Operations Schedule/Plan XML Publisher report (WIPLBOSP) in Oracle E-Business Suite 12.1.1 and 12.2.2. The package is classified under ETRM as OTHER and its header ($Header: WIPLBOSPB.pls 120.1 2008/01/31) confirms it belongs to the WIP (Work in Process) product family. Its business purpose is to assemble the dynamic WHERE-clause fragments used by the report's underlying SQL query so that the user-supplied parameters on the concurrent program's parameter form (job range, line range, assembly/item filter) are correctly translated into a runnable query. The report presents work order information organized by production line, and the package acts as the parameter-to-SQL translation layer that XML Publisher reports of this era conventionally relied upon.

Key Procedures and Functions

• JOB_LIMITER — Builds the SQL predicate that restricts the report by WIP entity name (job). It handles the permutations of the "from job" and "to job" parameters and returns the appropriate BETWEEN, greater-than-or-equal, or less-than-or-equal fragment, or a blank string when neither bound is supplied.
• LINE_LIMITER — This is the object the user searched for. FUNCTION LINE_LIMITER RETURN CHARACTER builds the SQL predicate that restricts the report by production line code (WL.LINE_CODE). Depending on whether the from-line and/or to-line parameters are populated, it returns a BETWEEN, >=, or <= fragment, or a single blank when no line restriction applies.
• C_DJ_LINE_LIMITERFORMULA — An XML Publisher "data join" style formula helper that returns a placeholder predicate (AND 1 = 2) when either the from-line or to-line parameter is supplied, and a blank string otherwise. It is used to control conditional joining of the line-based query block.
• C_ASSEMBLY_LIMITERFORMULA — Companion formula helper that returns AND when an item-level WHERE fragment (P_ITEM_WHERE) exists, and a blank otherwise, enabling conditional concatenation of the assembly restriction.
• BEFOREREPORT — The report's initialization trigger. It queries FND_ID_FLEX_STRUCTURES to resolve the key flexfield structure number for the MSTK (Inventory Item) flexfield under application 401, storing it for later use in the report logic.
• OPEN_PO_ONLY — Documented in the ETRM metadata; supports a runtime option controlling whether only open purchase-order-related data is included.
• AFTERREPORT — Standard XML Publisher after-report trigger for post-processing/cleanup.
• AFTERPFORM — Standard XML Publisher after-parameter-form trigger, used to validate or derive parameter values before the main query executes.

Tables Accessed

The only documented table reference is FND_ID_FLEX_STRUCTURES, read by BEFOREREPORT to obtain ID_FLEX_NUM for the MSTK key flexfield (APPLICATION_ID = 401, ID_FLEX_CODE = 'MSTK', ENABLED_FLAG = 'Y'). No DML is documented; the package is read-only with respect to the database. The report's own query, not part of this package, targets WIP tables such as WIP_ENTITIES, WIP_LINES, and related views through APPS synonyms.

Usage Notes

WIP_WIPLBOSP_XMLP_PKG is invoked indirectly when the WIP Line-Based Operations Schedule report concurrent program executes its XML Publisher template; the report engine calls BEFOREREPORT and AFTERPFORM, and the SQL query embeds the LIMITER functions to append dynamic predicates. The package is referenced by zero other packages, confirming it is a report-specific, self-contained utility rather than a shared API. Customizations should not modify the packaged body; instead, extensions should follow the standard EBS report customization (copy-and-rename) practice. Because the LIMITER functions concatenate literal parameter values into SQL, character-based line and job parameters are interpreted lexically, and users should be aware of collation and trimming behavior when specifying ranges.