Search Results flm_flmrfsch_xmlp_pkg

Overview

FLM_FLMRFSCH_XMLP_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the scheduling report associated with Oracle Flow Manufacturing. The package name follows the standard EBS report integration convention: the XMLP suffix identifies it as a report-level package generated to support an XML Publisher (BI Publisher) concurrent program, while the FLMRFSCH component aligns it with the Flow Manufacturing report invoked by the corresponding concurrent executable. In EBS 12.1.1 and 12.2.2, XML Publisher report definitions are frequently implemented as PL/SQL packages that combine the data model logic and report layout triggers, allowing the concurrent manager to execute report logic through the standard report submission framework.

The package is documented as VALID in the ETRM metadata, indicating that it has been compiled successfully against its dependencies in the APPS schema. Its API classification is recorded as OTHER, distinguishing it from standard public APIs and confirming that it is intended as an internal report-support component rather than a callable integration interface.

Key Procedures and Functions

The ETRM metadata documents three procedures or functions within this package. Their names reflect the Oracle Reports/XML Publisher report trigger model, where the report engine calls package entry points at defined phases of report execution:

• BEFOREREPORT — Executes before the main report data is generated. In the XML Publisher report package pattern, this procedure typically initializes package-level state, resolves run-time parameters and session context, and prepares the environment for data retrieval.
• AFTERREPORT — Executes after report data generation completes. It is conventionally used for post-processing, cleanup of temporary state, and finalizing any values needed for the output document.
• AFTERPFORM — Executes after the parameter form or parameter validation phase, before the main data query. This is the standard point at which validated report parameters are captured and made available to the report logic.

No parameter lists or return types are documented in the ETRM metadata, and none should be assumed. Each entry point exists to service the report execution lifecycle rather than to expose business functionality to external callers.

Tables Accessed

The documented table reference for this package is FND_ID_FLEX_STRUCTURES, accessed through an APPS synonym. This is the Oracle Application Object Library (FND) table that stores key flexfield structure definitions. Within a Flow Manufacturing report context, this reference is consistent with report logic that must resolve flexfield structure information — for example, to determine the structure of a key flexfield used in report parameters or output columns, or to validate a structure name against the report's input parameters before the data query is executed. The metadata lists no other table dependencies, indicating that the package's primary persistence access is limited to this FND reference within the documented dependency set.

Usage Notes

FLM_FLMRFSCH_XMLP_PKG is not intended for direct invocation by custom code. It is a report-support package executed by the Oracle EBS concurrent processing framework when the associated XML Publisher report is submitted. In EBS 12.1.1 and 12.2.2, such packages are registered against a concurrent program definition, and the report engine calls the BEFOREREPORT, AFTERPFORM, and AFTERREPORT entry points automatically as part of the report lifecycle.

The ETRM metadata records that this package is referenced by zero other packages and that it is self-referenced within its own dependency listing, confirming that it functions as a leaf-level report component. Because it is a report-owned package rather than a published API, it should be treated as subject to change with the report definition. Customizations requiring modifications to report behavior should be implemented through supported extension mechanisms or report copies rather than by altering this package directly. When troubleshooting report failures, the BEFOREREPORT and AFTERPFORM entry points are the appropriate locations to trace parameter resolution, while AFTERREPORT should be examined for post-generation cleanup issues.