Search Results p_item_rev

Overview

APPS.BOM_BOMRWUIT_XMLP_PKG is a server-side PL/SQL package that backs the Oracle Bills of Material "Where Used" concurrent report — historically registered as report BOMRWUIT and driven by the XML Publisher (XMLP) template of the same name. The package implements the report's Before Report and After Report logic, holds the concurrent program's parameter values as package-level variables, and executes the bill implosion (where-used) processing that produces both single-level and multi-level results. Its $Header comment (BOMRWUITS.pls 120.1, 2008/01/07) identifies it as an Oracle-shipped, non-customized (noship) component of the BOM module.

The package accepts organization, item range, category range, effectivity date, and implosion options as parameters, and it writes qualifying parent-item relationships into temporary implosion tables for subsequent report retrieval and formatting. It is closely related to the standard BOM implosion engine, providing the report-specific wrapper around that engine, including multi-level (ML), single-level (SL), and user-exit variants.

Key Procedures and Functions

• BEFOREREPORT — Fires at report initialization; performs parameter setup, resolves the organization context (including the ALL_ORGS option and organization hierarchy), and prepares the environment before implosion executes.
• AFTERREPORT — Fires after report completion to release resources and conclude processing.
• GET_STATUS — Returns a status description for a revised item, deriving its meaning from the revised item sequence, the implemented flag, and the associated change notice.
• GET_ORGCODE — Accepts an ORGANIZATION_ID and returns the corresponding organization code, used to display the organization on the report output (the function matching the user's search term, "get_orgcode").
• CF_ALL_ORGSFORMULA — A report formula column that evaluates and returns the character flag indicating whether the report is running across all organizations.
• GET_PRECISION — Accepts a quantity precision value and returns the precision as a formatted VARCHAR2 string for report display.
• IMPLODER_USEREXIT — Executes the implosion using the user-exit path, taking the sequence, engineering/manufacturing flag, organization, implemented flag, display option, implosion levels, item, and implosion date, and returning error message and error code outputs.
• IMPLOSION — The core implosion routine; same input signature as IMPLODER_USEREXIT, producing error message and error code outputs.
• SL_IMPLODER — Implements single-level implosion processing.
• ML_IMPLODER — Implements multi-level implosion processing.

Tables Accessed

• BOM_IMPLOSION_TEMP and BOM_IMPLOSION_TEMP_S — temporary tables holding the implosion results written by the implosion procedures and read by the report query.
• ENG_REVISED_ITEMS — source of revised item and change-notice information used by GET_STATUS.
• MTL_PARAMETERS — supplies organization-level defaults and the organization code used in GET_ORGCODE.
• FND_ID_FLEX_STRUCTURES — identifies the item and category key flexfield structures used for range defaults.
• DUAL — used for single-row evaluations; DBMS_SQL — dynamic SQL for flexible report query construction; PLITBLM — the Oracle Reports PL/SQL table package used for report data structures.

Usage Notes

The package is invoked implicitly when the "Where Used" concurrent program runs; it is not intended for direct interactive execution. It can also be called from custom code — for example, to re-use GET_ORGCODE as an organization-code lookup — but because the package is Oracle-owned and versioned (120.1), customers should avoid modifying it directly. All parameters are reset at each concurrent request, with P_CONC_REQUEST_ID (default 0) carrying the requesting concurrent request identifier and P_SEQUENCE_ID (default 9999) separating implosion runs. Behavior is consistent across EBS 12.1.1 and 12.2.2, where the file remains in the APPS schema and is registered as an XML Publisher data source.