ATP API- Returns Inconsistent Result In MRP_ATP_DETAILS_TEMP Using ATP API Compared To ATP Inquiry (Doc ID 2092646.1)

Last updated on MARCH 08, 2017

Applies to:

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

Goal

The customization/Custom code starts only after the data is populated in MRP_ATP_DETAILS_TEMP table.
We are trying to populate the MRP_ATP_DETAILS_TEMP table using the standard ATP API.

The issue I'm trying to address here is and I need Your help on is ,

The mismatch in data in the MRP_ATP_DETAILS_TEMP table between the following 2 options.

Option 1 :
Responsibility : Order Management Super User
Navigation : Scheduling > ATP Inquiry

Demand Class - A
Org - US2
Item - BB
Qty - 999999
Request Date - 24-JUN-2016

Hit 'ATP Details' button.
Once You are in the ATP Details window,
Help > Diagnostics > Examine and pick the SESSION_ID

Now try to query the MRP_ATP_DETAILS_TEMP table with the SESSION_ID.
It will return few rows. Check the CUMULATIVE_QUANTITY for each PERIOD_START_DATE.

Option 2 :
Run a Program calling the ATP API and pass the same set of parameters,
Demand Class - A
Org - US2
Item - BB
Qty - 999999
Request Date - 24-JUN-2016

Now pick the SESSION_ID from the log file of the program and query the MRP_ATP_DETAILS_TEMP table.
The CUMULATIVE_QUANTITY for PERIOD_START_DATE is different in this case.

The only difference is , We are passing 1000 Items into the API to get the output.This is done to handle the performance.

We are using details from the MRP_ATP_DETAILS_TEMP to build custom report on large numbers of items and need the correct information as seen when using the ATP Inquiry form.
 

Solution

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