Asynchronous Business Function Error During Confirm Shipment (P4205)

*ERROR* CallObject@1335da45: COSE#1000 Request timeout: timeout after 90000ms host S65F034B:6014(52724) SocID:3740 PID:6915 BSFN:F42UI05EditLine user:MURAKHO Env:JPD812
Complete in 90516ms. Business Function: F42UI05EditLine



There are two different layer of updating Item Location (F41021) during Shipment Confirmation (P4205):

• N4200790 - F42UI05EditLine (F42UI05 Edit Line) which is validate shipment confirmation detail information in exiting row updates Inventory Commitment buckets in F41021 through BSFN B4200370 - CommitSalesOrderToInventory (F41021 Update Order Commitment to Inventory). At this event, inventory cache (which is to be committed through F4111EndDocument) will be created.
• N4200790 - ShipconfirmEndDoc (Shipment Confirmation End Document) in clicking OK button update F41021 (On Hand Quantity and so on) through XT4111Z1 - F4111EndDocument. This routine is same across EnterpriseOne application that work with inventory.

If transaction volume is not high the following changes should be considered:

• jde.ini in the logic server (which controls connection between logic server and clients(JAS server))

[NETWORK QUEUE SETTINGS]
JDENETTimeout=180 (recommend: 360 which is maximum value which JDE recognizes)

• jas.ini (when JAS (client) is talking to Logic server)

[JDENET]
enterpriseServerTimeout=90000 (this is the value which affects your transaction for Asynchronous BSFN(s) get called. Along with above parameter JDENETTimeout you may set 360000 ms)

[OWWEB]
AsynchBSFNEnabled=true (since this value is ON at once Async BSFN gets called it determines time to handle within max value 720000 ms)

• jdbj.ini (When JAS accesses Database server directly the parameter sets below will take effect. So this won't cause timeout error in dealing with BSFN or Call Object Kernel)

[JDBj-CONNECTION POOL]
connectionTimeout=1800000