E1: 49: P4210 Generates Error: CAC0001017 and Users Can Not Edit Large Transportation Sales Orders
(Doc ID 2192064.1)
Last updated on JULY 21, 2020
Applies to:JD Edwards EnterpriseOne Transportation Management - Version 9.2 and later
Information in this document applies to any platform.
EnterpriseOne (E1) Application Release: 9.2
EnterpriseOne Tools Release: 18.104.22.168
Enterprise Server Operating System (OS) and service pack: Oracle Enterprise Linux 6 (on OVM, hosted by Sungard)
Database Type/Version/OS: Oracle 12c (22.214.171.124 on separate Oracle Enterprise Linux 6 OVM server, hosted by Sungard)
Web Server Type/Version/OS: WebLogic 12c (on Oracle Enterprise Linux 6 OVM server, hosted by Sungard)
Client Type/Version/OS: Web client - Chrome (latest version -- but also happens with Firefox and IE, on Windows 7, Windows 8, and Windows 10 workstations)
P4210 (Sales Order Entry) and P42101
When changing the carrier and mode of transportation in the header on orders
approximately 250 lines and larger, P4210 fails to update the F4211 from the
F4201 and issues the following errors:
ERROR MESSAGES (ON-SCREEN AND IN LOGS)
No errors on-screen when trying to modify the header. But when you go into
Workcenter, it says transaction not committed
Errors in jde_8579.log:
CAC0001017 - (jdeCacheOpenCursor) failed to open cursor due to reach the max
#cursors (100) for cache (331B490013002-3184)
JDB9900600 - Failed to store value, maximum exceeded. Probable cause is
forgetting to call jdeRemoveDataPtr()
OCI0000178 - Unable to execute - SELECT ABAN8, ABEFTB FROM TESTDTA.F0101
WHERE ( ABAN8 = :KEY1 )
OCI0000179 - Error - ORA-01000: maximum open cursors exceeded
JDB9900401 - Failed to execute db request
STEPS TO REPRODUCE ISSUE
1. Specify no consolidation in the transportation constants
1. Enter a large transportation order that has between 250 to 999 detail
2. Inquire on the order in P4210 and change the carrier and the mode of
transportation in the header. Click OK and ok through the detail.
3. System takes between 20 minutes to 1 hour to process. There is no error
issued in the application. A workcenter message is issued stating
transaction not committed.
4. The errors noted above are issued in the log and the F4211 is not updated
with the changes from the header.
Note- if non transportation fields are changed, the F4211 seems to get
updated but performance is still very slow- 15+ minutes.
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