Search Results get_flow_quantity

Overview

MRP_FLOW_SCHEDULE_UTIL is a utility package in the Oracle EBS Applications schema (APPS) that supports the maintenance, querying, and processing of flow schedules in a flow manufacturing environment. Flow schedules represent the sequenced production of assemblies on a line, and WIP_FLOW_SCHEDULES is the primary repository for the header and line records that describe these schedules, including quantities, completion dates, build sequences, and demand references.

The package belongs to the UTIL API classification, indicating that it is an internal helper rather than a published business API. It encapsulates the low-level operations required to insert, update, delete, lock, and query flow schedule rows, as well as to compute derived values and to perform post-schedule processing such as relieving demand and rolling schedules. It is referenced by thirteen other packages, which confirms its role as a shared service layer used throughout the flow manufacturing and planning modules rather than as an entry point invoked directly by end users.

The header comment shows the package body originates from the MRPUSCNS.pls script (version 120.1), reflecting its lineage in the MRP/flow scheduling code base. The specification also defines a large set of named constants used to map attribute positions to visual attributes and columns, which is characteristic of a generic attribute-handling utility that normalizes incoming data before it is written to the schedule tables.

Key Procedures and Functions

• CLEAR_DEPENDENT_ATTR and APPLY_ATTRIBUTE_CHANGES — manage the impact of attribute edits on dependent fields, preserving data integrity when descriptive or key attributes change.
• COMPLETE_RECORD and POPULATE_FLOW_SUMMARY — finalize a record or populate summary values after the core fields have been supplied.
• CONVERT_MISS_TO_NULL — normalizes missing or defaulted values to NULL, standardizing how absent data is stored.
• UPDATE_ROW, INSERT_ROW, DELETE_ROW, QUERY_ROW, and LOCK_ROW — the standard data manipulation primitives that read, write, and lock flow schedule rows with controlled concurrency.
• GET_VALUES and GET_IDS — retrieve attribute values and identifier lists used to drive subsequent processing.
• UPDATE_QUANTITY — adjusts schedule quantities; this is the procedure most closely associated with the search term "get_flow_quantity," which relates to reading or deriving the current flow quantity on a schedule record.
• DELETE_FLOW_ROW and DELETE_FLOW_SCHEDULES — remove individual rows or entire schedules, including their dependent detail.
• ROLL_FLOW_SCHEDULES — advances or re-sequences flow schedules, typically during rescheduling or planning runs.
• ITEM_WHERE_CLAUSE and CATEGORY_WHERE_CLAUSE — build dynamic WHERE clause fragments so that item and category filtering can be applied to flow schedule queries.
• LINE_SCHEDULE and POST_SCHEDULE_UPDATE — carry out line-level scheduling logic and the follow-on updates required once a schedule has been created or changed.

Tables Accessed

The package reads and writes WIP_FLOW_SCHEDULES, the central table holding flow schedule records. It references BOM_CALENDAR_DATES, BOM_OPERATIONAL_ROUTINGS, and MRP_SCHEDULING_RULES to obtain calendar, routing, and scheduling rule information needed to place and sequence schedules correctly. Execution-side data comes from FLM_EXE_LOT_NUMBERS, FLM_EXE_OPERATIONS, FLM_EXE_REQ_OPERATIONS, and FLM_EXE_SERIAL_NUMBERS, which supply lot, operation, and serial number context for manufactured units. Demand relief and recommendation processing use MRP_RELIEF_INTERFACE, MRP_RELIEF_INTERFACE_S, and MRP_RECOMMENDATIONS. Item filtering relies on MTL_ITEM_CATEGORIES and MTL_CATEGORIES_KFV, while MRP_FORM_QUERY and MRP_FORM_QUERY_S store the query definitions that drive the form-based schedule search.

Usage Notes

MRP_FLOW_SCHEDULE_UTIL is not intended for direct invocation by end users. It is called by Oracle Forms and by concurrent programs within the flow manufacturing and planning modules, and it is referenced by thirteen other PL/SQL packages. Customizations that need to manipulate flow schedules should generally call the sanctioned business APIs rather than this UTIL package, because its procedures perform physical row operations without the full validation and event propagation applied at the API layer. When it is used, it must run as APPS or under a user with appropriate privileges on the WIP_FLOW_SCHEDULES and related tables.