E1:OUTBOUND RTE Records Stay at a Status 3 in F90710 Because of Sequence Number Mismatch Between F90710 & F90708
(Doc ID 1621509.1)
Last updated on JUNE 09, 2023
Applies to:JD Edwards EnterpriseOne Tools - Version 9.1 and later
Information in this document applies to any platform.
Symptom 1: Using E1 Tools 188.8.131.52 for RTE against an Oracle 11g database. Everything was working fine before upgrading to this tools release, but just noticed that there were 87 records sitting in the F90710 at a status '3'. Have all the fixes for the issues with the F90710 and records stuck in status '3'. So it is not a bug issue. Customer submits requests using an application that calls a custom RTE. That then processes and then writes to a F59* status table that shows if the record is processed or whether it failed. In this case, the records would have failed. However, they were still sitting in the F90710 at a status 3(although not sure if they were resubmitted). The sequence # in the F90708 is greater than the F90710, so had to change the sequence # to '0' in the F90708. All transactions are now gone. However, because of this resubmit process, not sure if the user can resubmit the transaction, and if so, the data will be stale and not current. So need to understand how the F90708 # increments in sequence with the F90710 so they can code around these situations.
Symptom 2: Setting up a new RTE environment on a separate machine that points to a separate E1 Server and Transaction Server on a separate weblogic machine. Completed all the setup for the environment but when doing a RTEBUOUT transactions, the data is not processed and the record stays in the F90710 table at a status '3'
Error in the E1Root.log from transaction server:
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