My Oracle Support Banner

E1: DB: Native Table Trigger on F03012 Caused Blocking During Sales Order (Doc ID 2382561.1)

Last updated on JUNE 12, 2023

Applies to:

JD Edwards EnterpriseOne Sales Order Entry - Version 9.1 and later
JD Edwards EnterpriseOne Tools - Version 8.98 and later
Information in this document applies to any platform.


This case study is specific to DB2 database environment. Deadlock or database blocking may take place in different RDBMS system.

As suggested in <Document 1307451.1> - E1: BSFN: How to Debug Asynchronous Business Function Error and Commit Fail Error in EnterpriseOne, e1root_*.log represents as below,

*ERROR* CallObject@c8960b2: CallObject.executeRequest(): Problem executing function [F4211FSEndDoc] lib [CSALES] TM_TRAN_CANCELLED was received from CallObject user:USERID Env:JPD920
 BusFunctionAsynState.executeAsync(): async BSFN failed and need roll back!!
 | async BSFN=BSFN: F4211FSEndDoc
Form Name :P4210_W4210A_MF0100, Transaction ID=10.xx.xx.1xx:53334:1522766480406:61 com.jdedwards.runtime.base.BSFNException:
There was a problem with the server while running the business function F4211FSEndDoc.
The server may still be available, but because of state information, the entire unit of work must be resubmitted.
Please exit the application and restart it.
********* OWVirtual rollback Trxn. ***********
async BSFN failed, trxnID=10.xx.xx.1xx:53334:1522766480406:61


Add the native table trigger from database against F03012 (for this example, DB2).


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.