Results for “demand_class_code”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OE_AK_DEMAND_CLASS_V is a lightweight, read-only database view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Order Management (ONT) product family and exists purely to expose the set of valid demand class codes defined in the application's lookup repository. The view carries a VALID status in the data dictionary and presents the demand class values in the same canonical form used by Oracle EBS list-of-values mechanisms.
Demand classes are a fundamental order management and planning concept. They allow organizations to categorize demand by source, business channel, or priority — for example distinguishing forecast demand from actual sales order demand, or separating internal, intercompany, and external consumption. Because demand class drives reservation, scheduling, and available-to-promise logic in Order Management and Oracle Advanced Supply Chain Planning, applications and integrations frequently need to enumerate the permitted demand class codes. OE_AK_DEMAND_CLASS_V provides exactly that enumeration, and it is often the object referenced by the Oracle Application Framework (OAF) "AK" style lookups used on order entry pages.
The view is a single-column projection. It applies no joins, no aggregation, and no filtering other than the lookup type predicate, which keeps it extremely cheap to query at runtime and safe to expose to integration layers.
Underlying Base Objects
Per the documented ETRM metadata for 12.2.2, OE_AK_DEMAND_CLASS_V is defined over a single referenced base object: the OE_LOOKUPS view. In Oracle EBS, OE_LOOKUPS is itself a view over the core lookup table FND_LOOKUP_VALUES (and, historically, its pre-11i antecedent). It presents lookup codes in the Order Management domain, filtered and formatted so that seeded lookup types are exposed with their enabled values.
The view definition is minimal and explicit:
- SELECT LOOKUP_CODE FROM OE_LOOKUPS WHERE LOOKUP_TYPE = 'DEMAND_CLASS_CODE'
- The result is a derived single column aliased DEMAND_CLASS_CODE.
Because OE_LOOKUPS resolves against the FND lookup infrastructure, the values returned reflect only lookups that are currently enabled in the application. Disabling or end-dating a lookup value in the Lookup Codes form (Application Developer responsibility) automatically removes it from this view, which means the view is inherently locale- and configuration-aware without any additional logic. Note that the view text does not filter on VIEW_APPLICATION_ID or territory, so any enabled value under the DEMAND_CLASS_CODE lookup type is returned regardless of the application that owns it.
Key Columns
The view exposes a single column:
- DEMAND_CLASS_CODE (VARCHAR2) — the enabled lookup code from the DEMAND_CLASS_CODE lookup type. This is the stored value that Order Management writes to demand-class columns elsewhere in the schema, such as OE_ORDER_LINES_ALL.DEMAND_CLASS_CODE and OE_ORDER_HEADERS_ALL.DEMAND_CLASS_CODE, and that planning and shipping logic interprets. Values are seeded by Oracle (for example, the standard set includes codes representing normal, expedited, and forecast-style demand) and may be extended by the implementing organization through the Lookups form.
No display name, description, or enabled-flag column is exposed. Consumers that need the translated meaning of a code must join back to the underlying lookup definition.
Common Use Cases and Queries
The most common use is populating a selection list or validation list in a custom form, OAF page, or integration mapping. The trivial enumeration query is:
SELECT demand_class_code FROM oe_ak_demand_class_v ORDER BY demand_class_code;- Validating an inbound value:
SELECT 1 FROM oe_ak_demand_class_v WHERE demand_class_code = :p_code;
When the business meaning is required alongside the code, the view is typically joined to FND_LOOKUP_VALUES:
SELECT d.demand_class_code, l.meaning, l.descriptionFROM oe_ak_demand_class_v d, fnd_lookup_values lWHERE l.lookup_type = 'DEMAND_CLASS_CODE' AND l.lookup_code = d.demand_class_code;
Reporting queries commonly use the view as a driver to reconcile order-line demand classes against the master list, ensuring no dormant or retired codes remain assigned to open lines. Integration developers also use it as a fast, dependency-free source of truth for the demand class dimension when staging data for a planning interface.
-
View: OE_AK_DEMAND_CLASS_V 12.2.2
-
View: OE_DEMAND_CLASSES_V 12.2.2
This is view is used for the Demand Class LOV in Sales Orders form.
APPS.OE_DEMAND_CLASSES_V·↳ FND_COMMON_LOOKUPS·↳ FND_GLOBAL·Explore ONT module →
-
View: OE_AK_DEMAND_CLASS_V 12.1.1
-
View: OE_DEMAND_CLASSES_V 12.1.1
This is view is used for the Demand Class LOV in Sales Orders form.
APPS.OE_DEMAND_CLASSES_V·↳ FND_COMMON_LOOKUPS·↳ FND_GLOBAL·Explore ONT module →
-
View: OE_WIP_OPEN_DEMANDS_V 12.2.2
APPS.OE_WIP_OPEN_DEMANDS_V·↳ FND_LANGUAGES·↳ FND_PROFILE·↳ MTL_SALES_ORDERS·Explore ONT module →
-
View: OE_AK_LINE_TYPES_V 12.1.1
APPS.OE_AK_LINE_TYPES_V·↳ OE_LINE_TYPES_V·Explore ONT module →
-
View: OE_AK_LINE_TYPES_V 12.2.2
APPS.OE_AK_LINE_TYPES_V·↳ OE_LINE_TYPES_V·Explore ONT module →
-
View: OE_WIP_OPEN_DEMANDS_V 12.1.1
APPS.OE_WIP_OPEN_DEMANDS_V·↳ FND_LANGUAGES·↳ FND_PROFILE·↳ MTL_SALES_ORDERS·Explore ONT module →
-
View: OE_AK_SHIP_TO_ORGS_V 12.1.1
APPS.OE_AK_SHIP_TO_ORGS_V·↳ HZ_CUST_SITE_USES·↳ HZ_CUST_SITE_USES_ALL·Explore ONT module →
-
View: OE_AK_ORDER_TYPES_V 12.2.2
APPS.OE_AK_ORDER_TYPES_V·↳ OE_ORDER_TYPES_V·Explore ONT module →
-
View: OE_AK_ORDER_TYPES_V 12.1.1
APPS.OE_AK_ORDER_TYPES_V·↳ OE_ORDER_TYPES_V·Explore ONT module →
-
View: OE_ORDER_TYPES_115 12.1.1
No longer used
APPS.OE_ORDER_TYPES_115·↳ OE_TRANSACTION_TYPES_VL·Explore ONT module →
-
View: OE_AK_SHIP_TO_ORGS_V 12.2.2
APPS.OE_AK_SHIP_TO_ORGS_V·↳ HZ_CUST_SITE_USES·↳ HZ_CUST_SITE_USES_ALL·Explore ONT module →
-
View: OE_ORDER_TYPES_115_ALL 12.2.2
No longer used
APPS.OE_ORDER_TYPES_115_ALL·↳ OE_TRANSACTION_TYPES_ALL·↳ OE_TRANSACTION_TYPES_TL·Explore ONT module →
-
View: OE_CRM_ORDER_HEADERS_V 12.2.2
Compatible view provoded for CRM usage only. The view is based on oe_order_headers_all table.
APPS.OE_CRM_ORDER_HEADERS_V·↳ OE_ORDER_HEADERS·Explore ONT module →
-
View: OE_CRM_ORDER_HEADERS_V 12.1.1
Compatible view provoded for CRM usage only. The view is based on oe_order_headers_all table.
APPS.OE_CRM_ORDER_HEADERS_V·↳ OE_ORDER_HEADERS·Explore ONT module →
-
View: OE_MRP_OPEN_DEMANDS_V 12.1.1
This vew is used by MRP for their Scheduler's Workbench.
APPS.OE_MRP_OPEN_DEMANDS_V·↳ OE_ORDER_HEADERS_ALL·↳ OE_ORDER_LINES_ALL·↳ OE_SETS·Explore ONT module →
-
View: OE_MRP_OPEN_DEMANDS_V 12.2.2
This vew is used by MRP for their Scheduler's Workbench.
APPS.OE_MRP_OPEN_DEMANDS_V·↳ OE_ORDER_HEADERS_ALL·↳ OE_ORDER_LINES_ALL·↳ OE_SETS·Explore ONT module →
-
View: OE_LINE_TYPES_V 12.1.1
This is a view to show line transaction types types for a specific organization and language.
APPS.OE_LINE_TYPES_V·↳ OE_TRANSACTION_TYPES_VL·Explore ONT module →
-
View: OE_ORDER_TYPES_115 12.2.2
No longer used
APPS.OE_ORDER_TYPES_115·↳ OE_TRANSACTION_TYPES_VL·Explore ONT module →
-
View: OE_TRANSACTION_TYPES_V 12.2.2
APPS.OE_TRANSACTION_TYPES_V·↳ HR_GENERAL·↳ HR_ORGANIZATION_UNITS·↳ HR_SECURITY·Explore ONT module →
-
View: OE_ORDER_TYPES_115_ALL 12.1.1
No longer used
APPS.OE_ORDER_TYPES_115_ALL·↳ OE_TRANSACTION_TYPES_ALL·↳ OE_TRANSACTION_TYPES_TL·Explore ONT module →
-
View: OE_CRM_ORDER_LINES_V 12.1.1
Compatible view provoded for CRM usage only. The view is based on oe_order_lines_all table.
APPS.OE_CRM_ORDER_LINES_V·↳ OE_ORDER_LINES·Explore ONT module →
-
View: OE_ORDER_TYPES_V 12.2.2
This is a view to show order transaction types for a specific organization and language.
APPS.OE_ORDER_TYPES_V·↳ OE_TRANSACTION_TYPES_VL·Explore ONT module →
-
View: OE_ORDER_TYPES_V 12.1.1
This is a view to show order transaction types for a specific organization and language.
APPS.OE_ORDER_TYPES_V·↳ OE_TRANSACTION_TYPES_VL·Explore ONT module →
-
View: OE_TRANSACTION_TYPES_V 12.1.1
APPS.OE_TRANSACTION_TYPES_V·↳ HR_GENERAL·↳ HR_ORGANIZATION_UNITS·↳ HR_SECURITY·Explore ONT module →
-
View: OE_LINE_TYPES_V 12.2.2
This is a view to show line transaction types types for a specific organization and language.
APPS.OE_LINE_TYPES_V·↳ OE_TRANSACTION_TYPES_VL·Explore ONT module →
-
Org independent VL view for Shipping integration team to get the Order Type name.
APPS.OE_TRXT_TYPES_NOORGS_VL·↳ OE_TRANSACTION_TYPES_ALL·↳ OE_TRANSACTION_TYPES_TL·Explore ONT module →
-
MLS transaction types view for an organization.
APPS.OE_TRANSACTION_TYPES_VL·↳ OE_TRANSACTION_TYPES_SYN·↳ OE_TRANSACTION_TYPES_TL·Explore ONT module →
-
Sales Order upgrade table - Shipping integration.
-
Sales Order upgrade table - Shipping integration.
-
View: OE_ORDER_LINES_AUDIT_V 12.1.1
APPS.OE_ORDER_LINES_AUDIT_V·↳ OE_ORDER_HEADERS_ALL·↳ OE_ORDER_LINES_HISTORY·↳ OE_REASONS·Explore ONT module →
-
View: OE_ORDER_LINES_AUDIT_V 12.2.2
APPS.OE_ORDER_LINES_AUDIT_V·↳ OE_ORDER_HEADERS_ALL·↳ OE_ORDER_LINES_HISTORY·↳ OE_REASONS·Explore ONT module →
-
Org independent VL view for Shipping integration team to get the Order Type name.
APPS.OE_TRXT_TYPES_NOORGS_VL·↳ OE_TRANSACTION_TYPES_ALL·↳ OE_TRANSACTION_TYPES_TL·Explore ONT module →
-
View: OE_SHIP_TO_ORGS_V 12.1.1
Ship To Organizations.
APPS.OE_SHIP_TO_ORGS_V·↳ HZ_CUST_ACCT_SITES·↳ HZ_CUST_SITE_USES_ALL·↳ HZ_LOCATIONS·Explore ONT module →
-
View: OE_SHIP_TO_ORGS_V 12.2.2
Ship To Organizations.
APPS.OE_SHIP_TO_ORGS_V·↳ HZ_CUST_ACCT_SITES·↳ HZ_CUST_SITE_USES_ALL·↳ HZ_LOCATIONS·Explore ONT module →
-
This table stores information about the order and line transaction types
-
View: OE_CRM_ORDER_LINES_V 12.2.2
Compatible view provoded for CRM usage only. The view is based on oe_order_lines_all table.
APPS.OE_CRM_ORDER_LINES_V·↳ OE_ORDER_LINES·Explore ONT module →
-
View: OE_LINE_ACKS_V 12.1.1
Information about the acknowledgements for Order Lines
-
View: OE_LINE_ACKS_V 12.2.2
Information about the acknowledgements for Order Lines
-
MLS transaction types view for an organization.
APPS.OE_TRANSACTION_TYPES_VL·↳ OE_TRANSACTION_TYPES_SYN·↳ OE_TRANSACTION_TYPES_TL·Explore ONT module →
-
View: OE_ORDER_LINES_RM_V 12.2.2
APPS.OE_ORDER_LINES_RM_V·↳ FND_LANGUAGES·↳ OE_ORDER_LINES_ALL·↳ OE_TRANSACTION_TYPES_ALL·Explore ONT module →
-
View: OEFV_ORDER_HEADERS 12.2.2
APPS.OEFV_ORDER_HEADERS·↳ AR_LOOKUPS·↳ FND_CURRENCIES·↳ FND_USER·Explore ONT module →
-
View: OE_BLANKET_HEADERS_V 12.1.1
APPS.OE_BLANKET_HEADERS_V·↳ AR_LOOKUPS·↳ FND_CURRENCIES·↳ HZ_CUST_ACCOUNTS·Explore ONT module →
-
This table stores information about the order and line transaction types
-
View: OEFV_ORDER_HEADERS 12.1.1
APPS.OEFV_ORDER_HEADERS·↳ AR_LOOKUPS·↳ FND_CURRENCIES·↳ FND_USER·Explore ONT module →
-
View: OE_AK_ORDER_HEADERS_V 12.1.1
APPS.OE_AK_ORDER_HEADERS_V·↳ HZ_CUST_ACCOUNTS·↳ HZ_PARTIES·↳ OE_ORDER_HEADERS_ALL·Explore ONT module →
-
View: OE_HEADER_ACKS_V 12.2.2
Information about the acknowledgements for Order Headers.
APPS.OE_HEADER_ACKS_V·↳ ECE_TP_DETAILS·↳ ECE_TP_HEADERS·↳ HZ_CUST_ACCOUNTS·Explore ONT module →
-
View: OE_SCH_ORDER_LINES_V 12.2.2
APPS.OE_SCH_ORDER_LINES_V·↳ AR_LOOKUPS·↳ FND_GLOBAL·↳ HZ_CUST_ACCOUNTS·Explore ONT module →
-
This view is used to retrieve the Order History. This is used by the history form.
APPS.OE_ORDER_HEADERS_HIST_V·↳ AR_LOOKUPS·↳ HZ_CUST_ACCOUNTS·↳ HZ_CUST_ACCOUNT_ROLES·Explore ONT module →