Search Results rlm_schedule_purpose

Overview

RLM.RLM_DEMAND_EXCEPTIONS is a transactional table in the Oracle E-Business Suite Release 12.1.1 and 12.2.2 schemas that captures the exception messages produced when the Demand Processor is executed. Each row represents a discrete error, warning, or informational condition raised against an inbound demand or scheduling record processed by Oracle's Demand Planning and order scheduling flows. The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and is owned by the RLM schema. It functions as the diagnostic and audit trail for the demand scheduling engine, allowing planners and support personnel to trace why a specific demand line, schedule, or interface record failed validation or triggered a warning.

From a Data Vault modeling perspective, the heuristic classification determined from the foreign key structure is standalone. The table has no upstream hubs or links feeding it through enforced referential constraints beyond the documented FK to AR_CHARGE_SCHEDULE_HDRS; it behaves as a self-contained record of exception events rather than a classical hub, link, or satellite. Modelers should treat it as an event/log-style table keyed by a surrogate identifier.

Key Information Stored

The table contains 79 documented columns. The most significant are:

• EXCEPTION_ID — Surrogate primary key (EXCEPTION_ID_PK) and the column underlying the unique index RLM_DEMAND_EXCEPTIONS_U1; the sole documented business-key candidate.
• MESSAGE_NAME — Exception code, foreign key to FND_NEW_MESSAGES, with its own nonunique index RLM_DEMAND_EXCEPTIONS_N4.
• EXCEPTION_LEVEL — Classifies the row as warning ('W'), error ('E'), or information ('I').
• MESSAGE_TEXT — The rendered exception text presented to the user.
• SCHEDULE_HEADER_ID and SCHEDULE_LINE_ID — Link the exception to the demand schedule header and line (indexed via RLM_DEMAND_EXCEPTIONS_N2).
• INTERFACE_HEADER_ID and INTERFACE_LINE_ID — Identify the inbound interface record that caused the exception (indexed via RLM_DEMAND_EXCEPTIONS_N3).
• REQUEST_ID — The concurrent request that generated the exception (indexed via RLM_DEMAND_EXCEPTIONS_N1), enabling traceability to the Demand Processor run.
• SCHEDULE_PURPOSE, SCHEDULE_TYPE, and SCHEDULE_SOURCE — Describe the intent, classification, and origin of the schedule.
• SCHEDULE_ITEM_NUM and INVENTORY_ITEM — The item against which the exception was raised.
• CUSTOMER_ITEM_EXT, CUST_NAME_EXT, CUST_BILL_TO_EXT, CUST_SHIP_TO_EXT — External customer and location identifiers from the EDI segments.
• SCHED_GENERATION_DATE, START_DATE_TIME, HORIZON_START_DATE, HORIZON_END_DATE — Scheduling and horizon dates relevant to the exception.
• PURGE_STATUS and ORIGIN_TABLE — Support archival and provenance tracking.
• EXCEPTION_ATTRIBUTE1 through EXCEPTION_ATTRIBUTE20 — A flexible descriptive attribute set for extensibility.

Common Use Cases and Queries

Typical scenarios include error triage after a Demand Processor concurrent program run, reconciliation of EDI 830/862 inbound schedules, and vendor or customer scorecard reporting on exception frequency.

• Identify all errors from a specific run:
  SELECT EXCEPTION_ID, MESSAGE_NAME, MESSAGE_TEXT FROM RLM.RLM_DEMAND_EXCEPTIONS WHERE REQUEST_ID = :req AND EXCEPTION_LEVEL = 'E';
• Filter exceptions specific to the "rlm_schedule_purpose" attribute, which identifies the purpose of the schedule that triggered the exception:
  SELECT SCHEDULE_HEADER_ID, SCHEDULE_PURPOSE, EXCEPTION_LEVEL FROM RLM.RLM_DEMAND_EXCEPTIONS WHERE SCHEDULE_PURPOSE = :purpose;
• Trace exceptions back to the originating schedule header and line: join on SCHEDULE_HEADER_ID to RLM_DEMAND_SCHEDULE_HDRS.
• Trend warning volume by customer or item using CUST_NAME_EXT and SCHEDULE_ITEM_NUM for reporting.

Related Objects

• FND_NEW_MESSAGES — Joined via MESSAGE_NAME for the full exception message definition.
• AR_CHARGE_SCHEDULE_HDRS — Referenced by the documented FK on SCHEDULE_HEADER_ID.
• RLM_DEMAND_SCHEDULE_HEADERS / LINES — The schedule constructs to which exceptions attach.
• RLM_DEMAND_INTERFACE_HEADERS / LINES — The inbound interface records validated by the Demand Processor.
• FND_CONCURRENT_REQUESTS — Joined via REQUEST_ID to link exceptions to the concurrent program run.
• Demand Processor concurrent program — The program whose execution produces these exception rows.