My Oracle Support Banner

RLM Orphans Entries On Mtl_Sales_Orders Table When No OE_ORDER_HEADER Row Created (Doc ID 3005928.1)

Last updated on FEBRUARY 21, 2024

Applies to:

Oracle Release Management - Version 12.2.9 and later
Oracle Order Management - Version 12.2.9 and later
Oracle Inventory Management - Version 12.2.9 and later
Information in this document applies to any platform.

Symptoms


RLM orphans entries on mtl_sales_orders table when no OE_ORDER_HEADER row created.
When attempting to Process RLM Schedule to created Sales Orders it will use sales order
numbers based on our settings in our processing rules to generate one Order Number per
week for a customer for the window of time within the input schedule. When a gapless
sequence of sales order numbers is used, RLM will generate and book sales orders for
any orders needed an on the OE_ORDER_HEADERS_ALL table and will remove those
"temporary" order numbers that it used, however at the same time it is writing these sales
order values to the mtl_sales_orders table to sync with the inventory module, but then
does NOT go back and remove the unused sales order numbers, leaving these records
"orphaned".

Warning :: Calculate Schedule Ship date API returned the
following warning:
The Use EDI SDP code flag for Ship From Org C01, Customer
XXX Samples and address NNNNNN1 is set to Yes. Please
ensure that a valid Ship Delivery pattern code is passed
in the schedule. Using Default Ship Delivery Pattern Code Y.

Warning :: Past Due Demand detected - schedule indicates
demand 0 received for ship from-ship to-customer item
on request date 19-NOV-22
(Original Customer Request Date 19_NOV-22) prior to
schedule processing date 05-MAY-23 (Schedule Line 1).
Additional matching attribute(s) Customer Production
Line= , Customer Dock Code= , Customer Dock Code= ,
Purchase Order Number= nnnnnn88, Customer Item Revision=,
Job Number=, Model Serial Number=


1. Release Management Super User
2. Run > DSP side 830 Inbound Planning Schedule
3. Warning :: Calculate Schedule Ship date API returned
4. Warning :: Warning :: Past Due Demand detected - schedule indicates
                      demand 0 received for ship from-ship to-customer item
                      nnnnnn0  on request date 19-NOV-22

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.