Search Results weekly_plan_groupformula

Overview

FLM_FLMRFLIN_XMLP_PKG is the generated PL/SQL package body that supports the Oracle Flow Manufacturing "Linearity Report" concurrent program (report short name FLMRFLIN) in Oracle E-Business Suite 12.1.1 and 12.2.2. The package is owned by the APPS schema, and Oracle's ETRM classifies it under the generic "OTHER" API classification, confirming that it is not a public, externally supported API but rather an internal report implementation. Its documented header identifies it as "FLMRFLINB.pls 120.1 2007/12/31", indicating a report-generation package rather than an interface or business-logic package.

The report analyzes production linearity — the degree to which actual production is distributed evenly across days and weeks relative to the scheduled plan — for a given organization, schedule group, and date range. The package is responsible for preparing report parameters, invoking the underlying linearity calculation logic, and then formatting the extracted data into weekly and daily plan, actual, variance, and linearity columns for the Oracle Reports (XML Publisher) runtime engine.

Key Procedures and Functions

The ETRM metadata documents 132 procedures and functions, which is characteristic of an Oracle Reports XMLP package: most entries are single-line "formula" functions called by the report layout to compute or format individual columns. The most significant are:

• BEFOREREPORT — The primary initialization routine. It formats the user's date-range parameters (P_DATE_FROM, P_DATE_TO), derives the report option display name (Summary or Detail) from P_REPORT_OPTION, derives the sort option name (Week or Line) from P_SORT_OPTION, resolves P_ORGANIZATION from ORG_ORGANIZATION_DEFINITIONS using P_ORG_ID, reconciles the P_LINE_FROM / P_LINE_TO line range, obtains a new P_QUERY_ID from MRP_FORM_QUERY_S, calculates the week-start offset by comparing the first day-of-week of the report start date against a reference date, and finally calls FLM_LINEARITY_REPORT.populate_flow_summary to populate the report's staging data.
• AFTERREPORT — Cleanup routine that deletes the staging rows created for the report run from MRP_FORM (and, by association, the MRP_FORM_QUERY data keyed by P_QUERY_ID).
• AFTERPFORM — Post-parameter-form trigger executed once the user submits the report parameter form.
• WEEKLY_PLANFORMULA, WEEKLY_ACTUALFORMULA, WEEKLY_VARFORMULA, WEEKLY_LINFORMULA — Column-level formula functions that return the weekly plan quantity, actual quantity, variance, and linearity percentage for the layout.
• DAY1_VAR_GROUPFORMULA through DAY7_VAR_GROUPFORMULA — Seven group-level formula functions that compute the variance value associated with each day of the week shown in the report.
• WEEKLY_PLAN_GROUPFORMULA, WEEKLY_ACTUAL_GROUPFORMULA, WEEKLY_VAR_GROUPFORMULA, WEEKLY_LIN_GROUPFORMULA — Weekly aggregate group formulas.
• DAY1_LIN_GROUPFORMULA, DAY2_LIN_GROUPFORMULA, … — Day-of-week linearity group formulas continuing the same pattern, with the remaining documented functions following the same naming convention for the balance of the daily columns.

Tables Accessed

The documented tables directly referenced by this package are:

• MRP_FORM_QUERY_S — The sequence used in BEFOREREPORT to obtain a unique P_QUERY_ID for each execution. This identifier isolates one report run's staging data from concurrent runs.
• MRP_FORM_QUERY — The staging table populated by the underlying FLM_LINEARITY_REPORT.populate_flow_summary call; the report's queries read from it (and from MRP_FORM) using P_QUERY_ID.
• MRP_FORM — Deleted from in AFTERREPORT to purge the current run's rows. Additionally, BEFOREREPORT reads ORG_ORGANIZATION_DEFINITIONS (via the APPS synonym) to resolve the organization name, and reads DUAL for the day-of-week offset arithmetic.

Usage Notes

This package is not intended for direct invocation. It is registered automatically by Oracle Reports/XML Publisher as the PL/SQL library for the FLMRFLIN report, and its BEFORE REPORT, AFTER REPORT, and formula triggers are invoked by the report runtime. In a "get_var" search context, callers looking for parameter or column value retrieval will find that value access is accomplished through the individual formula functions rather than a generic getter; external programs should not call those functions directly. Because the package is classified as OTHER and is marked with the internal "noship" header, customers and integrators should treat it as unsupported for extension. Any custom reporting requirement on production linearity should be implemented against the underlying FLM_LINEARITY_REPORT API instead of this generated package.