Search Results rlm_demand_exceptions

Overview

RLM_DEMAND_EXCEPTIONS is a table in the RLM (Release Management) product schema of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It stores Release Management Exception records — that is, rows describing scheduling, demand, or interface conditions that Release Management has flagged as exceptions during processing. The table is populated by the Release Management scheduling and demand-processing programs and is used primarily for diagnostics, remediation, and downstream reporting of demand and scheduling anomalies before or after they are pushed to order and charge-schedule structures.

From a dimensional modeling perspective, the mined FK structure classifies this object heuristically as a standalone table. It carries no parent hub or link dependency other than an outbound reference to AR_CHARGE_SCHEDULE_HDRS, so it is best treated as an independent exception/fact-style table rather than a conformed dimension. Modeling it as a satellite or standalone exception fact keyed on EXCEPTION_ID is the practical suggestion.

Key Information Stored

EXCEPTION_ID — the surrogate primary key, enforced by EXCEPTION_ID_PK and also present in the unique index RLM_DEMAND_EXCEPTIONS_U1. This is the business-key candidate documented for the table.
MESSAGE_NAME, MESSAGE_TEXT — the exception identifier and its human-readable diagnostic text, the primary content consumed by users.
EXCEPTION_LEVEL — the severity or scope classification of the exception record.
SCHEDULE_HEADER_ID, SCHEDULE_LINE_ID — pointers to the release schedule (and line) that raised the exception. SCHEDULE_HEADER_ID carries the documented foreign key to AR_CHARGE_SCHEDULE_HDRS.
INTERFACE_HEADER_ID, INTERFACE_LINE_ID — the interface batch and line that carried the demand into Release Management.
ORDER_HEADER_ID, ORDER_LINE_ID — the sales order header and line affected, where known.
SCHEDULE_TYPE, SCHEDULE_PURPOSE, SCHEDULE_SOURCE, SCHEDULE_REFERENCE_NUM, SCHEDULE_ITEM_NUM, SCHEDULE_LINE_NUMBER, SCHED_GENERATION_DATE — schedule-context attributes that identify which scheduling run produced the exception.
INVENTORY_ITEM and the CUST_* columns (CUST_NAME_EXT, CUST_BILL_TO_EXT, CUST_SHIP_TO_EXT, CUST_ITEM_DESCRIPTION, CUST_PO_NUMBER and related fields) — external identifiers captured from the EDI or customer source.
DATE_TYPE_CODE, QTY_TYPE_CODE, ITEM_DETAIL_TYPE, ITEM_DETAIL_SUBTYPE, ITEM_DETAIL_QUANTITY — the demand measures and their classification underpinning the exception.
HORIZON_START_DATE, HORIZON_END_DATE, SCHEDULE_DATE, START_DATE_TIME, REQUEST_DATE — the time bounds and planning horizon in which the exception occurred.
ORIGIN_TABLE, PURGE_STATUS, REPORT_SUMMARY — provenance, purge lifecycle control, and report aggregation flags.
Standard WHO/audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

The most frequent use is exception review after a Release Management scheduling run. A typical query groups exceptions by message to find the dominant failure mode:

SELECT message_name, COUNT(*) FROM rlm.rlm_demand_exceptions WHERE creation_date >= :run_date GROUP BY message_name ORDER BY 2 DESC;
Trace an exception back to its charge schedule: SELECT e.exception_id, e.message_text, s.* FROM rlm.rlm_demand_exceptions e, ar.ar_charge_schedule_hdrs s WHERE e.schedule_header_id = s.schedule_header_id;
Correlate exceptions with order and interface context using ORDER_HEADER_ID, ORDER_LINE_ID, INTERFACE_HEADER_ID and INTERFACE_LINE_ID.
Purge maintenance reporting on PURGE_STATUS to age out resolved exceptions.

Reporting use cases include exception dashboards, aging analyses over HORIZON_START_DATE and HORIZON_END_DATE, and audit extracts feeding data warehouse staging for order-to-release cycle metrics.

Related Objects

AR_CHARGE_SCHEDULE_HDRS — referenced through RLM_DEMAND_EXCEPTIONS.SCHEDULE_HEADER_ID; the parent charge schedule for the exception.
RLM_DEMAND_EXCEPTIONS_U1 — the unique index on EXCEPTION_ID supporting the primary key lookup.
Release Management scheduling and interface programs — the concurrent programs that populate this table, identified via REQUEST_ID, PROGRAM_ID and PROGRAM_APPLICATION_ID.
Order Management order entities (order header and line tables) — joined through ORDER_HEADER_ID and ORDER_LINE_ID.
Interface tables referenced by INTERFACE_HEADER_ID and INTERFACE_LINE_ID, which carry demand into Release Management.
Inventory item master — joined through INVENTORY_ITEM for item-level exception reporting.

Table: RLM_DEMAND_EXCEPTIONS 12.2.2
owner:RLM, object_type:TABLE, fnd_design_data:RLM.RLM_DEMAND_EXCEPTIONS, object_name:RLM_DEMAND_EXCEPTIONS, status:VALID, product: RLM - Release Management , description: This table contains Release Management Exception records , implementation_dba_data: RLM.RLM_DEMAND_EXCEPTIONS ,
Table: RLM_DEMAND_EXCEPTIONS 12.1.1
owner:RLM, object_type:TABLE, fnd_design_data:RLM.RLM_DEMAND_EXCEPTIONS, object_name:RLM_DEMAND_EXCEPTIONS, status:VALID, product: RLM - Release Management , description: This table contains Release Management Exception records , implementation_dba_data: RLM.RLM_DEMAND_EXCEPTIONS ,
APPS.RLM_RLMDPPSR_XMLP_PKG SQL Statements 12.2.2
APPS.RLM_RLMDPPSR_XMLP_PKG SQL Statements 12.1.1
SYNONYM: APPS.RLM_DEMAND_EXCEPTIONS 12.1.1
owner:APPS, object_type:SYNONYM, object_name:RLM_DEMAND_EXCEPTIONS, status:VALID,
SYNONYM: APPS.RLM_DEMAND_EXCEPTIONS 12.2.2
owner:APPS, object_type:SYNONYM, object_name:RLM_DEMAND_EXCEPTIONS, status:VALID,
12.2.2 DBA Data 12.2.2
VIEW: RLM.RLM_DEMAND_EXCEPTIONS# 12.2.2
owner:RLM, object_type:VIEW, object_name:RLM_DEMAND_EXCEPTIONS#, status:VALID,
12.1.1 FND Design Data 12.1.1
12.2.2 DBA Data 12.2.2
12.2.2 FND Design Data 12.2.2
12.1.1 DBA Data 12.1.1
12.2.2 DBA Data 12.2.2
12.2.2 DBA Data 12.2.2
PACKAGE BODY: APPS.RLM_RLMDPPSR_XMLP_PKG 12.1.1
12.1.1 DBA Data 12.1.1
12.2.2 DBA Data 12.2.2
PACKAGE BODY: APPS.RLM_RLMDPPSR_XMLP_PKG 12.2.2
PACKAGE BODY: APPS.RLM_RLMDPPSR_XMLP_PKG 12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:RLM_RLMDPPSR_XMLP_PKG, status:VALID,
12.1.1 DBA Data 12.1.1
VIEW: RLM.RLM_DEMAND_EXCEPTIONS# 12.2.2
PACKAGE BODY: APPS.RLM_PS_SV 12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:RLM_PS_SV, status:VALID,
PACKAGE BODY: APPS.RLM_RLMDPPSR_XMLP_PKG 12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:RLM_RLMDPPSR_XMLP_PKG, status:VALID,
PACKAGE BODY: APPS.RLM_PS_SV 12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:RLM_PS_SV, status:VALID,
PACKAGE BODY: APPS.RLM_MESSAGE_SV 12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:RLM_MESSAGE_SV, status:VALID,
PACKAGE BODY: APPS.RLM_MESSAGE_SV 12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:RLM_MESSAGE_SV, status:VALID,
PACKAGE BODY: APPS.RLM_DP_SV 12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:RLM_DP_SV, status:VALID,
PACKAGE BODY: APPS.RLM_DP_SV 12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:RLM_DP_SV, status:VALID,
APPS.RLM_DP_SV SQL Statements 12.2.2
APPS.RLM_DP_SV SQL Statements 12.1.1
APPS.RLM_PS_SV SQL Statements 12.2.2
APPS.RLM_PS_SV SQL Statements 12.1.1
APPS.RLM_MESSAGE_SV SQL Statements 12.1.1
APPS.RLM_MESSAGE_SV SQL Statements 12.2.2
TABLE: RLM.RLM_DEMAND_EXCEPTIONS 12.2.2
owner:RLM, object_type:TABLE, fnd_design_data:RLM.RLM_DEMAND_EXCEPTIONS, object_name:RLM_DEMAND_EXCEPTIONS, status:VALID,
TABLE: RLM.RLM_DEMAND_EXCEPTIONS 12.1.1
owner:RLM, object_type:TABLE, fnd_design_data:RLM.RLM_DEMAND_EXCEPTIONS, object_name:RLM_DEMAND_EXCEPTIONS, status:VALID,
eTRM - RLM Tables and Views 12.2.2
description: This table stores the details of Query Criteria for each of the Query in RLM_UI_QUERIES ,
PACKAGE: APPS.RLM_MESSAGE_SV 12.2.2
PACKAGE: APPS.RLM_MESSAGE_SV 12.1.1
eTRM - RLM Tables and Views 12.1.1
description: This table stores the details of Query Criteria for each of the Query in RLM_UI_QUERIES ,
APPS.RLM_PS_SV dependencies on RLM_DEMAND_EXCEPTIONS 12.1.1
APPS.RLM_RLMDPPSR_XMLP_PKG dependencies on RLM_DEMAND_EXCEPTIONS 12.1.1
APPS.RLM_DP_SV dependencies on RLM_DEMAND_EXCEPTIONS 12.2.2
APPS.RLM_MESSAGE_SV dependencies on RLM_DEMAND_EXCEPTIONS 12.1.1
APPS.RLM_MESSAGE_SV dependencies on RLM_DEMAND_EXCEPTIONS 12.2.2
APPS.RLM_PS_SV dependencies on RLM_DEMAND_EXCEPTIONS 12.2.2
APPS.RLM_DP_SV dependencies on RLM_DEMAND_EXCEPTIONS 12.1.1
APPS.RLM_RLMDPPSR_XMLP_PKG dependencies on RLM_DEMAND_EXCEPTIONS 12.2.2
PACKAGE BODY: APPS.RLM_DP_SV 12.1.1
PACKAGE BODY: APPS.RLM_DP_SV 12.2.2