Search Results flm_linearity_report

Overview

FLM_LINEARITY_REPORT is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite. Its designation as a package body indicates that the object contains the implementation code for a corresponding package specification of the same name. In the ETRM repository it is classified as an OTHER API, meaning it is not a public, supported programmatic interface but rather an internal utility used to support a specific functional deliverable.

The name and dependency profile identify the object as belonging to the Flow Manufacturing (FLM) product family. Flow Manufacturing is the EBS module used to run mixed-model, demand-based production lines, and a central concept within that module is production linearity — the ability to sequence and level output so that units are produced at an even rate across a schedule group rather than in erratic batches. FLM_LINEARITY_REPORT supports that business function by assembling the data required for the Linearity Report, which compares planned takt or scheduled quantities against actual completed quantities at the line and schedule-group level. The package therefore serves as the data-gathering layer between the shop-floor transaction tables and the reporting interface presented to production managers and line supervisors.

Key Procedures and Functions

The ETRM metadata documents a single procedure or function within this package body:

• POPULATE_FLOW_SUMMARY — As the name implies, this routine populates a flow summary data set. In the Flow Manufacturing reporting context, this means it collects and consolidates the quantities that the linearity report requires, deriving summarized counts from the schedule-level and line-level source tables and staging them for display or downstream calculation. It is the sole documented entry point in the package, indicating that the remaining logic in the body consists of private helper code invoked only from within POPULATE_FLOW_SUMMARY.

No parameter lists are documented in the ETRM entry, and none should be assumed. The procedure is intended for internal invocation by the Flow Manufacturing reporting infrastructure rather than by external callers.

Tables Accessed

The package body references four application tables, all resolved through APPS synonyms: MRP_FORM_QUERY, WIP_FLOW_SCHEDULES, WIP_LINES, and WIP_SCHEDULE_GROUPS.

• WIP_FLOW_SCHEDULES — Stores the flow schedule header information, including the scheduled start and completion dates and quantities for each flow schedule. This is the primary source for the planned side of the linearity comparison.
• WIP_LINES — Holds the definition of the production lines on which flow schedules are executed. Line identity is essential because linearity is measured per line and per time bucket.
• WIP_SCHEDULE_GROUPS — Defines the schedule groups that organize flow schedules for reporting and sequencing purposes. Linearity reporting is typically performed at the schedule-group level, so this table supplies the grouping hierarchy.
• MRP_FORM_QUERY — A query-definition table used by MRP and related planning forms to store saved query criteria. Its presence suggests the package may honor a stored query definition or retrieve query metadata when building the report data set.

The dependency listing also shows a reference to the package specification FLM_LINEARITY_REPORT itself, confirming that the body implements the declared interface, and to the STANDARD package under SYS, indicating use of standard Oracle-supplied utility functions.

Usage Notes

FLM_LINEARITY_REPORT is not referenced by any other database object, which establishes it as a top-level consumer rather than a reusable library. Its most probable invocation paths are the Flow Manufacturing Linearity Report form or an associated concurrent program that executes the report and writes its output to a report file or staging table. Because POPULATE_FLOW_SUMMARY performs the data preparation work, it is normally called once per report execution, with the caller supplying the runtime selection criteria such as line, schedule group, and date range.

From a customization and support perspective, the package should be treated as an internal EBS object. It is not published in the Oracle integration repository as a supported API, so direct calls from customer code are discouraged; the supported integration points for Flow Manufacturing reporting lie in the standard report and concurrent program definitions. When troubleshooting discrepancies in linearity output, the WIP_FLOW_SCHEDULES, WIP_LINES, and WIP_SCHEDULE_GROUPS tables should be examined first, since they supply the values that POPULATE_FLOW_SUMMARY consolidates. The same structure is present in both Oracle EBS 12.1.1 and 12.2.2, so remediation and analysis steps are consistent across the two releases.