Search Results demand_code

Overview

The view RHX_DP_L_DMDCLASS_V is a reporting and integration object delivered within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments under the MRP – Master Scheduling/MRP product family. It exposes the set of values defined for the DEMAND_CLASS lookup type as maintained in the Oracle Application Object Library (FND) common lookups repository. The object is documented as "Retrofitted," indicating that it was introduced or reconstructed to conform to the RHX naming convention used by the Demand Planning / Demand Planning (DP) extension layer rather than being a native, first-generation Oracle EBS view.

Functionally, the view provides a normalized, presentation-ready projection of the demand classification codes used throughout demand planning, forecasting, and master scheduling processes. Rather than querying FND_COMMON_LOOKUPS directly, callers reference this view to obtain a stable column interface and to decouple application logic from the underlying lookup table schema. This pattern is common in EBS reporting and integration scenarios where lookup values must be surfaced consistently to concurrent programs, OBIEE extracts, or third-party planning tools.

Underlying Base Objects

The view is defined over a single documented base object: FND_COMMON_LOOKUPS (aliased as FCL in the view text). The defining SQL is:

• SELECT FCL.LOOKUP_CODE, FCL.MEANING, FCL.DESCRIPTION FROM FND_COMMON_LOOKUPS FCL WHERE FCL.LOOKUP_TYPE = 'DEMAND_CLASS'

Consequently, the view is essentially a filtered, column-renamed extract restricted to rows where LOOKUP_TYPE = 'DEMAND_CLASS'. Because FND_COMMON_LOOKUPS is a global, non-org-specific table, the view carries no inventory organization, operating unit, or ledger context; it returns the complete, enabled and disabled set of demand class lookup values registered in the application. The ETRM metadata notes the view is "Not implemented in this database," meaning it exists in the object definitions but may not be deployed in every instance, particularly where the Demand Planning retrofit has not been applied. No other base objects are documented, and no joins, unions, or subqueries are present in the view text.

Key Columns

The view exposes three columns, each derived directly from the base lookup table:

• DEMAND_CODE — Mapped from FCL.LOOKUP_CODE. This is the short, stored code identifying the demand class (for example, a value such as FORECAST or BOOKED). It is the column most commonly referenced by demand planning logic and is the target of the user's "demand_code" search term.
• DEMAND_CLASS — Mapped from FCL.MEANING. This is the descriptive, user-facing label associated with the demand code, suitable for display in reports and LOVs.
• DESCRIPTION — Mapped from FCL.DESCRIPTION. Provides the extended textual definition of the demand class, useful for documentation and validation reporting. Note that this column is commonly null for lookup rows that have no supplementary description.

Common Use Cases and Queries

The view is typically used to populate selection lists, drive demand classification logic, and validate inbound interface data. A representative query returning the demand class reference set is:

• SELECT DEMAND_CODE, DEMAND_CLASS, DESCRIPTION FROM RHX_DP_L_DMDCLASS_V ORDER BY DEMAND_CODE;

To resolve a specific code for a planning program parameter:

• SELECT DEMAND_CLASS FROM RHX_DP_L_DMDCLASS_V WHERE DEMAND_CODE = :p_demand_code;

For reporting demand class distribution across forecast or booking extracts, the view is joined to demand planning fact tables or interface staging tables on DEMAND_CODE. Because the object is a simple lookup projection, it is inexpensive to query and can be safely embedded in concurrent program LOV definitions, BI Publisher data templates, and integration extracts without performance concern.