Search Results demand_class




Overview
Explore in AI Chat

Overview

MRPBV_DEMAND_CLASSES is a read-only view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the MRP (Master Scheduling/MRP) product family. ETRM metadata classifies the object as a VIEW with a status of VALID and describes it as a retrofitted component, indicating it was introduced or harmonized to preserve backward compatibility with earlier Oracle Applications releases. The view exposes the set of valid demand class codes used by Oracle Master Scheduling/MRP and Advanced Supply Chain Planning to categorize independent and dependent demand.

Demand classes allow planners to segment demand by source, business channel, customer group, or priority so that supply can be allocated, netted, and reported distinctly. MRPBV_DEMAND_CLASSES presents this reference data in a report-friendly form, joining the demand class lookup values to their enabled/disabled status expressed as a YES/NO meaning. Because it is defined with a WITH READ ONLY clause, it is intended purely for query, reporting, integration, and lookup purposes rather than for direct DML.

Underlying Base Objects

The view is defined over the FND_COMMON_LOOKUPS view, which it references twice through a self-join, and it also relies on the FND_GLOBAL package within the EBS technology stack. One instance of FND_COMMON_LOOKUPS, aliased DEMAND_CLASS, is filtered to rows where LOOKUP_TYPE equals 'DEMAND_CLASS'. The second instance, aliased LKUP, is filtered to rows where LOOKUP_TYPE equals 'YES_NO'. The join condition equates LKUP.LOOKUP_CODE with DEMAND_CLASS.ENABLED_FLAG, so the enabled flag stored on the demand class lookup record is translated into the human-readable YES/NO meaning from the common lookup set. FND_COMMON_LOOKUPS is itself a view maintained by Oracle Application Object Library, and MRPBV_DEMAND_CLASSES therefore inherits standard EBS lookup security and multi-org behavior through that layer. The FND_GLOBAL dependency supplies session context such as user and responsibility information used by the underlying lookup view.

Key Columns

  • DEMAND_CLASS — The lookup code that uniquely identifies the demand class.
  • MEANING — The descriptive, user-facing name of the demand class.
  • DESCRIPTION — Optional free-text detail about the demand class.
  • START_EFFECTIVE_DATE — The date from which the demand class becomes active.
  • END_EFFECTIVE_DATE — The date on which the demand class ceases to be active.
  • ENABLED_FLAG — The enabled/disabled indicator, exposed here as the YES/NO meaning resolved via the FND_COMMON_LOOKUPS join.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — Standard EBS audit columns recording who created and last modified the lookup row and when.

Note that the documented column listing includes MEANING as the enabled-flag meaning; the underlying query also selects the DEMAND_CLASS.MEANING as the first meaning column, which is the demand class description presented to users.

Common Use Cases and Queries

MRPBV_DEMAND_CLASSES is most often queried to populate list of values, reporting lookups, and integration extracts that must present only enabled demand classes. A typical query retrieves the active demand class set:

  • Validate a demand class code entered in a planning interface before loading demand or supply records.
  • Join to planning demand tables to describe demand class codes in reports.
  • Filter to enabled classes using the YES/NO meaning, for example: SELECT demand_class, meaning FROM mrp_demand_classes_view WHERE enabled_flag = 'Y';
  • Retrieve effective-dated classes using START_EFFECTIVE_DATE and END_EFFECTIVE_DATE.

Because the object is read-only, it should be used strictly for retrieval. Changes to demand class definitions must be made through the standard lookup maintenance UI in Application Developer responsibility, which updates FND_COMMON_LOOKUPS and is immediately reflected in this view.