Search Results mrp_get_bis_values




Overview
Explore in AI Chat

Overview

APPS.MRP_GET_BIS_VALUES is a PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema that supports the Oracle Manufacturing "Business Intelligence System" (BIS) reporting layer for Oracle Material Requirements Planning (MRP). Its specific role is to resolve derived values that the MRP BIS views require but cannot compute directly through standard joins — most notably forecast-related error metrics and expected ship dates associated with planning recommendations and pegging records.

The package is classified as VALID in the ETRM metadata and its API classification is listed as OTHER, indicating that it is not part of a documented public interface intended for customer extension. Consistent with this classification, the package carries no published parameter contract in the ETRM record and exposes limited callable logic. The package body is present alongside the package specification, and dependency information confirms it is a leaf-level utility object that other MRP objects depend upon rather than one that initiates business processes itself.

In Oracle EBS 12.1.1 and 12.2.2, MRP BIS views such as MRP_BIS_FORECAST_V, MRP_BIS_FORECAST_SET_V, and MRP_BIS_LATE_ORDERS_V rely on this package to present forecast accuracy and order lateness information in planning inquiry screens. The dependency metadata confirms that these three views reference APPS.MRP_GET_BIS_VALUES, making the package a supporting component of the planning workbench's analytical reporting rather than of the planning engine itself.

Key Procedures and Functions

  • FORECAST_ERROR — Computes a forecast error measure used by the BIS forecast views. This logic supplies the variance between forecast quantities and actual demand consumed against them, enabling the forecast accuracy displays in the MRP planning workbench.
  • EXPECTED_SHIP_DATE — Derives an expected ship date for planning recommendations. This value supports the late-orders reporting view by providing the date against which order lateness is assessed.

The ETRM documentation lists exactly two documented procedures or functions. No parameter lists are published in the metadata, and no signatures should be assumed. Any existing callers invoke these routines as part of view definitions rather than through a documented open API.

Tables Accessed

  • MRP_FULL_PEGGING — The full pegging table mapping supply to demand across planning levels. The package reads pegging information to associate recommendations with the originating demand, which supports the computation of expected ship dates and forecast consumption.
  • MRP_RECOMMENDATIONS — The planning recommendations table holding suggested planned orders and reschedules. The package reads recommendation data to derive order-related date and quantity attributes used by the BIS views.

Both tables are accessed via APPS synonyms, which is standard for PL/SQL objects compiled in the APPS schema. The package's dependency listing also shows a reference to the SYS.STANDARD package, reflecting normal PL/SQL runtime usage. No insert, update, or delete activity is documented; the object behaves as a read-oriented calculation utility.

Usage Notes

MRP_GET_BIS_VALUES is not intended for direct invocation by end users or by customer-written concurrent programs. Its principal consumers are the MRP BIS views identified in the dependency metadata. When a planner queries forecast accuracy or late-order information through the planning workbench, Oracle invokes these views, which in turn call the package functions to supply the derived columns.

Three other packages are documented as referencing this object, indicating that at least some planning-side PL/SQL code also depends on its results. Because the package is classified as OTHER with no published API documentation, customizations should not call it directly; instead, custom reports should select from the supported MRP_BIS views, which encapsulate the dependency and shield customer code from changes across 12.1.1 and 12.2.2. Developers validating dependencies should note that the package sits beneath the views in the dependency chain, so recompilation or invalidation of MRP_GET_BIS_VALUES will invalidate all three dependent views and may affect other referencing packages.