Results for “item_number”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MRP_EXCEPTION_SC is an Oracle EBS PL/SQL package owned by the APPS schema and classified under the ETRM as an OTHER API. The suffix "SC" denotes a server-side controller package, indicating that it functions as a supporting programmatic layer for the Oracle Material Requirements Planning (MRP) exception workbench — the interface through which planners review and act upon planning exceptions such as late orders, excess inventory, shortage conditions, and rescheduling recommendations. Rather than exposing a public transactional API for external integration, this package supplies the query, navigation, lock, and update mechanics that the exception enquiry form relies upon.

The package is documented as VALID and carries dependencies on the SYS schema through the STANDARD package, confirming it is a conventional compiled PL/SQL unit. It is referenced directly by MRP_EXCEPTION_DETAILS_V, a view, and is referenced by one other APPS package, indicating a role within the broader MRP exception subsystem rather than an isolated utility.

Key Procedures and Functions

The ETRM documents seven procedures and functions within MRP_EXCEPTION_SC:

• SAVE_AS — Persists the planner's current query criteria under a named saved query, supporting personalisation of exception searches.
• GROUP_BY — Applies or modifies grouping attributes so that exception records are aggregated or ordered according to planner-selected dimensions.
• UPDATE_ROW — Commits modifications made to an exception row, allowing the planner to record disposition or corrective action against a specific exception.
• LOCK_ROW — Obtains a row-level lock on an exception record prior to update, preserving concurrency integrity in a multi-planner environment.
• ITEM_NUMBER — Derives or resolves the item number associated with an exception, typically for display or validation purposes.
• SUPPLIER — Resolves supplier information attached to an exception where the planning condition relates to a purchasing document.
• SUPPLIER_SITE — Resolves the supplier site associated with the exception's sourcing context.

Parameter lists are not reproduced here; the functions are invoked internally by the exception form and its supporting view.

Tables Accessed

The package references four underlying objects through APPS synonyms:

• MRP_ITEM_EXCEPTIONS — The central exception repository. LOCK_ROW, UPDATE_ROW, and the resolution functions read and write rows in this table.
• MRP_FORM_QUERY_S — Stores form query definitions, supporting SAVE_AS and GROUP_BY behaviour so that planner search preferences persist across sessions.
• DBMS_SQL — Used for dynamic SQL construction, consistent with a flexfield-driven or user-configurable query model in the exception workbench.
• DUAL — Used for scalar evaluations and single-row lookups.

Usage Notes

MRP_EXCEPTION_SC is not a formally published interface; it should be treated as an internal, form-driven package. It is invoked when planners open the MRP exception workbench, query exceptions, group results, and record resolutions. Custom code should avoid calling it directly, as Oracle may alter its signature without notice. The APPS.MRP_EXCEPTION_DETAILS_V view depends on this package, so any modification to the package body can affect reporting built on that view. Where custom extensions require exception data, querying MRP_ITEM_EXCEPTIONS or the supplied view is the safer approach.