Search Results demand_class_fk




Overview
Explore in AI Chat

Overview

The EDW_DEMAND_CLASS_FKV view is a reporting and integration artifact within the Oracle EBS Master Scheduling/MRP (MRP) module. Its name encodes two conventions that are important for interpretation. The prefix EDW indicates that it belongs to the Enterprise Data Warehouse / business intelligence layer rather than the operational transaction schema, while the FKV suffix designates a "foreign key view" — an object whose purpose is to expose a user-readable description for a foreign key value. In this case the foreign key is the demand class reference used throughout demand, forecast, and planning data.

In the Oracle EBS 12.1.1 and 12.2.2 data model, many transactional tables store only a numeric or coded demand class identifier. Reports, extracts, and ETL mappings that surface demand class to end users must translate that identifier into a meaningful label. EDW_DEMAND_CLASS_FKV provides that translation: it returns the lookup code together with a composite display value that appends the instance code from EDW_LOCAL_INSTANCE. The view is therefore a convenience object that standardizes how the demand class dimension is presented across warehouse queries.

Underlying Base Objects

The view text is defined as a join between two objects:

Although the ETRM metadata records no additional referenced base objects for the 12.2.2 release, the view text itself makes the dependency on the lookup and instance tables explicit. The double underscore in the view name does not signify a database link; it is simply the EDW naming convention separating the subject area from the object type. The view is classified in the source notes as "Not implemented in this database," which in EBS documentation typically denotes that the object is a seeded or patch-delivered definition whose physical presence depends on whether the relevant EDW components were installed in the instance.

Key Columns

The view exposes a small, purpose-built column set:

  • DEMAND_CLASS_FK — the foreign key value; this is the LOOKUP_CODE from FND_LOOKUP_VALUES, effectively the demand class identifier carried by transactional and planning records.
  • DEMAND_CLASS_ID — the demand class identifier column expected by consuming queries and mappings. In the supplied definition the descriptive column is the concatenation LOOKUP_CODE || '-' || INSTANCE_CODE, which yields a display value combining the demand class code and the local instance code.

Because only the lookup code, the concatenated description, and the demand class identifier are projected, the view is narrow by design. Its value lies in the canonical, instance-aware representation of the demand class rather than in exposing additional lookup attributes such as descriptions or enabled flags.

Common Use Cases and Queries

Typical use cases include join-back lookups in BI reports, ETL dimension resolution (mapping a stored demand class code to its label), and validation extracts confirming which demand class codes are active for a given language.

  • Resolving demand class descriptions for forecast and demand reporting:
SELECT DEMAND_CLASS_FK, DEMAND_CLASS_ID
FROM   EDW_DEMAND_CLASS_FKV
ORDER  BY DEMAND_CLASS_FK;
  • Joining the view to a planning or demand fact table on the demand class foreign key to produce user-facing output:
SELECT F.ORGANIZATION_ID,
       F.DEMAND_CLASS,
       D.DEMAND_CLASS_ID
FROM   MY_DEMAND_FACT F,
       EDW_DEMAND_CLASS_FKV D
WHERE  F.DEMAND_CLASS = D.DEMAND_CLASS_FK;

Because the view filters by USERENV('LANG') and SECURITY_GROUP_ID = 0, results are language- and security-group dependent; queries should be executed in the intended session context to obtain correct labels.