Last updated on MAY 30, 2017
Applies to:JD Edwards EnterpriseOne Tools - Version SP24 and later
Information in this document applies to any platform.
Checked for relevance on August 14, 2013
Customer upgrading from EnterpriseOne Xe to 9.0 application release level, iSeries AS400 platform. In the upgrade plan, TC R894072 is mapped to run locally on the deployment server in the table conversion workbench. This has a very slow performance compared to the TC running on the application server.
1) How to run TC UBE R894072 on the server?
2) From our analysis we identified that the next numbering known issue for SY='45' has to be set in the F0002 table. Are there any other boundary conditions we have to consider?
3) Are there any issues running this report NOT on the deployment server?
Customer has a list of their conversion jobs ordered by computing time. And they now look for any method how to reduce the time for each job.
TC R894072 is one of these jobs at the top of their list. Though this is a conversion with a sequence number > 100, this job is mapped to LOCAL, i.e. and by default run on the deployment server.
From the Programmers' guide, you can verify that there is a dependency on next numbering on SY='45' which comes in with E1 9.0 and is only available on the local deployment server database.
But if we add this NN prior to running this job to the NN in the control tables on the AS400, we think that we can run it directly on the iSeries server. It looks like it works well, but we are not sure if this dependency is the only reason, and why this job is scheduled to the deployment server.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms