E1: 46: P4617 - Pick Confirmation Creates Zombie Kernel when Case Picking Process is Run
(Doc ID 2720621.1)
Last updated on DECEMBER 15, 2020
Applies to:JD Edwards EnterpriseOne Warehouse Management - Version 9.2 and later
Information in this document applies to any platform.
When processing Case Picking using Pick, Pack and Ship and overriding a 2-Phase Pick where for Phase 1 a quantity is picked that is less than the requested quantity and for Phase 2 the To location is overridden then the Call object Kernel associated with that process dies and creates a Zombie kernel. There appears to be a clear cutoff, the user can pick 45 cases and it works, but 46 cases will kill the kernel every time.
The jde.log shows errors:
ipcSawImpRegisterBSFNV6: Error: BSFN table full for index 34.
: registering <CTRAN.dll/UNKNOWN/CacheProcessPickPackShipHeader> (48) size 989 limit 1024
The JDEDebug.log shows recursive calls of BSFN N4601020 - F4620UpdateforPickConfirm calling itself over and over again.
In the support environment the process simply timed out because the logging slowed down the process so much. For the customer it made 47 calls all the way down to BSFNLevel = 50 before it crashed the kernel.
Also this seems related to the fix for Bug: 25044420 as when that bug fix is commented out in N4601020 then it seems to work.
Steps to Duplicate:
1) Set up dimensionless carton in P46091
2) Set up item with UOM structure 1 CA = 24 EA
3) P46011 Set up U/M definition for UOM=CA and populate Container code
4) Enter Transportation Sales order which creates Pick request for 187 CA
5) Set R46471 version called from R46171 to generate Carton Detail information
6) Set P4620 version to generate Shipment pieces and to create Serial number based on UCC-128
7) Run R46171 to create suggestion for 187 CA = 4488 EA, Note: P4620 Carton detail has been created, 187 records, 1 CA per 1 Container (Box2)
8) P4617 Override Suggestion in Phase 1 and pick 48 CA only
9) P4617 Override the To Location in Phase 2 and pick confirm the 48 CA
10) The process either fails with a web exception or creates Zombie kernel
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