Search Results populate_flow_summary

Overview

The APPS.FLM_LINEARITY_REPORT package is a PL/SQL database package that supports the flow manufacturing linearity reporting capability within Oracle E-Business Suite. Linearity reporting is a core analytical function in Oracle Flow Manufacturing, used by production planners and shop-floor supervisors to measure how evenly production output is distributed across a scheduling horizon. Rather than measuring only total quantity produced, linearity analysis evaluates whether units were completed at a consistent rate against the schedule, which is a critical indicator of production stability and takt-time adherence.

The package is declared with AUTHID CURRENT_USER, meaning its procedures execute with the privileges of the invoking database user rather than as the definer. The package carries a source header revision of 115.1, originally shipped in November 2002 and designated as a "ship" version, indicating it is a production-seeded object delivered with the application. It is owned by the APPS schema and is classified as an "OTHER" API, meaning it is not part of a formally published public API family but is an internal reporting package. The only publicly declared program unit is populate_flow_summary, which indicates the package exists primarily to stage or populate data for downstream linearity report rendering.

Key Procedures and Functions

The package exposes a single documented procedure, populate_flow_summary. Its purpose is to assemble and populate the summary data set that drives the flow linearity report. Invoking this procedure causes the package to gather production flow information for a defined scope and aggregate it into the structure consumed by the reporting layer.

Although the procedure's full parameter list is documented in the source header, all parameters operate as filter and control values that define the scope of the summary: a line range, a schedule group, an operating unit (organization) identifier, a date range covering the beginning and end of the reporting window, an identifying query ID used to tag a specific report run, and an OUT return status parameter used to signal success or failure to the caller. The x_return_status output allows calling code to detect and react to processing errors. Because the majority of input parameters are mandatory scope identifiers, the procedure is designed to be invoked for a specific, bounded slice of production data rather than as a global batch refresh.

Tables Accessed

The metadata documents four tables accessed through APPS synonyms, all of which are consistent with a flow manufacturing linearity data-gathering routine:

• WIP_FLOW_SCHEDULES — the primary source of scheduled flow production quantities and dates used to establish the expected build rate across the reporting window.
• WIP_LINES — supplies the production line definitions required to bound the report by line range and to associate schedules with their physical or logical flow line.
• WIP_SCHEDULE_GROUPS — provides the schedule group context used to filter and organize the flow schedules included in the summary.
• MRP_FORM_QUERY — stores the query definition and parameterization associated with the report run, keyed by the query ID, allowing the report to persist and reuse the selection criteria used to generate the summary.

Taken together, these tables indicate that the procedure reads schedule and line master data, filters it by the supplied scope, and writes results into a summary structure for subsequent report retrieval.

Usage Notes

populate_flow_summary is typically invoked as a supporting routine behind a flow manufacturing linearity report, whether triggered from an Oracle Forms-based report submission or a concurrent program that first populates the summary before the report output is produced. The presence of the query ID parameter strongly suggests it is called in a pattern where a form captures selection criteria, persists them to MRP_FORM_QUERY, and then passes the resulting identifier to this procedure.

Because the package is documented as being referenced by one other package but does not itself appear as a top-level published API, customizations should call it only through the same pathways the standard flow manufacturing reports use. Developers extending or debugging linearity reporting must respect the AUTHID CURRENT_USER behavior, ensuring the invoking user has access to the underlying WIP and MRP objects, and must supply a valid date range, line range, schedule group, and organization ID, since these are the mandatory filters that define the scope of the summary population.