My Oracle Support Banner

ATP Demand Saved In MSC_SALES_ORDERS Whereas OM Does Undo/Rollback Of Scheduling Action (Doc ID 2464426.1)

Last updated on AUGUST 12, 2021

Applies to:

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


Several years ago for 12.1.3, there were demand discrepancies for Check ATP items between the Order Management (OM) and Global Order Promising (GOP) tables for ATP based on collected data
(msc_sales_orders was showing demand for lines not scheduled in OM).
This was happening, for example, when a processing constraint was preventing OM from saving the sales order line after a schedule action.
Applied then 12.1.3 patches like:

Patch 18268780:R12.ONT.B OEXCSCHB.pls
Patch 17595785:R12.ON.T.B OEXUSCHB.pls 120.54.12010000.81 and other files

It seems there is a similar issue resurfacing in 12.2.6 while doing tests for an upgrade project.

Any time something prevents a Schedule action from being saved in OM (e.g. a processing constraint preventing update)
then the GOP/MSC demand data should be eliminated/deleted/rolled back as well.

1. Enter a sales order line for a Check ATP¨= Material item in an instance where we use ATP based on collected data.
2. Schedule a line where a processing constraint is set to prevent the save on the OM side.

you can see Demand for above line in View Collected Data (and msc_sales_orders)
for a line which is not Scheduled in OM as the schedule action was rolled back by processing constraint.


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

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