Search Results get_released_quantity




Overview
Explore in AI Chat

Overview

OE_LIN_SCH is a scheduling utility package within the Oracle Order Management (OM) module of Oracle E-Business Suite. Its name reflects its purpose: OE (Order Entry) LINe SCHeduling. The package consolidates the server-side logic used to evaluate, validate, and retrieve scheduling quantities and attributes for order lines. It centralizes calculations that determine how much of an ordered quantity on a given line has been reserved, released, or otherwise made available for scheduling, and it exposes those values to the Order Management forms and internal scheduling engine.

The package is declared AUTHID CURRENT_USER, meaning its procedures execute with the privileges of the invoking user rather than the definer. This design is typical of OM utility packages that are called from both the standard Order Management application and from custom extensions, since it allows calling code to rely on its own schema privileges when accessing the referenced tables. The original header dates the package to the late 1990s (RDBMS port era), and it has been carried forward essentially unchanged into 12.1.1 and 12.2.2, indicating that its logic remains stable and embedded in the core scheduling flow.

Key Procedures and Functions

The ETRM metadata documents ten callable units. Their purposes are as follows:

  • GET_RESERVED_QUANTITY — Returns the quantity reserved against a given order line.
  • GET_RELEASED_QUANTITY — Returns the released quantity for a line, taking into account whether the line involves a configuration item. This is the procedure most directly associated with the user search term p_line_released_quantity, which is its OUT parameter.
  • CHECK_DETAILS_COMPLEXITY — Counts the scheduling detail rows associated with a line to indicate the complexity of its scheduling structure (for example, simple versus multi-shipment/detailed scheduling).
  • GET_SCHEDULING_QUANTITY — Aggregates reserved quantity, released quantity, and details-complexity count for a line in a single call, returning a composite view of its scheduling state.
  • CHECK_SCHEDULING_QUANTITY — Validates scheduling quantities (ordered, cancelled, reserved) against one another to confirm the line’s scheduling data is internally consistent.
  • GET_SCHEDULE_STATUS — Derives the scheduling status code and name for a line and the associated schedule action code, driving the schedule status indicator displayed in the UI.
  • GET_SCHEDULE_DB_Values — Populates the full set of scheduling-related database values for a line, including schedule date, demand class, ship-to site/contact, warehouse, shipment priority, ship method, ordered quantity, and unit of measure, along with the corresponding value IDs (svrid columns) needed by the forms layer.
  • VALIDATE_SCHEDULING_ATTRIBUTES — Validates the scheduling attributes (dates, warehouses, demand classes, and related fields) before they are committed to the database.
  • SCHEDULING_SECURITY — Applies scheduling-related security checks, enforcing data-access restrictions relevant to scheduling.
  • QUERY_RESERVED_QUANTITY — A query variant used to retrieve reserved quantity, typically for display or refresh operations.

Tables Accessed

The package operates against two documented tables through APPS synonyms:

  • SO_LINE_DETAILS — The core order-line detail table. It is the source of the line’s ordered, reserved, and released quantities and the scheduling attributes (schedule date, warehouse, ship-to, demand class, ship method, priority). Nearly every procedure reads from this table.
  • SO_LOOKUPS — The Order Management lookup table, used to resolve schedule status codes and names and to translate coded scheduling values into their display values.

The metadata indicates no write operations beyond the validation pathways; the package is predominantly a read/derive-and-return utility rather than a data-maintenance API.

Usage Notes

OE_LIN_SCH is an internal utility package rather than a public integration API. It is referenced by zero other packages in the ETRM dependency records, which means it is invoked directly by Order Management forms (notably the Sales Orders and Scheduling forms) and by the scheduling engine itself, rather than being called through other PL/SQL wrappers. Its procedures are most commonly triggered when a user enters, saves, or re-queries an order line: the form calls GET_SCHEDULING_QUANTITY or its individual getters to display reserved and released quantities, GET_SCHEDULE_STATUS to set the schedule status indicator, and GET_SCHEDULE_DB_Values to populate scheduling fields.

Because the package is AUTHID CURRENT_USER and not documented as a supported public interface, custom code should treat it as subject to change across releases. When extending Order Management, developers generally prefer supported APIs; where OE_LIN_SCH must be called, it should be invoked in the same context as the standard form—typically as a client-side form trigger or a tightly scoped server-side call—and should not be relied upon to commit or roll back scheduling data, as its documented role is to compute and validate rather than persist.