Results for “save_as”

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

Overview

The APPS.MRP_EXCEPTION_SC package body is a server-side PL/SQL component in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that supports the Oracle MRP/MPS planning exception workflow. Its primary business function is to collect, aggregate, and persist exception counts derived from planning exception messages generated during a plan run. These exception messages alert planners to conditions requiring attention, such as late supply, excess inventory, or shortage risks. Rather than displaying raw exception rows, the package condenses the results into summary counts that can be presented to the user through the Planner Workbench summary interface and stored in the MRP_FORM_QUERY structure for later retrieval. The package is classified as an OTHER API, meaning it is an internal supporting utility rather than a public, documented integration interface. The header comment indicates a maintenance revision dated 2006 and references bug fixes, confirming its role as a long-standing internal object within the MRP schema family.

Key Procedures and Functions

The package exposes seven documented procedures and functions:

• GROUP_BY — The core aggregation routine. It inserts selected exception counts into MRP_FORM_QUERY using dynamically constructed SQL. The ALL_ORGS parameter, when supplied, controls whether the query spans all organizations or restricts results to the planned organization. This is the routine most directly associated with the user search term all_orgs.
• SAVE_AS — Persists the current query definition, allowing a planner to store and later re-run a named exception view.
• UPDATE_ROW — Modifies an existing stored query row, typically when the user edits a saved exception view.
• LOCK_ROW — Acquires a row-level lock to preserve consistency during concurrent modification of a stored query.
• ITEM_NUMBER — Resolves or validates item-related identifiers used in exception filtering.
• SUPPLIER — Resolves supplier context for exceptions relating to sourcing or purchasing.
• SUPPLIER_SITE — Resolves supplier site context for site-specific exception conditions.

Tables Accessed

The package reads and writes the following objects through APPS synonyms:

• MRP_FORM_QUERY / MRP_FORM_QUERY_S — The destination for aggregated exception counts. The sequence MRP_FORM_QUERY_S.NEXTVAL supplies the exception_id and related identifiers.
• MRP_ITEM_EXCEPTIONS — The source view (MRP_ITEM_EXCEPTION_V) from which exception counts are selected and summed.
• DUAL — Used to retrieve the next sequence value.
• DBMS_SQL — Referenced for dynamic SQL execution; the original DBMS_SQL cursor logic is commented out in favor of EXECUTE IMMEDIATE.

Usage Notes

MRP_EXCEPTION_SC is an internal supporting package invoked primarily by the Planner Workbench exception summary forms and by related MRP packages. It is referenced by one other package in the EBS codebase, indicating a tightly scoped dependency chain. The dynamic SQL construction in GROUP_BY is significant: the query string is assembled at runtime and bound using EXECUTE IMMEDIATE with bind variables, including the all_orgs value. This design permits flexible grouping and organization scoping without hard-coding each variant. Because the package is classified as OTHER and is not a public API, custom extensions should avoid direct dependence on its internal signatures; the recommended integration surface remains the standard MRP exception views and concurrent programs.