OEXOEORD - Order not Eligible for Booking Workflow Error ORA-20001 (Doc ID 268714.1)

Last updated on SEPTEMBER 02, 2016

Applies to:

Oracle Order Management - Version 11.5.8 to 12.2 [Release 11.5.8 to 12.2]
Information in this document applies to any platform.
Checked for relevance on 07-Jul-2010
***Checked for relevance on15-APR-2015***
This document is intended to help users successfully setup organizations for the purpose of Intercompany Invoicing through the Oracle Inventory Application.



Symptoms

Please understand that different customer scenarios may cause this error message.  Below you will find samples of 12 scenarios that include the basic description of the issue, symptoms experienced and potential fix.  Please choose the scenario that best matches your issue.

1) Receive workflow error when booking sales order:
Error is: Order is not Eligible for Booking. Check workflow status for this order.
Checking the workflow status, the workflow exception error is:
ORA-20001:
OE_Order_WF.Book_Order(OEOH,29058, 110960, RUN)
Wf_Engine_Util.Function_Call(OE_BOOK_WF.BOOK_ORDER, OEOH, 29058,110960.RUN)

Or

2) Receive workflow error when booking sales order:
Error is: Order Not Eligible to be Booked, please review the Workflow.
Checking the workflow status, the workflow gives the error ORA-20001 without any error message.
OMSE11i.sql output shows following (as an example):
WORKFLOW ORDER LEVEL ERRORS
Book - Order, Manual Book Exception Error
SYSADMIN SYSADMIN -20001
ORA-20001:
OE_Order_WF.Book_Order (OEOH, 394710, 62943, RUN)
Wf_Engine_Util.Function_Call (OE_BOOK_WF.BOOK_ORDER, OEOH, 394710, 62943, RUN)

Or

3) Sales order errored with ORA-20001 when booking the order.
Workflow exception error at header level when booking a Sales Order.
Activity: Book
Result: Exception
Error Name: -20001
Error Message: ORA-20001:
Error Stack: OE_Order_WF.Book_Order(OEOH, 1024, 144461, RUN)
Wf_Engine_Util.Function_Call(OE_BOOK_WF.BOOK_ORDER, OEOH, 1024, 144461, RUN)

Or

4) OM Order Information.txt
OMSE11i.sql output for order shows:
Order Header and lines are entered
Order Header:
Order type = Order Cash
Activity
BOOK_ORDER
Result
#EXCEPTION
Status
Error
-----
Error Name :-20001
Error Message: ORA-20001:
Error Stack:
OE_Order_WF.Book_Order(OEOH, 1367, 135371, RUN)
Wf_Engine_Util.Function_Call(OE_BOOK_WF.BOOK_ORDER, OEOH, 1367, 135371, RUN)
-----
Order Lines:
Process:
ENTER
Activity
BOOK_WAIT_FOR_H
Status
NOTIFIED

Or

5) ORA-20001at OE_FULFILL_WF.START_FULFILLMENT
OMSE11i.sql output shows:
OE_Fulfill_WF.Fulfillment(OEOL, 4301, 83745, RUN)
Wf_Engine_Util.Function_Call(OE_FULFILL_WF.START_FULFILLMENT, OEOL, 4301,
83745, RUN)

Or

6) 11-MAY 16:37:40 11-MAY 16:37:40
Line Flow - Generic Fulfill Exception Error
11-MAY 16:37:40 -20001
Customer has orders that are stuck in awaiting fulfillment with child lines.
Confirmed via OMSE11i.sql output for all affected orders that the order lines were at awaiting
Fulfillment
Notification ids exist for order lines that are part of the ATO and they are in booked status

Or

7) Order has an exception in workflow with the following error message:
Error Message ORA-20001:
Error Stack OE_Order_WF.Book_Order(OEOH, 70176, 110960, RUN)
Wf_Engine_Util.Function_Call(OE_BOOK_WF.BOOK_ORDER, OEOH, 70176, 110960, RUN)

Or

8) ORA-20001:
OE_Order_WF.Book_Order(OEOH,29058, 110960, RUN)
Wf_Engine_Util.Function_Call(OE_BOOK_WF.BOOK_ORDER, OEOH, 29058,110960.RUN)

Or

9) The Customer has are several orders that have a workflow error at booking:
Order is not Eligible for Booking. Check workflow status for this order.
Checking the workflow status, ther workflow exception error is:
ORA-20001:
OE_Order_WF.Book_Order(OEOH,29058, 110960, RUN)
Wf_Engine_Util.Function_Call(OE_BOOK_WF.BOOK_ORDER, OEOH, 29058,110960.RUN)

Or

10) 12-APR 11:01:53 12-APR 11:01:53
Schedule - Line Schedule Exception Error
12-APR 11:01:53 -20001
WORKFLOW LINE STATUS ERRORS
LIN_ID PROCESS_NAME ERROR_ACTIVITY_NAME RESULT ACT_STATUS
ERROR_NAME
ERROR_MESSAGE
ERROR_STACK
5225 Schedule - Line Schedule Exception Error -20001
There is an error in the workflow on the line:
ORA-20001:
OE_OEOL_SCH.Schedule Line(OEOL, 5225, 86289, RUN)
Wf_Engine_Util.Function_Call(OE_OEOL_SCH.SCHEDULE_LINE, OEOL, 5225, 86289, RUN)
Customer has order which line will not progress to AR after booking etc.
-----
Ran script

SQL> select item_key
2 from wf_item_activity_statuses_v
3 where item_type='OEOL'
4 and activity_name = 'LINE_SCHEDULING'
5 and activity_status_code = 'ERROR';
ITEM_KEY
---------------
4975
5225
So, there is another line with the same error (ITEM_KEY = 4975)

Or

11) Workflow shows following exception on the order header
Error Name -20001
Error Message ORA-20001:
Error Stack
OE_Order_WF.Book_Order(OEOH, 1221, 124292, RUN)
Wf_Engine_Util.Function_Call(OE_BOOK_WF.BOOK_ORDER, OEOH, 1221, 124292, RUN)

Or

12) There are several orders that have a workflow error when booking:
Order is not Eligible for Booking. Check workflow status for this order.
Checking the workflow status, ther workflow exception error is:
ORA-20001:
OE_Order_WF.Book_Order(OEOH,29058, 110960, RUN)
Wf_Engine_Util.Function_Call(OE_BOOK_WF.BOOK_ORDER, OEOH, 29058,110960.RUN)
There is a WF error in:
WORKFLOW ORDER LEVEL ERRORS
PROCESS_NAME ERROR_ACTIVITY_NAME RESULT ACT_STATUS ERROR_NAME
ERROR_MESSAGE
ERROR_STACK
Book - Order, Manual Book Exception Error -20001
ORA-20001:
OE_Order_WF.Book_Order(OEOH, 29058, 110960, RUN)
Wf_Engine_Util.Function_Call(OE_BOOK_WF.BOOK_ORDER, OEOH, 29058, 110960, RUN)
-----
Workflow Activity Status for Order Error Process
ERR_TYPE_KEY ERR_PROCESS_NAME ERR_ACTIVITY_NAME RESULT ACT_STATUS NOTIF_ID
ASGND_USER BEGIN_DATE END_DATE
WFERROR-WF3875 ROOT Retry-only Null
Active 15-MAR 16:14:44
Retry-only Start Null
Complete 15-MAR 16:14:44 15-MAR 16:14:44
Retry-only Initialize Error COMPLETE
Complete 15-MAR 16:14:44 15-MAR 16:14:44
Retry-only NTF with RETRY only Notified 273351
FND_RESP0: 15-MAR 16:14:44 21615
All orders have the same error and same notification sent to FND_RESP 21615.
-----
SQL> select substr(name,0,18) Name, substr(text,0,55) Value
2 from wf_resources
3 where name in
4 'WF_ADMIN_ROLE';

NAME
VALUE
==========================
WF_ADMIN_ROLE
FND_RESP0:21613

WF_ADMIN_ROLE
FND_RESP0:21613

WF_ADMIN_ROLE
FND_RESP0:21613

WF_ADMIN_ROLE
FND_RESP0:21613

Cause

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