E1: UPG: Handling Custom Objects For an Upgrade and Re-Running Spec Merge
Last updated on APRIL 09, 2018
Applies to:JD Edwards EnterpriseOne Tools - Version 8.97 and Prior and later
Information in this document applies to any platform.
Checked for relevance on February 20, 2013
Checked for relevance on July 31, 2014
What must be done to have custom objects upgraded when upgrading from one release to a newer release? Custom Objects might be changed to product code 88 by the Spec Merge process (as seen on the R98700 PDF, Warning SY88) or not picked up at all if they are not coded correctly in the previous release (i.e. the 'from release'). Some customers may continue development in the prior release and want to upgrade the custom objects after the upgrade plan has been run for the environment. How can these objects be upgraded later?
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