My Oracle Support Banner

OM - Schedule Orders Failed (Doc ID 2120417.1)

Last updated on JULY 29, 2019

Applies to:

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

Symptoms

After upgrade from 12.1.3 to 12.2.5 Schedule Orders program failed each time with ATP Processing Error.
Collect and Plan are now OK but orders can't be scheduled.
The error is also reproduced on Quick Sales Order form.

***** Begin Call_Schedule Procedure *****
Error in Call_ATP_No_Commit :-6502
Call_ATP_No_Commit: ORA-06502: PL/SQL: numeric or value error: character to number conversion error
Call_ATP_No_Commit: shipset count 1
Call_ATP_No_Commit: Exception x_return_status : E
Rows deleted from msc_regions_temp:2
Rows deleted from msc_atp_src_profile_temp:0
debug_wf: Debug WF started p_session_id 103488109
something wrong in Call_ATP_Commit : 100
Call_ATP_Commit: ORA-01403: no data found
ORA-06502: PL/SQL: numeric or value error: character to number conversion error


STEPS
--------
1. Order Management Responsibility
2. Sales Orders > Query Order in Entered status

Changes

upgrade from 12.1.3 to 12.2.5 

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.