My Oracle Support Banner

Poor Performance of ATP while scheduling orders (Doc ID 2753806.1)

Last updated on MARCH 02, 2021

Applies to:

Oracle Global Order Promising - Version 12.2.9 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.9 version, ATP based on planning data

ACTUAL BEHAVIOR
---------------
Poor performance of ATP during order booking.

The following SQL is taking 3.3 seconds. The performance could further be improved:

UPDATE MSC_ATP_PEGGING MAP1 SET OFFSET_SUPPLY_ID = :B1
WHERE
 MAP1.PLAN_ID = :B8 AND DECODE(MAP1.DEMAND_SOURCE_TYPE,100,
  MAP1.DEMAND_SOURCE_TYPE,-1) =DECODE(:B7 , 100, :B7 , -1) AND
  MAP1.SALES_ORDER_LINE_ID IN (:B6 , :B5 ) AND MAP1.RELIEF_TYPE =
  DECODE(MAP1.OFFSET_TYPE, 1, 6, 2) AND MAP1.INVENTORY_ITEM_ID = :B4 AND
  MAP1.PEGGING_ID = :B3 AND MAP1.SUPPLY_ID = :B2


EXPECTED BEHAVIOR
-----------------------
Expect that the orders to be scheduled in fair amount of time.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Enter the application.
2. Attempt to book sales orders.
3. See the above issue.


Changes

 

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
Changes
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.