Copyright (c) 2025, Oracle. All rights reserved. Oracle Confidential.
Selecting the Availability Button on Sales Order Form Shows Error APP-ONT-251229 There Are
No Scheduling Results to Display (Doc ID 3027263.1)
In this Document
Symptoms
Changes
Cause
Solution
References
APPLIES TO:
Oracle Order Management - Version 12.2.13 and later
Oracle Global Order Promising - Version 12.2.13 to 12.2.13 [Release 12.2]
Information in this document applies to any platform.
SYMPTOMS
When attempting to selecting the availability button on Sales Order form, the following error is shown.
APP-ONT-251229 There are no scheduling results to display.
The issue can be reproduced at will with the following steps:
1. Responsibility: Order Management Super User (or equivalent)
2. Navigate to: Orders, Returns > Sales Orders
3. Query the order
4. Click on the line and open Availability form and above error message is shown.
CHANGES
Recently upgraded to Oracle Applications version 12.2.13
CAUSE
This issue will occur if Scheduling Level, under the shipping tab, at both Header and Line
transaction type is blank and availability button is clicked to check availability details.
The error is coming from procedure OE_GROUP_SCH_UTIL.Validate_Group.
This procedure calls the procedure OE_SCHEDULE_UTIL.Validate_Line to get scheduling level code for that line.
Procedure OE_SCHEDULE_UTIL.Validate_Line is returning Scheduling level code as NULL. Due to null value the next set of
executions is not happening.
This is explained in the following unpublished bug:
Bug 36650040 - AVAILABILITY FUNCTION ON SALES ORDER FORM IS GIVING ERROR APP-ONT-251229
SOLUTION
To implement the permanent solution, please execute the following steps:
1. Download and review the readme and pre-requisites for Patch 36650040:[Link].C
2. Ensure that you have taken a backup of your system before applying the recommended patch.
3. Apply the patch in a test environment.
4. Confirm the following file versions:
$ONT_TOP/patch/115/sql/[Link] version 120.117.12020000.148
$ONT_TOP/patch/115/sql/[Link] version 120.21.12020000.17
You can use the commands like the following:
strings -a / | grep $Header
5. Retest the issue.
6. Migrate the solution as appropriate to other environments.
REFERENCES
Didn't find what you are looking for?