E1: 09: R09612 Report Fails to Load Data to F09616 & F09617 Tables When There are Multiple Transactions with Same Bank Statement Numbers But with Unique Sequence Numbers.
Last updated on OCTOBER 18, 2017
Applies to:JD Edwards EnterpriseOne General Ledger - Version 9.1 and later
Information in this document applies to any platform.
Report R09612 fails to process the data correctly from F09610 and F09611 tables when there are multiple transactions with same Bank statement numbers but with unique sequence numbers. Because of this all the records in F09610, F09611 tables are not inserted into F09616, F09617 tables as the report updates the statement id value wrongly in F09610, F09611 tables which cause the duplicate data and insert into table failed issue in the tables F09616 & F09617.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms