Search Results p_resource_to




Overview
Explore in AI Chat

Overview

APPS.BOM_BOMRWURS_XMLP_PKG is the generated PL/SQL wrapper package for the Oracle E-Business Suite concurrent program "Bill of Material / Resource Usage Report" (short name BOMRWURS). It belongs to the Oracle Bills of Material (BOM) product family and is classified under the generic API category OTHER, meaning it is not a published, supported business API but rather an internal runtime artifact created by Oracle Reports and XML Publisher when a report is registered as a concurrent program.

The package exposes the report's parameter bindings as package-level variables and provides the standard report trigger functions that Oracle Reports executes at defined points in the report lifecycle. It serves no independent business logic of its own: its purpose is to marshal concurrent program parameters, establish session context, and hand control to the underlying report definition so that the Bill of Material / Resource Usage Report can be produced for a specified organization, resource range, and effective date.

The user's search term, p_eng_bill_flag, maps directly to the package variable P_ENG_BILL_FLAG VARCHAR2(40). This parameter drives whether the report presents engineering bills of material rather than (or in addition to) manufacturing bills, and is therefore central to the report's selection logic.

Key Procedures and Functions

The package declares three documented program units, all of which are standard Oracle Reports trigger entry points:

  • P_DEBUGVALIDTRIGGER — A validation trigger associated with the debug parameter. It governs acceptance of the debug flag supplied at submission time, ensuring that only valid values are honoured before the report proceeds. This corresponds to the P_DEBUG variable, a two-character switch used to emit diagnostic information during report execution.
  • BEFOREREPORT — Executes once, before the report's first data fetch. It is the conventional place to initialise session state, including the organization context derived from P_ORG_ID, and to apply the parameter values (P_RESOURCE_FROM, P_RESOURCE_TO, P_EFFECTIVE_DATE, P_QTY_PRECISION, P_ENG_BILL_FLAG) before the query is opened.
  • AFTERREPORT — Executes once after all report output has been produced. It performs any required cleanup or post-processing, and returns control to the concurrent manager.

Each function returns BOOLEAN, in keeping with Oracle Reports' trigger signature. The package also declares P_CONC_REQUEST_ID NUMBER := 0, populated by the concurrent manager with the request identifier for the current run.

Tables Accessed

The ETRM metadata for this package records no directly referenced tables via APPS synonyms. This is expected for a generated report wrapper: the SQL statements that read BOM and resource data reside in the associated report definition (the .rdf / XML template), not in the PL/SQL package text. Any tables the report queries — principally bills of material, bill components, and resource usage structures — are therefore resolved through the report's own query, using the organization and effective-date parameters set by BEFOREREPORT. Readers should consult the report definition itself for the authoritative table list.

Usage Notes

This package is invoked indirectly. A user submits the Bill of Material / Resource Usage Report from the concurrent programs form or the Requests window; the concurrent manager then executes the registered report, which calls BEFOREREPORT and AFTERREPORT at the appropriate points. The package is not intended to be called from custom PL/SQL, nor is it a documented integration interface.

Because the package is OS (Oracle Support) owned and its body is regenerated whenever the report is modified in Oracle Reports, customisations should never be applied to it — they would be overwritten on patching or upgrade, and the behaviour is identical across EBS 12.1.1 and 12.2.2. Where additional selection criteria are required, the supported approach is to copy the report and register a custom concurrent program rather than alter BOM_BOMRWURS_XMLP_PKG.

When diagnosing output, the P_DEBUG parameter is the primary lever: enabling it triggers the debug validation path and increases trace verbosity, while P_ENG_BILL_FLAG determines whether engineering rather than manufacturing bill structures are reported.