Schedule Orders Program Creates Wrong Demand In Msc_sales_orders Table If SO Lines Fail In Error (Doc ID 1638134.1)

Last updated on MARCH 25, 2014

Applies to:

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


On : 12.1.3 version, Scheduling and Sourcing

Demand is saved in msc_sales_orders table while SO line is not scheduled when a user attempts to schedule a sales order with a line referring to an item which is not orderable anymore.
Any subsequent ATP inquiry or scheduling will be inconsistent for this item after this and add more ATP demand.

You used a processing constraints to prevent ordering of the item. When Schedule Orders Concurrent program processes this SO line, it rejects the scheduling with a dedicated Process message and schedule ship date / schedule arrival date remain empty. But the demand is still viewable in MSC_SALES_ORDERS table.

Previously Bug 17595785 was logged for the same kind of issue but when scheduling SO lines directly from OM screens. <Patch 17595785> was provided that resolved the issue scheduling is launched from SO line / tools / Scheduling / Schedule. Need the same fix for Schedule Orders concurrent program.

Item would not have any demand in ATP

The issue can be reproduced at will with the following steps:
1. Run Schedule Orders concurrent program to schedule non scheduled SO lines
2. The scheduling is rejected due to processing constraint however demand is saved in msc_sales_orders table.


Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms