E1: XML: XML Interoperability & Explicit Transaction Processing
(Doc ID 641086.1)
Last updated on MAY 30, 2017
Applies to:JD Edwards EnterpriseOne Tools - Version 8.93 and later
Information in this document applies to any platform.
We are experiencing issues when attempting to implement Explicit Transactions through the XML Call Object Interoperability Framework.
We are specifying the JDERequest "StartTransaction" request as below :
<startTransaction trans="T1" type="manual"></startTransaction>
We then place a Sales Order (Header, Lines, Footer). We then, to prove concept, perform a rollback as below :
<endTransaction trans="T1" action="rollback"></endTransaction>
However the Order still appears to be committed even though we have explicitly instructed the "Rollback".
We are ensuring the following occurs :
1> The JDE Session Value persist throughout all of the calls including the Transaction Management.
2> We clear the work file at the end of every success or failure.
1> Should the "mnTransactionID" Attribute within the Sales Order Placement FSBeginDoc, EditLine and EndDoc elements be populated with the same value as used within the "trans" attribute of the StartTransaction and EndTransaction Elements?
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